From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31382 invoked by alias); 10 Jun 2002 13:00:21 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 31358 invoked from network); 10 Jun 2002 13:00:10 -0000 Received: from unknown (HELO cygbert.vinschen.de) (217.81.213.157) by sources.redhat.com with SMTP; 10 Jun 2002 13:00:10 -0000 Received: (from corinna@localhost) by cygbert.vinschen.de (8.11.6/8.9.3/Linux sendmail 8.9.3) id g5AD02m11345 for cygwin@cygwin.com; Mon, 10 Jun 2002 15:00:02 +0200 Date: Mon, 10 Jun 2002 07:41:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Syslog (was: ) Message-ID: <20020610150002.U30892@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20020610124718.83609.qmail@web21008.mail.yahoo.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 X-SW-Source: 2002-06/txt/msg00523.txt.bz2 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@cygwin.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/