Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
X-Originating-IP: [24.0.161.175]
From: "Karl M" <karlm30 AT hotmail DOT com>
To: fred AT ontosys DOT com
Cc: cygwin AT cygwin DOT com
Subject: Re: cygrunsrv fails to start
Date: Sat, 02 Jun 2001 12:56:54 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F200tXsL1c00goZolmR0000d677@hotmail.com>
X-OriginalArrivalTime: 02 Jun 2001 19:56:54.0301 (UTC) FILETIME=[2C1074D0:01C0EB9E]

Hi All...

>From: Fred Yankowski <fred AT ontosys DOT com>
>To: Karl M <karlm30 AT hotmail DOT com>
>CC: cygwin AT cygwin DOT com
>Subject: Re: cygrunsrv fails to start
>Date: Fri, 1 Jun 2001 16:23:24 -0500
>
>You've done a good job chasing down the problem so far, and I
>sympathize with the hassle involved in tests that require restarting
>NT over and over.
>
>I would suggest adding some trace statements that write to a file
>rather than depending on the syslog facility.  I would put one right
>after the entry to main() to see if the process is even entered.  Be
>sure to flush() the trace output after each message in case the
>process aborts and loses buffered output.  I would put another trace
>message at the point where StartServiceCtrlDispatcherA() fails in
>main().  Then I'd put another right after the entry to service_main().

I put a fopen, fputs and fflush at the top of service_main before anything 
else happens. The times when cygrunsrv starts up, everything works and I get 
my output. The times when it does not start, I get nothing (no file creater 
and no output).

I also completely removed cygwin and reinstalled everything with setup 2.57. 
No change: sometimes it works, sometimes it doesn't. I wasn't expecting this 
to make a difference.

>It looks like failure of StartServiceCtrlDispatcherA() would not be
>reported currently, given that error() writes to stderr and that
>stream is useless in this case.  However, it's hard to see how that
>API could fail in some cases and not others.
>
>Your questions about possible problems in loading the cygwin1.dll
>occurred to me too, but I don't know anywhere near enough about Cygwin
>to suggest how to explore that possibility.
>
>--
>Fred Yankowski           fred AT OntoSys DOT com      tel: +1.630.879.1312
>Principal Consultant     www.OntoSys.com       fax: +1.630.879.1370
>OntoSys, Inc             38W242 Deerpath Rd, Batavia, IL 60510, USA

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple