Date: Fri, 23 Nov 2007 10:14:45 GMT From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: FreeBSD-gnats-submit@FreeBSD.org Subject: docs/118214: close(2) error returns incomplete Message-ID: <200711231014.lANAEjqU004027@critter.freebsd.dk> Resent-Message-ID: <200711231040.lANAe4MJ036061@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 118214 >Category: docs >Synopsis: close(2) error returns incomplete >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Fri Nov 23 10:40:04 UTC 2007 >Closed-Date: >Last-Modified: >Originator: Poul-Henning Kamp >Release: FreeBSD 8.0-CURRENT i386 >Organization: >Environment: System: FreeBSD critter.freebsd.dk 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Mon Nov 5 00:09:37 UTC 2007 root@critter.freebsd.dk:/usr/obj/freebsd/src/sys/C5 i386 >Description: The close(2) manpage does not list ENOTCONN as a possible error return, yet I have just received it. >How-To-Repeat: Not sure. >Fix: It may be relevant to split the ERRORS section into sections: generic errors that all fd's can give, and subsystem specific errors that can only come from pipes, devices or sockets. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200711231014.lANAEjqU004027>