Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Subject: RE: access to event log of windows
Date: Mon, 12 Jul 2004 15:25:04 +0200
Message-ID: <0C7AD907113E984F9C2AF0B651D0D3DE07A698@exmid04.africa.enterprise.root>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Mike Kenny - BCX - Infrastructure Services" <Mike DOT Kenny AT bcx DOT co DOT za>
To: <cygwin AT cygwin DOT com>
X-OriginalArrivalTime: 12 Jul 2004 13:25:04.0739 (UTC) FILETIME=[A489FB30:01C46813]
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id i6CDPMlV024000

> > thanks for this useful information. Is there a comparable 
> command line utility
> > to inspect the event log(s)? I know of psloglist and 
> dumpel, but I really want
> > to stick with cygwin tools. Any possibility?
> 
> Not yet, no.  You could write one ;-)
> 
> Corinna

I could, but it might end up putting more messages into the
event log than it reads :-(

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/