Can it be sendmail refers internaly to a domain which isn't resolvable
at that time? DNS not yet up? Link not yet configured?
> Just happend again -- twice. The first time, it didn't seem to be coming
> out of it any time soon. I eventualy did sysrq-u,s,b and went for another
> go. Did it again, same spot. This time I got two addresses: c018e264 and
> c011184d. The first is apm_do_idle (+0x64), the second is schedule (+9).
> (I didn't check the sysrq-t output this time, but the schedule would seem to
> suguest that sendmail was acatually doing _somthing_. OTOH, I don't know
> why apm_do_idle would be doing anything in that case.) Also, please see my
> Oops post that I'll be putting up shortly: it's possible that they are
> related. Oh, yeha. I'm going to disable APM in the BIOS on my next boot to
> see if that has any effect.
The machine was problably idleing, waiting for the DNS request to
return...
Met vriendelijke groet,
Pauline Middelink
-- PGP Key fingerprint = DE 6B D0 D9 19 AD A7 A0 58 A3 06 9D B6 34 39 E2 For more details look at my website http://www.polyware.nl/~middelin- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu