Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Tue, 6 Mar 2001 15:36:15 +0100 From: Corinna Vinschen To: cygwin Subject: Re: Does "syslogd" work? Message-ID: <20010306153615.G7734@cygbert.vinschen.de> Mail-Followup-To: cygwin References: <016901c0a647$02e56210$275c100a@actfs.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <016901c0a647$02e56210$275c100a@actfs.co.uk>; from Malcolm.Boekhoff@actfs.co.uk on Tue, Mar 06, 2001 at 02:09:08PM -0000 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