X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Andrew Schulman <schulman DOT andrew AT epamail DOT epa DOT gov>
Subject:	Re: Making sftp and ssh work on cygwin
Date:	Wed, 07 Mar 2007 10:54:14 -0500
Lines:	18
Message-ID:	<9lntu2pcn67ib9cj92ji2j95ekk0sg88ba@4ax.com>
References:	<45EECEBC DOT 1000003 AT buongiorno DOT com> <gnktu2dogel1pi6ip30rd00ap357jsfeme AT 4ax DOT com> <45EEDDD2 DOT 30900 AT buongiorno DOT com>
Mime-Version:	1.0
X-Archive:	encrypt
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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

> Andrew Schulman wrote:
> > Try adding -v or -vv to get some information about the protocol exchange,
> > and where it's stopping.  You can probably also get some information from
> > the ssh server logs.
> >   
> 
> Thanks for your quick answer, Andrew. I didn't get more information with 
> ssh or sftp using -v or -vv. I've also looked for logs under cygwin root 
> directory, but found none. Would you have any idea where these logs are 
> usually stored?

To be clear, you want to look at the server logs on the remote host:
142.268.10.26 (or whatever the right host name is), where the ssh server is
running.  On my Debian box, sshd logs to /var/log/auth.log, but you have to
be root to read the log.

Good luck,
Andrew.


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

- Raw text -