This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: 1.5.8 release announcement
At 06:51 PM 3/16/2004 -0500, Christopher Faylor wrote:
>On Tue, Mar 16, 2004 at 09:47:30AM -0500, Pierre A. Humblet wrote:
>>
>>
>>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 (*).
>
>Can you attach to the process with strace or gdb to see what's going on?
>Is there a stackdump file sitting around somewhere possibly? I wonder
>if this is a cygrunsrv complaint rather than an exim complaint.
>
>I can't duplicate this on my system, fwiw.
strace didn't show anything unusual.
I think it's a cygrunsrv issue. It seems to go together with a syslog
error entry. Looking at the Windows event log, the syslog error entries
(signal 15 raised) started appearing last time I updated cygrunsrv.
Pierre