[src/trunk]: src/lib/libc/sys compatibility note

[yamt <yamt%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/319fd0e6549b
branches:  trunk
changeset: 765671:319fd0e6549b
user:      yamt <yamt%NetBSD.org@localhost>
date:      Thu Jun 02 01:04:18 2011 +0000

description:
compatibility note

diffstat:

 lib/libc/sys/accept.2 |  13 +++++++++++--
 1 files changed, 11 insertions(+), 2 deletions(-)

diffs (34 lines):

diff -r 14c82f706da1 -r 319fd0e6549b lib/libc/sys/accept.2
--- a/lib/libc/sys/accept.2     Thu Jun 02 00:58:26 2011 +0000
+++ b/lib/libc/sys/accept.2     Thu Jun 02 01:04:18 2011 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: accept.2,v 1.25 2006/11/17 23:59:33 rillig Exp $
+.\"    $NetBSD: accept.2,v 1.26 2011/06/02 01:04:18 yamt Exp $
 .\"
 .\" Copyright (c) 1983, 1990, 1991, 1993
 .\"    The Regents of the University of California.  All rights reserved.
@@ -29,7 +29,7 @@
 .\"
 .\"     @(#)accept.2   8.2 (Berkeley) 12/11/93
 .\"
-.Dd November 18, 2006
+.Dd June 2, 2011
 .Dt ACCEPT 2
 .Os
 .Sh NAME
@@ -135,6 +135,15 @@
 The call returns \-1 on error.
 If it succeeds, it returns a non-negative
 integer that is a descriptor for the accepted socket.
+.Sh COMPATIBILITY
+This implementation makes the new file descriptor inherit file flags
+(like
+.Dv O_NONBLOCK )
+from the listening socket.
+It's a traditional behaviour for BSD derivative systems.
+On the other hand, there are implementations which don't do so.
+Linux is an example of such implementations.
+Portable programs should not rely on either of the behaviours.
 .Sh ERRORS
 The
 .Fn accept