Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-Id: <4.2.2.20010426084120.00b59940@autobahn.its.washington.edu>
X-Sender: joel AT autobahn DOT its DOT washington DOT edu
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Thu, 26 Apr 2001 08:52:17 -0700
To: Corinna Vinschen <cygwin AT cygwin DOT com>
From: Joel Bradbury <joel AT its DOT washington DOT edu>
Subject: Re: problem with sshd as service
In-Reply-To: <20010426105235.C3827@cygbert.vinschen.de>
References: <4 DOT 2 DOT 2 DOT 20010425130142 DOT 00b53d30 AT autobahn DOT its DOT washington DOT edu>
 <4 DOT 2 DOT 2 DOT 20010425130142 DOT 00b53d30 AT autobahn DOT its DOT washington DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

Moving to 1.3.1 did fix this for me.

I also received a note from Karl M pointing out that the problem was 
related to sshd and ssh running under different usernames (which of course 
occurred since I was running the service under the system account).  When 
running sshd from the command line, the same problem arose if the client 
logged in under a different username.

Some other suggestions--piping sshd to cmd.exe, and using bash instead of 
sh, didn't help in my case.

Thanks to everyone for the speedy responses!

At 10:52 AM 4/26/01 +0200, you wrote:
>On Wed, Apr 25, 2001 at 01:53:58PM -0700, Joel Bradbury wrote:
> > I'm having a weird problem when I try to run sshd as a service on NT.  The
> > sshd service is set to run under the system account (using srvany.exe), I
> > have system path set to include my /bin and /usr/bin directories, and my
> > log in shell is /bin/sh.  I can log in fine and run pwd or cd, but when I
> > try something like ls, things just hang, with my cpu usage hitting the
> > ceiling.  I have to kill the sh and ls to recover.  If, from the /bin/sh
> > prompt, I run cmd.exe, and try ls under that, it works fine!
> >
> > If, instead of running sshd as a service I just start it from the command
> > line, I do NOT have the problem.
> >
> > Also, if, instead of using the current sshd, I substitute the Okhapkin 
> port
> > of sshd (which I've been using for years), it works fine, even when run as
> > a service (with NO other configuration changes except renaming the sshd
> > executable).
> >
> > I'd really like to upgrade to the OpenSSH port, but have been unable to 
> get
> > around this problem (which prevents me from using the server with sftp or
> > with gui scp programs, since  ls doesn't work). I've made sure that I have
> > current cygwin1.dll, sshd, sh, and ls (and checked to make sure there are
> > no other cygwin1.dlls in my paths).
> >
> > Any thoughts on what I'm doing wrong here?
>
>If you're using an older Cygwin, upgrade to 1.3.1.
>
>If the problem disappears, fine.
>
>If not and if you're using ntsec, set it to nontsec, restart
>your box and try again. I would be interested if that solves
>the hanging problem. Please report back.
>
>Corinna
>
>--
>Corinna Vinschen                  Please, send mails regarding Cygwin to
>Cygwin Developer                                mailto:cygwin AT cygwin DOT com
>Red Hat, Inc.
>
>--
>Want to unsubscribe from this list?
>Check out: http://cygwin.com/ml/#unsubscribe-simple


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple