This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Does "syslogd" work?
- To: cygwin <cygwin at cygwin dot com>
- Subject: Re: Does "syslogd" work?
- From: Corinna Vinschen <cygwin at cygwin dot com>
- Date: Tue, 6 Mar 2001 15:36:15 +0100
- References: <016901c0a647$02e56210$275c100a@actfs.co.uk>
On Tue, Mar 06, 2001 at 02:09:08PM -0000, Malcolm Boekhoff wrote:
> I thought I could use the syslogd daemon to get some idea of what ssmtp is
> doing, but when I type "syslogd&" at the bash prompt, the command starts and
> exits immediately!
Nope. It forks and the parent exits. The child is running in the
background as it's usual for a daemon.
Unfortunately, syslogd isn't that useful.
the syslog always goes to the NT eventlog on NT/W2K and always
into C:\\CYGWIN_SYSLOG.TXT on 9x/ME.
However, patches to Cygwin are really welcome. I would like to
see my syslog output fed to syslogd as well when it's running.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple