X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <20051124113107.GC2999@calimero.vinschen.de>
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>
Date: Thu, 24 Nov 2005 15:03:42 +0100
To: cygwin AT cygwin DOT com
X-UMS: email
Subject: Re: Suggest cygrunsrv extension: --pidfile option (patch included)
From: "Christian Franke" <Christian DOT Franke AT t-online DOT de>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Message-ID: <1EfHhO-1i3eWO0@fwd33.aul.t-online.de>
X-ID: EZMX6-ZG8eSJtG69DQeQHRyC9oV2sfg2MvKHuWW1yWCDcee2lOTagy AT t-dialin DOT net
X-TOI-MSGID: cb4f2b0b-13b9-445c-bc4a-93598592273d
X-IsSubscribed: yes
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

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.

Service control via SCM works as expected, because the handler is run in
an extra thread.


> > 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 ;-) 

Unlike syslog, windows event log is intended to store only message
parameters, not complete messages.
The (probably localized) messages must be provided by such an "event
message file" (the misleading MS-term;-), which is essentially an .exe
or .dll containing (message id, string) pairs in a resource section.
For Cygwin, this would be one trivial (0, "%1") pair.

Does such a file (and associated registry tool) exist for Cygwin?

Christian



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