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
Date: Tue, 2 Jan 2001 11:29:08 -0500
From: bailey9 AT marshall DOT edu
To: cygwin <cygwin AT cygwin DOT com>
Subject: Re: Openssh 2.3.0p1 weird exec problem, cont.
Message-ID: <20010102112906.B10372@marshall.edu>
References: <Pine DOT LNX DOT 4 DOT 30 DOT 0012291553380 DOT 11220-100000 AT terror DOT curl DOT com> <20001229223005 DOT E4278 AT cygbert DOT vinschen DOT de> <20001229172106 DOT B1194 AT akamai DOT com> <20001230200044 DOT E882 AT cobold DOT vinschen DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001230200044.E882@cobold.vinschen.de>; from cygwin@cygwin.com on Sat, Dec 30, 2000 at 08:00:44PM +0100

On Sat, Dec 30, 2000 at 08:00:44PM +0100, Corinna Vinschen wrote:
> On Fri, Dec 29, 2000 at 05:21:07PM -0500, bailey9 AT akamai DOT com wrote:
> > That seems to solve the problem for me. Thanks!
> 
> You _did_ recompile OpenSSH with USE_PIPES and that solves
> actually the problem? I'm just asking to be really sure.
> 
> Corinna
> 

 Yup, compiling with USE_PIPES defined eliminates the problem of sometimes 
not getting output from exec'd commands. I haven't tested interactive mode
extensively but at least superficially everything seems to work ok.

 .andy


> > > On Fri, Dec 29, 2000 at 03:59:12PM -0500, John Pollock wrote:
> > > > However, i've only seen this issue with non-cygwin apps (like VC++ and
> > > > such) which don't seem to understand how to send output reliably when
> > > > cooperating with a version of ssh using socket pairs instead of pipes.
> > > > The cygwin version of openssh, i believe ,uses socket pairs and not pipes,
> > > > which may be the source of the problem.
> > > 
> > > That's an interesting point. socket pairs are prefered over pipes in
> > > OpenSSH. Using pipes is a special option. I'm currently on vacation
> > > and need the time for my move to another town. If somebody is willing
> > > to build OpenSSH using pipes and test that situation again I would
> > > gladly appreciate this.
> > > 
> > > Using pipes instead of socket pairs is easy: After configuring just
> > > open `defines.h', goto line 378 and remove the comments from this
> > > line containing `#define USE_PIPES 1', then make. If that solves the
> > > problem (and still works in all other situations) I will release
> > > a new Cygwin version of OpenSSH then.
> 
> -- 
> 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