Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <01ab01c0a651$4f608020$275c100a@actfs.co.uk> From: "Malcolm Boekhoff" To: "Cygwin News Group" References: <016901c0a647$02e56210$275c100a AT actfs DOT co DOT uk> <20010306153615 DOT G7734 AT cygbert DOT vinschen DOT de> Subject: Re: Does "syslogd" work? Date: Tue, 6 Mar 2001 15:22:51 -0000 > > 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 bash> ssmtp # Or some command that supposedly writes to syslog? -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple