Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Tue, 10 Jul 2001 17:27:32 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: ssh stalls after completion of command Message-ID: <20010710172732.T8578@cygbert.vinschen.de> Mail-Followup-To: cygwin@cygwin.com References: <001901c1093b$871c8c00$59b4b080@unimuenster.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <001901c1093b$871c8c00$59b4b080@unimuenster.de>; from wuebbel@math.uni-muenster.de on Tue, Jul 10, 2001 at 02:26:21PM +0200 On Tue, Jul 10, 2001 at 02:26:21PM +0200, Frank Wuebbeling wrote: > I'm trying to execute a single remote command on a Windows95 host with sshd > running, from a LINUX box. While the command executes correctly, the prompt > does not return (the connection is not given up), I have to press CTRL-C in > the LINUX window to get my prompt back. The same thing happens when I log in > from the local Windows95 box to itself: > > ssh -v localhost id It's a known OpenSSH problem on various systems. I'm not sure if the current 2.9p2 shows the same behaviour since I didn't follow the OpenSSH developers mailing list during vacation. Moreover there's still another problem in Cygwin related to select() calls on pipes which nobody could track down to date. Perhaps you have a chance when you compile OpenSSH by yourself using socketpairs instead of pipes. Unfortunately socketpairs are way slower and they don't work on all systems apparently. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/