X-Spam-Check-By: sourceware.org
Date: Thu, 24 Nov 2005 12:31:07 +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: <20051124113107.GC2999@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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4384E07F.6000308@t-online.de>
User-Agent: Mutt/1.4.2i
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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 23 22:34, Christian Franke wrote:
> Corinna Vinschen wrote:
> 
> >[...]
> > /* foo */
> >
> > /* foo bla ...
> >    ... blub */
> > 
> >
> 
> ;-)
> 
> 
> Sorry, I have no time now to answer in detail, let net new patch speak 
> for itself ;-)
> 
> http://franke.dvrdns.org/cygwin/cygrunsrv-pidfile-patch-1.txt
> 
> Stale .pid file is now removed on exit of cygrunsrv (Testcase: syslogd 
> itself)
> All other issues changed as requested.

Cool.

> Open issue: signals are blocked in waitanypid().

I'll have a look into it, but I'm fairly busy at the moment.

> 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.  The fact that logging using syslogd works at
all is pretty new, introduced with 1.5.16 or 1.5.17.


Thanks,
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/