DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 4ALAMnoQ4016634
Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 4ALAMnoQ4016634
X-Recipient: archive-cygwin AT delorie DOT com
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
Date: Thu, 21 Nov 2024 11:22:25 +0100
To: cygwin AT cygwin DOT com
Subject: Re: Read Windows event log from via Cygwin /proc, /dev, ...?
Message-ID: <Zz8J4Rd8kNY6F_yA@calimero.vinschen.de>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CAAvCNcCneJYStu-8BLdwdgGwuUcZ1z8-X6q40YyHHdW2Ga60Pg AT mail DOT gmail DOT com>
 <badb0463-d3c3-4de4-9b38-c7e0466d0785 AT SystematicSW DOT ab DOT ca>
 <CAAvCNcBNkFc50B4KWXXtX7h1Dve2sy8E239x7TCDYG4woBRskA AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <CAAvCNcBNkFc50B4KWXXtX7h1Dve2sy8E239x7TCDYG4woBRskA@mail.gmail.com>
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.30
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Corinna Vinschen via Cygwin <cygwin AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
Cc: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>

On Nov 20 23:36, Dan Shelton via Cygwin wrote:
> On Wed, 24 Jul 2024 at 03:10, Brian Inglis via Cygwin <cygwin AT cygwin DOT com> wrote:
> >
> > On 2024-07-23 18:07, Dan Shelton via Cygwin wrote:
> > > Does Cygwin have a script API to read the Windows event log, maybe via /proc
> > > or /dev?
> > Install package syslog-ng and set up Cygwin syslog, then set up other processes
> > that can, to write to syslog, and read that at /var/log/syslog.
> 
> That was not my idea. I want to access the Windows event log via /proc or /sys

Cygwin doesn't have that.  Is `wevtutil' not sufficient?

PTC, though I'm not sure what this is worth.  Windows events are not
just some numbers and a lump of strings.  They contain pointers (more
or less) into DLLs which in turn contain log strings.  And there
aren't just the four Windows logs anymore as in the past, but a whole
lot of "application and service logs".


Corinna

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