Date: Thu, 29 Jul 1999 08:55:39 -0600 From: Wes Peters <wes@softweyr.com> To: Nik Clayton <nik@nothing-going-on.demon.co.uk> Cc: hackers@FreeBSD.ORG Subject: Re: Documenting writev(2) ENOBUFS error Message-ID: <37A06B6B.B5BF74CF@softweyr.com> References: <19990728170119.A47890@kilt.nothing-going-on.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Nik Clayton wrote:
>
> -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.
How does this look:
[ENOBUFS] Insufficient system buffer space exists to complete the op-
eration.
Here's the patch against -current:
--- write.2 Tue Jul 13 06:53:41 1999
+++ /home/wes/src/write.2 Thu Jul 29 08:49:54 1999
@@ -242,6 +242,8 @@
values in the
.Fa iov
array overflowed a 32-bit integer.
+.It Bq Er ENOBUFS
+Insufficient system buffer space exists to complete the operation.
.El
.Pp
The
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
http://softweyr.com/ wes@softweyr.com
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?37A06B6B.B5BF74CF>