Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Delivered-To:	corinna-cygwin AT cygwin DOT com
Message-ID:	<f02230868fe32e7c2dbbfc5a249723dd@snellwilcox.com>
Date:	Thu, 17 Apr 2003 12:14:47 +0100
From:	steve DOT simon AT snellwilcox DOT com
To:	cygwin AT cygwin DOT com, corinna-cygwin AT cygwin DOT com
Subject:	Re: Re: cygwin + sshd = nagle?
MIME-Version:	1.0

Hi,

Appologies for not being clear.

I was indeed surprised to find nagle was being turned off when I asked for
a non-interactive session - this is contarary to my understanding of ssh.

My concern was/is that though the debug printouts imply nagle is being turned
I think it is left on. I beleive this because I am getting peformance comensurate
nagle enabled even when ssh's debug assures me it has been disabled.

I am interested to know if the reason nagle is left on is because sshd assumes
the socket on its standard input is a real socket whereas under cygwin the socket
may have already been replaced with a pipe by the underlieing cygwin DLL.

I suspose what I'am asking is where is the pipe implemented in cygwin, is
it between an Inetd like application (sshd would be similar to inetd in this respect)
or is it implemented in the exec wrapper?

I am not trying to report a bug mearly trying to understand how sshd is working
and how to make my application work.

-Steve

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -