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: Fri, 29 Dec 2000 22:30:05 +0100 From: Corinna Vinschen To: cygwin Subject: Re: Openssh 2.3.0p1 weird exec problem, cont. Message-ID: <20001229223005.E4278@cygbert.vinschen.de> Mail-Followup-To: cygwin 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 jpollock@curl.com on Fri, Dec 29, 2000 at 03:59:12PM -0500 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 -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple