The close(2) manpage does not list ENOTCONN as a possible error return, yet I have just received it. 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. How-To-Repeat: Not sure.
Responsible Changed From-To: freebsd-doc->eadler I'll take it.
Responsible Changed From-To: eadler->freebsd-doc I won't be looking at this PR for a while and I need to clear some out of my queue
For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped