just found out that exim 3.2x on our 2.7 boxes is also showing this problem,
binaries were compiled with gcc on a separate 2.7 box. exim 3.16 is fine on
these boxes.
Jon
-----Original Message-----
From: Philip Hazel [
mailto:ph10@cus.cam.ac.uk]
Sent: 12 June 2001 11:11
To: EXIM Users
Cc: exim-users@???
Subject: RE: [Exim] exim 3.22 problem on solaris 2.6
On Tue, 12 Jun 2001, EXIM Users wrote:
> The only change to the configuration between 3.2x and 3.16 I made was to
> remove "timeout_frozen_after" (as this option isn't supported in 3.16)
My researches in the code haven't turned up anything that appears to be
significant.
What I am going to do is to build 3.30 as it currently is, and start
running it on our Solaris 8 systems. I will make it available in the
Testing subdirectory for people to try out for this problem.
My expectation is that the problem will still be present. If it is, I
will make another version that has additional logging at some high log
level (say 10) that writes a few log lines while it is supposedly
receiving a message and putting it in a -D file. Running this until
there is an orphan might give me enough information to figure out what
is happening. If not, we might have to go round the loop again...
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
--
## List details at
http://www.exim.org/mailman/listinfo/exim-users Exim
details at
http://www.exim.org/ ##
----------------------------------------------------------------------
If you have received this e-mail in error or wish to read our e-mail
disclaimer statement and monitoring policy, please refer to
http://www.drkw.com/disc/email/ or contact the sender.
----------------------------------------------------------------------