X-Spam-Check-By: sourceware.org Message-ID: <31b7d2790703070803k483aade6mfd5ab18d7acf91b2@mail.gmail.com> Date: Wed, 7 Mar 2007 10:03:50 -0600 From: "DePriest, Jason R." To: cygwin@cygwin.com Subject: Re: Making sftp and ssh work on cygwin In-Reply-To: <9lntu2pcn67ib9cj92ji2j95ekk0sg88ba@4ax.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45EECEBC.1000003@buongiorno.com> <45EEDDD2.30900@buongiorno.com> <9lntu2pcn67ib9cj92ji2j95ekk0sg88ba@4ax.com> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 3/7/07, Andrew Schulman wrote: > > 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. > > > -- By default, the errors will be sent to the Windows Event Log. -Jason -- 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/