Date: Wed, 28 Jul 1999 17:01:19 +0100 From: Nik Clayton <nik@nothing-going-on.demon.co.uk> To: hackers@freebsd.org Subject: Documenting writev(2) ENOBUFS error Message-ID: <19990728170119.A47890@kilt.nothing-going-on.org>
next in thread | raw e-mail | index | archive | help
-hackers,
Could someone who knows write/writev(2) take a quick look at docs/10512.
In essence, writev(2) can fail with ENOBUFS if (and I quote from the PR)
if you "exhaust writev'able buffer space". This doesn't mean a great
deal to me, and I'm hoping one of you can take a look at come up with a
phrasing suitable for a man page.
Cheers,
N
--
[intentional self-reference] can be easily accommodated using a blessed,
non-self-referential dummy head-node whose own object destructor severs
the links.
-- Tom Christiansen in <375143b5@cs.colorado.edu>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990728170119.A47890>