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:	<007d01c27b7a$18913030$f9ae1fc6@highlandshighspeed.net>
From:	"Chris K Ellsworth" <cke AT highlandshighspeed DOT net>
To:	<cygwin AT cygwin DOT com>
References:	<3500515B75D9D311948800508BA379559508A3 AT EX-LONDON>
Subject:	Re: cannot start sshd
Date:	Thu, 24 Oct 2002 09:26:24 -0700
Organization:	Highlands Highspeed Computers
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000

good idea is to also check out the ssh-I list server they specilise in SSH
and cygwin, they 99% have seen this problem before
also to log eorrs to the text files you have to (from what i remember) is to
redirect the error messages to text files.
look in the ssh-i history for this.

http://tech.erdelynet.com/mailman/listinfo/ssh-l/
and for the web page
http://tech.erdelynet.com/ssh.html




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