From owner-freebsd-hackers Thu Jul 29 7:57: 9 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 BC7FD14E98 for ; Thu, 29 Jul 1999 07:56:48 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from [204.68.178.224] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #1) id 119rbI-0004GF-00; Thu, 29 Jul 1999 08:56:07 -0600 Message-ID: <37A06B6B.B5BF74CF@softweyr.com> Date: Thu, 29 Jul 1999 08:55:39 -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: hackers@FreeBSD.ORG Subject: Re: Documenting writev(2) ENOBUFS error References: <19990728170119.A47890@kilt.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: > > -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