From nobody@FreeBSD.ORG Tue Mar  9 11:28:02 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 34545150D0; Tue,  9 Mar 1999 11:27:55 -0800 (PST)
Message-Id: <19990309192755.34545150D0@hub.freebsd.org>
Date: Tue,  9 Mar 1999 11:27:55 -0800 (PST)
From: hgoldst@mpcs.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: ENOBUFS returnable from writev(2) but not documented
X-Send-Pr-Version: www-1.0

>Number:         10512
>Category:       docs
>Synopsis:       ENOBUFS returnable from writev(2) but not documented
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Mar  9 11:30:00 PST 1999
>Closed-Date:    Fri Jul 30 14:20:11 PDT 1999
>Last-Modified:  Fri Jul 30 14:20:41 PDT 1999
>Originator:     howard goldstein
>Release:        3.1-R
>Organization:
>Environment:
FreeBSD slice 3.1-RELEASE FreeBSD 3.1-RELEASE #0: Tue Mar  2 10:13:03 EST 1999     hg@slice:/usr/src/sys/compile/SLICE  i386

>Description:
Pretty much the same as the summary.  ENOBUFS is a returnable
errno from a writev(2) call but is not documented in the man page.
>How-To-Repeat:
Exhaust writev'able buffer space.  The fd may need to be a
unix domain datagram socket, I've only seen it in that context.
>Fix:
assuming this action is correct then update docs

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: nik 
State-Changed-When: Fri Jul 30 14:20:11 PDT 1999 
State-Changed-Why:  
Document the error in write(2).  Thanks for the pointer. 
>Unformatted:
