From owner-freebsd-hackers  Fri Nov 15 08:19:58 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id IAA25486
          for hackers-outgoing; Fri, 15 Nov 1996 08:19:58 -0800 (PST)
Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA25479
          for <hackers@FreeBSD.org>; Fri, 15 Nov 1996 08:19:51 -0800 (PST)
Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id KAA28016; Fri, 15 Nov 1996 10:17:30 -0600
From: Joe Greco <jgreco@brasil.moneng.mei.com>
Message-Id: <199611151617.KAA28016@brasil.moneng.mei.com>
Subject: Re: Sockets question...
To: karl@mcs.net (Karl Denninger)
Date: Fri, 15 Nov 1996 10:17:30 -0600 (CST)
Cc: jgreco@brasil.moneng.mei.com, karl@mcs.net, scrappy@ki.net,
        jdp@polstra.com, hackers@FreeBSD.org
In-Reply-To: <199611151613.KAA21230@Mercury.mcs.net> from "Karl Denninger" at Nov 15, 96 10:13:58 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> > > > Are you checking the return value from write() to make sure it actually
> > > > thinks that N bytes were _written_?
> > > > 
> > > > ... JG
> > > 
> > > Uh, hang on a second...
> > > 
> > > Are you saying that the behavior of a *TCP* connection is such that you
> > > would expect to see a write(2) call to the socket come back with a short
> > > count for any reason other than the remote having closed or some other 
> > > kind of transport error (ie: host unreachable, etc)?
> > 
> > Yes: a nonblocking socket write will most definitely display this
> > behaviour.
> 
> Yes, but I did not set nonblocking mode on that socket.

Did you receive a signal?  That is known to cause similar behaviour on
SunOS...

However, if you received a return value from write() equal to the number
of bytes you supplied to write(), I would state that the problem is
almost certainly elsewhere.

... JG