DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 4ALAlL6U4023491 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 4ALAlL6U4023491 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=L1HhdR15 X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0396D3857722 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1732186041; bh=HKP0ZMVAhrWTi6NVH1o0Ji9Rpsqe6Iolz0Ud+fa3O2Q=; h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=L1HhdR159yfQ/8wSMnGD25KaM0MUM6i2QsZElQ3cN9LSl/1UNhhreyKPj/ug6oQfc VYh3Iu3Whdsq33DBm37L89XFLZ5vNvt8vr7cgyNTHQVmo0Gztfc9a6PaDt0M2WHj/x OUwhKcJcrRtPNmXzLBKrbW1qRC9TlD4vtCYBqTqs= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org E3F063857810 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org E3F063857810 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1732186016; cv=none; b=YpvNcprQLYbSA4xzPcmd8iY+ximNSXgK8/bhd8hpvZAeVbdinOFSRzKSh/VGI8MAUrxpL6ZfGgp9tgbLyEEQjnIjfMjXkPjuJ38npyocCcibT6YRFOmbd9gAM8O58I2WddLgF5u/Jfd3xJ+8d2KA7IAF/CYtQWWSY3A2x7qJqB8= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1732186016; c=relaxed/simple; bh=C4mMz/RqYrjB31QP+wEEeMcUMwcFK1KsytZoy2Ikkzw=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=Y92kdBiRraSnkDZmFg9bwuOZg0VQnbVxqgigvpTCqruaRS3ac95E+I0Cyu8e0A7FR8WjhAk6W/0JPIdxmPXQyGd5eupd5LDP8aethNytMaZd0iumPiLrDB7HN4dWRhscp0LVmkg7Yp8mNz+BWBKFCu5IF3Td6+8JPtlVZFXxQh0= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E3F063857810 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732186013; x=1732790813; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=C4mMz/RqYrjB31QP+wEEeMcUMwcFK1KsytZoy2Ikkzw=; b=hh97JyEAm2KF3Inh2s2fcXUlw4EZ9MeD1cszke6Vn0ExUMtDh6GDGfgmZvM/yKkw3/ WTkH7ISzVd4FDiYIZfGsWB390Euvt63s7UnO4W2Z/8bufpdkX0HPbYpdT2fd2wZ8aDVU c4iOM1QA/CfUlWiouCTNjviOU73e5xt9oSIL+tTcZl3qVSQh+5Urvf4AQFQt4aOAu4Nt 6NpSI+nnAPoaIGcrHHZhSa7GPxZi4Uv7hafOy1f/j6+RtS2p555t1FUYQT73o0SkKSc6 kSPYf7wq4kwCwhdz1GgX0Uf/nW7OROyvpMnanVxy9mFkXSJplk+kCZU2CsrFT6mWcJiC 013A== X-Gm-Message-State: AOJu0Yzo1Fqcgiv/g6s8LNM2Kun6lwWr+8pdy+JgfRlDtDOVbmXWGu6f C81gB3BtYgpHXRm9ZrEOMiGmPI92fBu1nMgoEeOoJgzcNYH3wvg47rsoWRT9jC4VOhNGYuXS/Ol QpI+nNAjEP0K794DiC3b4KiEykjy9tw== X-Google-Smtp-Source: AGHT+IGj3jqsP2od+3fzorbyG/GdA6AyYiBMpo5HuOAlx4Q5gTDn85tDBVQyAPK5XkkhTZisFjGjotx+7GVEw+oqQMc= X-Received: by 2002:a2e:be25:0:b0:2ff:59fa:44f1 with SMTP id 38308e7fff4ca-2ff8db15ed0mr58312271fa.1.1732186013317; Thu, 21 Nov 2024 02:46:53 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 21 Nov 2024 11:46:00 +0100 Message-ID: Subject: Re: Read Windows event log from via Cygwin /proc, /dev, ...? To: cygwin AT cygwin DOT com X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , From: Martin Wege via Cygwin Reply-To: Martin Wege Content-Type: text/plain; charset="utf-8" Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 4ALAlL6U4023491 On Wed, Nov 20, 2024 at 11:38 PM Dan Shelton via Cygwin wrote: > > On Wed, 24 Jul 2024 at 03:10, Brian Inglis via Cygwin 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 > So you want to access the Windows "Ereignisanzeige" via /proc filesystem? Actually a cool idea, because then we could use find&grep to crawl the log for issues Thanks, Martin -- 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