delorie.com/archives/browse.cgi | search |
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: | Fri, 29 Dec 2000 15:59:12 -0500 (EST) |
From: | John Pollock <jpollock AT curl DOT com> |
To: | <cygwin AT sourceware DOT cygnus DOT com> |
Subject: | RE: Openssh 2.3.0p1 weird exec problem, cont. |
Message-ID: | <Pine.LNX.4.30.0012291553380.11220-100000@terror.curl.com> |
MIME-Version: | 1.0 |
i've been seeing this exact issue too and only recently learned to pipe output through cat if i want to expect to see it reliably come back. A command repeated 30 times will return the correct output about 10 times, and then a variety of other outputs the other 20 times. 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. J -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |