X-Spam-Check-By: sourceware.org
Message-ID: <438E32E4.FEAE0875@dessent.net>
Date: Wed, 30 Nov 2005 15:16:52 -0800
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Redirect SSHD messages from Application to Security log in Win2k
References: <loom DOT 20051130T010840-939 AT post DOT gmane DOT org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
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

Listmail wrote:

> 1) The sshd messages in the Windows Event Viewer Application log are half junk
> and half "real" message. The following junk paragraph appears in every logged
> message. How can I get rid of it ?

It is possible, but not a simple change that you can just enable. 
You'll need to add a messagetable resource to the cygwin DLL and rebuild
it, as well as add registry keys for all event sources.  Search the
mailing list archives for details.  Here is a recent thread:
<http://cygwin.com/ml/cygwin/2005-11/msg00747.html>.

> 2) I would like the ssh messages to go to the Security log, as it is empty now
> and seems like a logically named place for these events. The application log is
> getting full quickly by ssh logon/logoff messages.

This is not possible without modifying the syslog code in cygwin, and
even then I don't know if regular applications can log to the security
log.

Brian

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