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/
