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-Authentication-Warning:	shell-2.enteract.com: fcy set sender to fred AT ontosys DOT com using -f
Date:	Fri, 1 Jun 2001 16:23:24 -0500
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
Message-ID:	<20010601162324.A85235@enteract.com>
References:	<F54Ssuot0OUIHNkjgJK0000bf16 AT hotmail DOT com>
Mime-Version:	1.0
User-Agent:	Mutt/1.2.5i
In-Reply-To:	<F54Ssuot0OUIHNkjgJK0000bf16@hotmail.com>; from karlm30@hotmail.com on Thu, May 31, 2001 at 10:34:17PM -0700

On Thu, May 31, 2001 at 10:34:17PM -0700, Karl M wrote:
> If I add syslog statements, when it works I see log entries for all of them. 
> When it doesn't work, I see none of the log entries that I added. The first 
> one was just after the openlog call in service_main (and just before the 
> RegisterServiceCtrlHandlerA call). Sometimes it works, sometimes it doesn't.

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().

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

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

- Raw text -