Philip Hazel wrote:
On Wed, 22 Mar 2006, Chris Lightfoot wrote:
I believe it's because exim links against libc_r (because
it is linked against libcrypto, which itself is linked
against libc_r).
This does not seem to be a problem on FreeBSD 4.10, which is where I ran
my tests, which do include Exim operating as a server, both with and
without TLS (linked with -lcrypto).
In this version of FreeBSD (5.2.1-RELEASE) the threads library is a
userspace one, and I think it must be setting O_NONBLOCK on stdin for
some reason of its own.
OK, it sounds like a FreeBSD 5 thing, but how is it related to stdin? Or
are you running Exim from inetd?
My patch isn't harmless, sadly -- it results in a file
descriptor leak which I also haven't been able to
localise. However, rebuilding the port with
WITHOUT_TLS=yes fixes the problem, which is enough for me.
My reaction to that is to do nothing until I hear more, either from you
or somebody else... I hope this is reasonable.
I would advise strongly against investing any time chasing
oddities on FreeBSD 5.X *unless* they have persisted into
FreeBSD 6.X or 7.X.
5.X was a highly transitional critter, one we ultimately elected
to give a complete miss to - i.e. never did make the 'ready for
prime time' league.
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/
