accept.2: Demote discussion of DECNet to NOTES

DECNet ceased to be important long ago...

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2016-08-23 10:03:31 +12:00
parent cb1bcdf28c
commit ccdf8bc04f
1 changed files with 14 additions and 13 deletions

View File

@ -137,19 +137,6 @@ Alternatively, you can set the socket to deliver
when activity occurs on a socket; see
.BR socket (7)
for details.
.PP
For certain protocols which require an explicit confirmation,
such as
DECNet,
.BR accept ()
can be thought of as merely dequeuing the next connection request and not
implying confirmation.
Confirmation can be implied by
a normal read or write on the new file descriptor, and rejection can be
implied by closing the new socket.
Currently, only
DECNet
has these semantics on Linux.
If
.IR flags
@ -354,6 +341,20 @@ needs to have the
.B O_NONBLOCK
flag set (see
.BR socket (7)).
For certain protocols which require an explicit confirmation,
such as
DECNet,
.BR accept ()
can be thought of as merely dequeuing the next connection request and not
implying confirmation.
Confirmation can be implied by
a normal read or write on the new file descriptor, and rejection can be
implied by closing the new socket.
Currently, only
DECNet
has these semantics on Linux.
.\"
.SS The socklen_t type
The third argument of
.BR accept ()