Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Mon, 28 May 2001 11:35:38 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: ssh hanging--a workaround Message-ID: <20010528113538.A7365@cygbert.vinschen.de> Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from karlm30@hotmail.com on Sat, May 26, 2001 at 02:22:15PM -0700 On Sat, May 26, 2001 at 02:22:15PM -0700, Karl M wrote: > I forced select to return by setting a timeout. The > timeout does force it to return--and in fact, there is IO waiting to be > processed. You're telling that IO is available so select should return but it doesn't? > It is not an ssh bug as far as I can tell. No, it seems to be a Cygwin problem. > Also, in the past, I needed pipes and you did not. Now we all have pipes. > But why do you think that in the past, I needed pipes and you did not? Dunno. Since I never had a problem using socketpair on my machines I could never reproduce that. I'm using pipes instead of socketpairs by default now because pipes seem to work for nearly all people and pipes are way faster than socketpairs, at least on W2K. 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