Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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" To: , References: Subject: Re: sshd.log permissions error message Date: Thu, 21 Nov 2002 22:02:17 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit 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 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/