Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID:	<020701c291a9$a7f22500$78d96f83@pomello>
From:	"Max Bowsher" <maxb AT ukf DOT net>
To:	<Mike DOT P DOT Smith AT kp DOT org>, <cygwin AT cygwin DOT com>
References:	<OF1C4C5A0A DOT BF646AFF-ON88256C78 DOT 00754B97 AT KP DOT ORG>
Subject:	Re: sshd.log permissions error message
Date:	Thu, 21 Nov 2002 22:02:17 -0000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106

Mike DOT P DOT Smith AT kp DOT org <Mike DOT P DOT Smith AT kp DOT org> wrote:

> Hi Max,

Hi - please keep replies on list.

> You know in the heat of working through setting sshd up I didn't
> think to check the latest time stamp on the log, and after checking
> it I find that it is a bit stale. However, if I have logs prior to
> the time that I fixed a problem preventing sshd from starting then
> why don't I get any entries in sshd.log now?

Because sshd only logs serious error conditions to stdout & stderr (which is
what is being sent to /var/log/sshd.log, by cygrunsrv).

You can add the -e option to log to stderr instead of syslog (the NT event
log).

--
Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -