Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Mon, 10 Jun 2002 15:00:02 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Syslog (was: ) Message-ID: <20020610150002.U30892@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20020610124718 DOT 83609 DOT qmail AT web21008 DOT mail DOT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020610124718.83609.qmail@web21008.mail.yahoo.com> User-Agent: Mutt/1.3.22.1i On Mon, Jun 10, 2002 at 05:47:18AM -0700, Nicholas Wourms wrote: > I completely agree, plus it could also allow customization of which > messages are logged and which are sent to the console. > > So you have my vote for this functionality :-). There's just the problem that we don't want Cygwin to rely on a running syslogd. syslogd isn't an integral part of the OS (as on U*X systems) while the NT event log is. Well, on NT. On 9x we have the ugly syslog file workaround. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/