From owner-freebsd-hackers Sat Jul 31 18:57:11 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 9F8E114E7B for ; Sat, 31 Jul 1999 18:57:09 -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 11Akqm-0002Mu-00; Sat, 31 Jul 1999 19:55:45 -0600 Message-ID: <37A399C1.43B5154E@softweyr.com> Date: Sat, 31 Jul 1999 18:50:09 -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: Ville-Pertti Keinonen Cc: dillon@apollo.backplane.com, hackers@FreeBSD.ORG Subject: Re: Documenting writev(2) ENOBUFS error References: <19990731082450.7417.qmail@ns.oeno.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ville-Pertti Keinonen wrote: > > > :wes@softweyr.com (Wes Peters) writes: > > : > > :> [ENOBUFS] Insufficient system buffer space exists to complete the op- > > :> eration. > > : > > :Do you know what kind of circumstances that error *really* occurs > > :under? > > So you can get ENOBUFS not related to mbufs for UDP/local datagram > sockets, but you should never get ENOBUFS from write for TCP sockets > or local stream sockets. 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. -- "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