Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <9b83ffd9050907155754d21e1@mail.gmail.com>
Date: Wed, 7 Sep 2005 15:57:59 -0700
From: Jack Offerman <jofferman@gmail.com>
To: Cygwin List <cygwin@cygwin.com>
Subject: Re: sftp "connection closed"
In-Reply-To: <6.2.1.2.0.20050907172646.04743e18@pop.prospeed.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
References: <9b83ffd905090709337e1bf8f2@mail.gmail.com> 	 <6.2.1.2.0.20050907172646.04743e18@pop.prospeed.net>
Content-Transfer-Encoding: 8bit

On 9/7/05, Larry Hall <lh-no-personal-replies-please@cygwin.com> wrote:
> At 12:33 PM 9/7/2005, you wrote:
> >When "ssh host" works but "sftp host" doesn't, where should I look?
> >
> >I appreciate your help.
> 
> I guess you could try starting the server with debugging turned on and
> see what you get from the logs there.  Results from that are usually
> more instructive.


It started working again after I changed /etc/passwd.
When I recreated the file by doing mkpasswd -l, I also
hand-editted something. That is the last part of the line,
the login shell. Originally it was bash, and I changed it
to tcsh. Being a tcsh fan all my life, I've always hated
when I had to type "tcsh" right after logging in on a ssh
session because the login shell is bash. When I did
mkpasswd, I thought it was a perfect time to change
my login shell to tcsh. And I was happy with the result:
tcsh running as a login shell.

With tcsh as a login shell, however, sftp didn't work.
With bash, it is working now. So I take it.

J

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