Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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" To: fred AT ontosys DOT com Cc: cygwin AT cygwin DOT com Subject: Re: cygrunsrv fails to start Date: Sat, 02 Jun 2001 17:36:52 -0700 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 03 Jun 2001 00:36:52.0646 (UTC) FILETIME=[48A87C60:01C0EBC5] Hi All... >From: Fred Yankowski >To: Karl M >CC: cygwin AT cygwin DOT com >Subject: Re: cygrunsrv fails to start >Date: Fri, 1 Jun 2001 16:23:24 -0500 > >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. I also put logging to a file just in front of the call to StartServiceCtrlDispatcherA. And...When it works, it works (and I get logging from service_main and main). When it fails I get nothing. So it looks like we don't even get to the call for StartServiceCtrlDispatcherA when it fails. To me this looks more and more like someone doesn't like loading the cygwin1.dll or something like that? I don't know what else to try right now. I'm open to ideas. >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. > Thanks, ...Karl _________________________________________________________________ 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