From owner-freebsd-hackers Wed Jul 28 13: 4:44 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 2A43B153FF for ; Wed, 28 Jul 1999 13:04:39 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: from kilt.nothing-going-on.org (kilt.nothing-going-on.org [192.168.1.18]) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) with ESMTP id UAA66629 for ; Wed, 28 Jul 1999 20:56:08 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Received: (from nik@localhost) by kilt.nothing-going-on.org (8.9.3/8.9.3) id RAA48822 for hackers@freebsd.org; Wed, 28 Jul 1999 17:01:20 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Date: Wed, 28 Jul 1999 17:01:19 +0100 From: Nik Clayton To: hackers@freebsd.org Subject: Documenting writev(2) ENOBUFS error Message-ID: <19990728170119.A47890@kilt.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -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. Cheers, 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