This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Does "syslogd" work?
On Tue, Mar 06, 2001 at 03:22:51PM -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.
>
> What can I type on the bash command line to get something into the event "application" log?
>
> Something like this maybe?
>
> bash> syslogd
Don't start syslogd.
> bash> ssmtp # Or some command that supposedly writes to syslog?
If ssmtp doesn't log by itself, you're out of luck. I suppose that
ssmtp at least has a switch or option in it's conf file.
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