Date: Tue, 03 Aug 1999 00:04:46 -0600 From: Wes Peters <wes@softweyr.com> To: Nik Clayton <nik@FreeBSD.ORG> Cc: Ville-Pertti Keinonen <will@iki.fi>, dillon@apollo.backplane.com, hackers@FreeBSD.ORG Subject: Re: Documenting writev(2) ENOBUFS error Message-ID: <37A6867E.F85C69A8@softweyr.com> References: <19990731082450.7417.qmail@ns.oeno.com> <37A399C1.43B5154E@softweyr.com> <19990801105855.A67372@catkin.nothing-going-on.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Nik Clayton wrote:
>
> On Sat, Jul 31, 1999 at 06:50:09PM -0600, Wes Peters wrote:
> > So, do you want to enumerate the cases in which this error can occur in the
> > man page? This is not generally done, now that we have verified it is
> > possible for the system to generate ENOBUFS on a writev. I think the text
> > stands as it is.
>
> FWIW, I committed:
>
> [ENOBUFS] The mbuf pool has been completely exhausted when writing to
> a socket
Mmmm. Yummy.
Do we want to mention that one or more of the vectors may have been written
before the failure occurred, or is that OTTMCO? ;^)
--
"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?37A6867E.F85C69A8>