From owner-freebsd-hackers Sun Aug 1 12:56:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 0CF2914E44 for ; Sun, 1 Aug 1999 12:56:42 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id KAA67609; Sun, 1 Aug 1999 10:58:55 +0100 (BST) (envelope-from nik) Date: Sun, 1 Aug 1999 10:58:55 +0100 From: Nik Clayton To: Wes Peters Cc: Ville-Pertti Keinonen , dillon@apollo.backplane.com, hackers@FreeBSD.ORG Subject: Re: Documenting writev(2) ENOBUFS error Message-ID: <19990801105855.A67372@catkin.nothing-going-on.org> References: <19990731082450.7417.qmail@ns.oeno.com> <37A399C1.43B5154E@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <37A399C1.43B5154E@softweyr.com>; from Wes Peters on Sat, Jul 31, 1999 at 06:50:09PM -0600 Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 ... 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