From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21180 invoked by alias); 10 Jun 2002 14:29:56 -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 21140 invoked from network); 10 Jun 2002 14:29:45 -0000 Received: from unknown (HELO cygbert.vinschen.de) (217.81.213.157) by sources.redhat.com with SMTP; 10 Jun 2002 14:29:45 -0000 Received: (from corinna@localhost) by cygbert.vinschen.de (8.11.6/8.9.3/Linux sendmail 8.9.3) id g5AETaP11771 for cygwin@cygwin.com; Mon, 10 Jun 2002 16:29:36 +0200 Date: Mon, 10 Jun 2002 08:22:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Syslog (was: ) Message-ID: <20020610162936.A11668@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20020610150002.U30892@cygbert.vinschen.de> <20020610131410.43748.qmail@web21001.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020610131410.43748.qmail@web21001.mail.yahoo.com> User-Agent: Mutt/1.3.22.1i X-SW-Source: 2002-06/txt/msg00528.txt.bz2 On Mon, Jun 10, 2002 at 06:14:10AM -0700, Nicholas Wourms wrote: > If you are going to emulate *n*x, you are going have to run some > processes. Memory is cheap, and certainly the syslogd wouldn't use that > much, would it? Also, it's not like you couldn't have the messages fall > back to the NTeventlog or Ugly-syslog, should the service not be started > or fail. I bet it would even be possible to have syslogd pass messages to > the NT Event Log, as well. Anyhow, the concept of running a full blown > installation of cygwin w/o any additional processes will be moot once > cygserver becomes mainstream. IMHO, the NT Event Log is not very > extensible and, of course, is proprietary. Just my 2 cents... Memory is obviously not a problem but: - The base tools needed to build programs (gcc/as/ld/etc) always will have to run w/o starting some service. - Even if cygserver is becoming mainstream, Cygwin will still have to run nicely w/o cygserver. No base functionality (e. g. fork()) may require cygserver. - The openlog/syslog calls in the kernel should work even if no syslogd is running. This will become somewhat tricky if each call has to check the existance of a running syslogd to be able to fallback to event log if it's not running (The connection is..., well, connectionless. Syslog is using UDP). Ok, that's easy to solve... The solution if we going to utilize syslogd has to fulfill these requirements. Basically Cygwin is still only an emulation layer to allow building and running POSIX applications, not a full substitute for an OS (even if we're not *that* far away ;-)). 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/