X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: "Bryan D. Thomas" <cinder_bdt AT yahoo DOT com>
Subject:  SOLVED Re: cygrunsrv stderr and stdout only to a syslog-ng log?
Date:  Wed, 22 Mar 2006 06:59:37 -0800
Lines: 21
Message-ID: <dvroos$335$1@sea.gmane.org>
References:  <20060321214505 DOT 62914 DOT qmail AT web31302 DOT mail DOT mud DOT yahoo DOT com> <20060322133845 DOT GC9091 AT calimero DOT vinschen DOT de>
X-IsSubscribed: yes
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

"René Berber" <r DOT berber AT computer DOT org> wrote:
> The problem I guess is that you have more than one sshd process running, 
> are
> the syslog messages the same as the ones in the event log?

"Corinna Vinschen" <corinna-cygwin AT cygwin DOT com> wrote:
> 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.

Thanks again, René and Corinna.  The Application Event Log messages stopped 
at one point during the day, and I was able to determine from the PID in the 
messages that the same messages were not being logged by syslog-ng.  So it 
turned out that it was a sshd process that had started before or ended after 
syslog-ng.  I used the sc.exe tool to add a dependency on syslog-ng to the 
sshd service, and I will modify my install instructions to add the -y option 
to the cygrunsrv install of sshd.

Best regards,
Bryan 




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