Date: Wed, 22 Mar 2006 14:38:45 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cygrunsrv stderr and stdout only to a syslog-ng log?
Message-ID: <20060322133845.GC9091@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20060321214505.62914.qmail@web31302.mail.mud.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060321214505.62914.qmail@web31302.mail.mud.yahoo.com>
User-Agent: Mutt/1.4.2i
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Mar 21 13:45, Bryan D. Thomas wrote:
> I've found in cygrunsrv.README that the -1 and -2
> arguments may be used to specify that output of stdout
> and stderr go to a log file instead of to the Windows
> Event Log.
> 
> I'm using cygrunsrv to run two services: sshd and
> syslog-ng.  I'm using syslog-ng to collect timestamped
> log entries from sshd and do postprocessing with
> filters.  What I want to do is stop logging sshd
> events also to the Windows Event Log.

Is it possible that the sshd service is started before the syslog-ng
service?  In that case the startup messages of the starting sshd service
would go to the Windows event log as a fallback, because the syslog
function finds that no syslog service is running.  If you add a
dependency to the sshd service, so that its only started when syslog-ng
is present, then you shouldn't see that problem anymore.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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