Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Message-ID: <001701c13548$0f4b6000$59b4b080@unimuenster.de>
From: "Frank Wuebbeling" <wuebbel@math.uni-muenster.de>
To: "Corinna Vinschen" <cygwin@cygwin.com>
References: <003d01c1336e$26b8d0f0$0200000a@dyn.ik.ca> <001b01c1352c$f9f1efa0$0100a8c0@duron> <20010904123906.C2419@cygbert.vinschen.de>
Subject: Re: On Win98, connections hang when using remote command execution with SSHD.
Date: Tue, 4 Sep 2001 15:46:51 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200

Corinna,
> Not a solution, just a guess. Try a developers snapshot of Cygwin.
> It's not that likely to help since the problem is probably induced
> by the crappy pipe handling of 9x/ME, but...
I tried it, but it makes things even worse (*if* I did it right). I took
cygwin1.dll and put it into /usr/bin, nothing else, I did no recompilation.
Here's the report:

I use the following batch file in the Startup folder to start sshd on
Windows startup:
================
@echo off
D:
chdir \programme\cygwin\bin
bash --login -c /usr/sbin/sshd.exe
================
With the old cygwin1.dll, the DOS-Window in which this batchfile is started,
never vanishes. I checked "close window on exit" for the batchfile, but no
result. With the new cygwin1.dll, the DOS-Window actually goes away after
sshd backgrounds, which it should. So this is the good news.

The bad news is that sshd still sleeps after having completed exactly 8
connections. I can't open any new connections to this sshd, so this
behaviour didn't change with the new version. But in the old version I could
kill sshd, start a new one, and I could try again for 8 connections. With
the new version of cygwin1.dll, I can't even restart after killing sshd, the
newly-started sshd never gets a connection.

My current solution to the problem, by the way, is to run sshd from inetd
(with the old library, of course), which may be inefficient, but works.

Frank


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

