>> Apparently, the accept() in sendmail daemon loop can return
>> ETIMEDOUT and cause sendmail to sleep for 5 seconds during
>> which time no new connections will be accepted. An error is
>> reported to syslog:
>> What is going on here? This is a heavily loaded mail server. Is
>> this really a Linux kernel bug?
Richard> Apparently. Sendmail() expects to see EWOULDBLOCK even
Richard> though the socket has not been set to non-blocking. The
Richard> kernel returns ETIMEDOUT if no resources are presently
Richard> available. I know what my Sun does under these
Richard> conditions, but I don't think a kernel crash is the
Richard> correct response either!
Odd. Well, I manually patched Sendmail to ignore ETIMEDOUT and
EHOSTUNREACH (both of which I've been getting recently) and the
problems went away. Go fig.
-- Brought to you by the letters X and R and the number 4. "We are the music makers. And we are the dreamers of dreams." -- Willy Wonka Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu