Philip Hazel wrote:
On Tue, 21 Mar 2006, Chris Lightfoot wrote:
Further inspection with ktrace indicates that something
was setting O_NONBLOCK on the input stream (smtp_in in
smtp_in.c); the first read from the stream will then
typically fail with -EAGAIN, which is treated as an error.
As you say, Exim doesn't use O_NONBLOCK on the input file descriptor,
and this problem has not been reported by anybody else. There are
certainly people running Exim under FreeBSD - indeed I tested it on the
exim.org machine.
So, anyway, I have a temporary fix, but if it'd be useful
to investigate this further I'm happy to help.
I don't think there's anything I can do myself, because the problem
doesn't arise on the FreeBSD system to which I have access. Your fix
seems innocuous, but I'm not too keen on just putting it in without
understanding why it should be necessary.
JFWIW, we have never run Exim on anything *but* FreeBSD, both:
- from the 'ports' collection
- from Exim tarball, with apropriate edits of local.cfg
.. and have never (been aware of) experiencing the problem reported.
FreeBSD 4.8 thru 4.11 (so far).
Bill Hacker
--
## List details at http://www.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://www.exim.org/eximwiki/
