Re: writev() BUGS!

Jim Nance (jlnance@sailboat.mis.uncwil.edu)
Thu, 3 Jun 1999 00:25:31 -0400


On Wed, Jun 02, 1999 at 11:30:50PM +0000, Jens-Uwe Mager wrote:

> Uhm, are you sure? I have never seen that behaviour on any
> other Unix. If a socket is in blocking mode, writev (or send)
> is supposed to sleep until all is send or an error occurs. I
> would believe a lot software would break if write returned partial
> results on blocking software. On the reading side the bahaviour is
> known and the applications compensate for that. The description at
> <http://www.opengroup.org/onlinepubs/007908799/xns/send.html> makes me
> believe that write/send shouldn't do partial things on blocking sockets.

I thought you were wrong, but now I think you are right (at least wrt Digital
Unix). Here is the Digital Unix man page:

http://alisa.ucsd.edu/cgi/webman?SEARCH+man2+write.2.gz

Jim

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/