This is the mail archive of the cygwin-patches@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Fwd: 1.5.11-1: sftp performance problem]


On Sep 11 13:24, Bob Byrnes wrote:
> On Sep 11,  3:02pm, Corinna Vinschen wrote:
> -- Subject: Re: [Fwd: 1.5.11-1: sftp performance problem]
> >
> > http://cygwin.com/acronyms/#PCYMTNQREAIYR
> 
> Sorry ... done.
> 
> > | One really annoying consequence of socketpairs for sshd is that
> > | Windows-native (i.e. non-Cygwin) programs don't know how to write
> > | directly to sockets on stdout (or stderr), so if you try to use
> > | them via ssh, their output silently disappears.
> > 
> > Oh lord!  I tried it with `net', `ping' and `nslookup', which are roughly
> > the only Windows applications I use on the command line, and all three
> > have no problems.  I'm wondering how the above can happen since the
> > interactive application side is running in a PTY (which *is* a pipe),
> > not on socketpairs.
> 
> Try it without a pty:
> 
>     ssh cygwin-system-with-sshd-using-sockpairs "win32-native-command"
> 
> vs.
> 
>     ssh cygwin-system-with-sshd-using-sockpairs "win32-native-command | cat"

Yeah, sure.  But native apps are not our first concern and the above can
also easily be done with

  ssh -t cygwin-system-with-sshd-using-sockpairs "win32-native-command"

> And we'd still have the problem with win32-native apps, which I think
> is a show-stopper for socketpairs.

I'm actually in doubt that this should be a showstopper.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin@cygwin.com
Red Hat, Inc.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]