This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: 1.5.8 release announcement
Christopher Faylor wrote:
>
> On Mon, Mar 15, 2004 at 11:42:12PM -0500, Christopher Faylor wrote:
> >Given Pierre's description of the exim problem, however, it doesn't seem
> >like my fix would affect that.
>
> FYI, I just fixed a problem similar to what Pierre reported.
>
> So, it looks like there were two different problems.
>
> cgf
>
> >Assuming that this checkin didn't solve the problem, Pierre, can you
> >tell me how to duplicate your exim problems?
This is what I see with the snapshot
***********************************
~> uname -a
CYGWIN_NT-4.0 usched40576 1.5.8s(0.112/4/2) 20040316 00:33:52 i686 unknown unknown Cygwin
~> net stop exim
The Exim Mail Transfer Agent service is stopping.
A system error has occurred.
System error 1067 has occurred.
The process terminated unexpectedly.
The Exim Mail Transfer Agent service was stopped successfully.
************************************
While experimenting after sending my report yesterday I had also
sometimes observed the message above. Today I only see the message,
there are no errors in the log (*).
Except for the message, everything is fine! I don't understand
why Windows reports that the termination is unexpected when it occurs
after "net stop". Also, I don't see any abnormalities when stopping
with cygrunsrv -E. So I am not sure there is a Cygwin problem.
To reproduce: if you have never installed exim, do so and run
exim-config. Answer yes to start the service.
Then "net stop exim".
Pierre
(*) When stopping, exim very often has log entries such as
2004-03-16 09:34:39 50 select() failures: Bad file descriptor
This is not new and doesn't seem to indicate a real problem.