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
Subject:	RE: access to event log of windows
Date:	Tue, 13 Jul 2004 14:59:17 +0200
Message-ID:	<D7FBE8A336018A4EB5EBDC6C898821930991C752@HUELVA.belgium.fhm.de>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
From:	"Morche Matthias" <Matthias DOT Morche AT P7S1Produktion DOT de>
To:	<cygwin AT cygwin DOT com>
X-OriginalArrivalTime:	13 Jul 2004 12:59:18.0471 (UTC) FILETIME=[354DF570:01C468D9]
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id i6DCxxKs005321

Another Method is using psloglist from SysInternals psutils package. It's not cygwin, but native win32.

...
> I have doubts there's a portable way to scan syslog 
> programmatically.  If
> you simply want to access the NT event log, look at the libwin32-perl
> package (there may be other ways, too).
...

--
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/

- Raw text -