Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Date: Tue, 16 Aug 2005 11:33:29 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: openssh-4.1p1-2/cygwin-1.5.18-1: write(2) misbehaving?
Message-ID: <20050816093329.GA11102@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CB0EAF8A515FC4488F2B4B546BEE012CA0EAEF AT islexch2k DOT isllcnets DOT studentloan DOT org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CB0EAF8A515FC4488F2B4B546BEE012CA0EAEF@islexch2k.isllcnets.studentloan.org>
User-Agent: Mutt/1.4.2i

On Aug 15 19:57, Dave Kilzer wrote:
> 2. Apply the attached patch and (re)build openssh.  After reading the
> manpage for write(2), it said that write(2) returns -1 on error, thus
> errno will not contain a "related" error if checked when write(2)
> returns 0.  (There were other mitigating circumstances when writing to
> "real" files according to the manpage, but this did not apply.)  The
> fact that this patch works tells me that write(2) seems to be broken,
> and is actually returning 0 when it should be returning a positive
> integer (e.g., the value of "len" in this case).
> 
> Note that I tried running "ssh.exe" from openssh-3.9p1-3/cygwin-1.5.13-1
> with cygwin-1.5.18-1, and it had the exact same problem.  (I have not
> tried compiling openssh-4.1p1-2 on the system running cygwin-1.5.13-1
> yet, though.)
> 
> Any idea what's going on?

Not exactly, but I'm suspecting a specific piece of code in Cygwin.  The
problem is that I can't reproduce this problem.  Using ssh to access other
machines works fine for me, high traffic is also no problem.

So, first step, could you please try the latest snapshot DLL from
http://cygwin.com/snapshots/ and see if the problem persists?  If so,
we will have to do some debugging together.



Corinna

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

--
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/