From owner-freebsd-hackers Mon Aug 2 23: 6:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id 114051523D; Mon, 2 Aug 1999 23:06:29 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #1) id 11BXgn-0006HC-00; Tue, 3 Aug 1999 00:04:42 -0600 Message-ID: <37A6867E.F85C69A8@softweyr.com> Date: Tue, 03 Aug 1999 00:04:46 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Nik Clayton Cc: Ville-Pertti Keinonen , dillon@apollo.backplane.com, hackers@FreeBSD.ORG Subject: Re: Documenting writev(2) ENOBUFS error References: <19990731082450.7417.qmail@ns.oeno.com> <37A399C1.43B5154E@softweyr.com> <19990801105855.A67372@catkin.nothing-going-on.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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