From: bailey9@marshall.edu
To: cygwin <cygwin@cygwin.com>
Subject: Re: Openssh 2.3.0p1 weird exec problem, cont.
Date: Tue, 02 Jan 2001 08:27:00 -0000 [thread overview]
Message-ID: <20010102112906.B10372@marshall.edu> (raw)
In-Reply-To: <20001230200044.E882@cobold.vinschen.de>
On Sat, Dec 30, 2000 at 08:00:44PM +0100, Corinna Vinschen wrote:
> On Fri, Dec 29, 2000 at 05:21:07PM -0500, bailey9@akamai.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@cygwin.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
next prev parent reply other threads:[~2001-01-02 8:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-29 12:59 John Pollock
2000-12-29 13:30 ` Corinna Vinschen
2000-12-29 14:20 ` bailey9
2000-12-30 11:00 ` Corinna Vinschen
2001-01-02 8:27 ` bailey9 [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-05 10:49 Ed Eden
2001-01-05 6:30 Ed Eden
2000-12-30 15:11 R v D
2000-12-29 12:18 bailey9
2000-12-29 13:19 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010102112906.B10372@marshall.edu \
--to=bailey9@marshall.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).