Added the following text to answer PR 7249:

The manual page for each system call will list some of the
	common errno codes that system call can return, but that
	should not be considered an exhaustive list, i.e.  a properly
	written program should be able to gracefully recover from
	any error that a system call might return.  Documenting
	all the error codes that a system call can return in a more
	specification-like manner would take more resources than
	this project has available.
This commit is contained in:
fair 2001-03-16 06:56:48 +00:00
parent fb3c4927d6
commit bee514872a
1 changed files with 10 additions and 1 deletions

View File

@ -1,4 +1,4 @@
.\" $NetBSD: intro.2,v 1.23 2001/03/13 03:24:13 fair Exp $ .\" $NetBSD: intro.2,v 1.24 2001/03/16 06:56:48 fair Exp $
.\" .\"
.\" Copyright (c) 1980, 1983, 1986, 1991, 1993 .\" Copyright (c) 1980, 1983, 1986, 1991, 1993
.\" The Regents of the University of California. All rights reserved. .\" The Regents of the University of California. All rights reserved.
@ -73,6 +73,15 @@ Note that a number of system calls overload the meanings of these
error numbers, and that the meanings must be interpreted according error numbers, and that the meanings must be interpreted according
to the type and circumstances of the call. to the type and circumstances of the call.
.Pp .Pp
The manual page for each system call will list some of the common
errno codes that system call can return, but that should not be
considered an exhaustive list, i.e.
a properly written program should be able to gracefully recover from
any error that a system call might return.
Documenting all the error codes that a system call can return in
a more specification-like manner would take more resources than
this project has available.
.Pp
The following is a complete list of the errors and their The following is a complete list of the errors and their
names as given in names as given in
.Aq Pa errno.h . .Aq Pa errno.h .