Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3A2C2FD5.7AACB10C@sattel.com>
Date: Mon, 04 Dec 2000 15:59:17 -0800
From: Bruce Edge <bedge AT sattel DOT com>
Organization: Sattel Global Networks
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.15-4mdk i686)
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin support <cygwin AT sources DOT redhat DOT com>
Subject: syslogger, NT vs. Win 95
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

After spending some time debugging on both NT and win 95, I have to say, I
like the win 95 method for handling syslog messages much better. Putting the
syslog message text in a file is much more conveniant than having to dig them
out of the NT event loggger.

You can "tail -f" the generated file and view events in pseudo-real-time, just
like in unix, whereas the NT event logger seems to be optimized for systems
that don't generate many events. It's impossible to get a quasi-real-time log
dumped to stdout. One must click on each event to extract the text that was
logged.

I'd like to suggest that the NT event logger mechanism be made into an option
that can be disabled. 
As long as I'm at it, a time stamp in the file would be nice too.

Just my $.02

-Bruce.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com