X-Spam-Check-By:	sourceware.org
Date:	Thu, 24 Nov 2005 16:31:42 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Suggest cygrunsrv extension: --pidfile option (patch included)
Message-ID:	<20051124153142.GE2999@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<4380AB2E DOT 7010302 AT t-online DOT de> <20051121153016 DOT GI2999 AT calimero DOT vinschen DOT de> <438221C6 DOT 1080103 AT t-online DOT de> <20051122095442 DOT GL2999 AT calimero DOT vinschen DOT de> <4384E07F DOT 6000308 AT t-online DOT de> <20051124113107 DOT GC2999 AT calimero DOT vinschen DOT de> <1EfHhO-1i3eWO0 AT fwd33 DOT aul DOT t-online DOT de>
Mime-Version:	1.0
In-Reply-To:	<1EfHhO-1i3eWO0@fwd33.aul.t-online.de>
User-Agent:	Mutt/1.4.2i
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Nov 24 15:03, Christian Franke wrote:
> Corinna Vinschen wrote:
> > [...]
> > > Open issue: signals are blocked in waitanypid().
> > 
> > I'll have a look into it, but I'm fairly busy at the moment.
> 
> If the --pidfile option is used, signals sent to cygrunsrv will not be
> routed to service because cygrunsrv is blocked in WaitForSingleObject().
> This is IMO a minor issue than can be left open in an initial release.

Oh, right.  That should be solvable in future by adding another
cygwin_internal() option.

> > > OffTopic: Is there any event message file available for cygwin apps
> > > writing to syslog if syslogd is not running ?
> > > I can provide one if you want.
> > 
> > Huh?  If syslogd is not running, the logs are written either to the
> > Application event log (NT) or to C:\\CYGWIN_SYSLOG.TXT (9x).  That's
> > implemented since eons.  [...]
> 
> Yes, and since eons the windows event viewer complains about a missing
> "event message file" when viewing messages generated by Cygwin apps ;-) 

Argh, again I misinterpreted what you said, as you might have noticed.
Brian has answered that.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -