Remove $FreeBSD$: one-line nroff pattern

Remove /^\.\\"\s*\$FreeBSD\$$\n/

Renumber copyright clause 4

Renumber cluase 4 to 3, per what everybody else did when BSD granted
them permission to remove clause 3. My insistance on keeping the same
numbering for legal reasons is

Renumber copyright clause 4

Renumber cluase 4 to 3, per what everybody else did when BSD granted
them permission to remove clause 3. My insistance on keeping the same
numbering for legal reasons is too pedantic, so give up on that point.

Submitted by: Jan Schaumann <[email protected]>
Pull Request: https://github.com/freebsd/freebsd/pull/96

show more ...

accept(2) may and can return EAGAIN, document it.

MFC after: 1 week

Add some missing .Nm for newer syscalls in existing man pages.

MFC after: 1 week

accept(2): Update portability note for accept4().

The accept(2) man page warns that O_NONBLOCK and other properties on the
new socket may vary across implementations. However, this issue only
applie

accept(2): Update portability note for accept4().

The accept(2) man page warns that O_NONBLOCK and other properties on the
new socket may vary across implementations. However, this issue only
applies to accept() and not to accept4(). On the other hand, accept4()
is not commonly available yet.

Reported by: pluknet
Reviewed by: bjk
Approved by: re (kib)

show more ...

accept(2), pipe(2): Fix .Dd.

Add accept4() system call.

The accept4() function, compared to accept(), allows setting the new file
descriptor atomically close-on-exec and explicitly controlling the
non-blocking status on the new

Add accept4() system call.

The accept4() function, compared to accept(), allows setting the new file
descriptor atomically close-on-exec and explicitly controlling the
non-blocking status on the new socket. (Note that the latter point means
that accept() is not equivalent to any form of accept4().)

The linuxulator's accept4 implementation leaves a race window where the new
file descriptor is not close-on-exec because it calls sys_accept(). This
implementation leaves no such race window (by using falloc() flags). The
linuxulator could be fixed and simplified by using the new code.

Like accept(), accept4() is async-signal-safe, a cancellation point and
permitted in capability mode.

show more ...

Keep up with negative addrlen check removal in r249649.

accept(2): Mention inheritance of O_ASYNC and signal destination.

While almost nobody uses O_ASYNC, and rightly so, the inheritance of the
related properties across accept() is a portability issue l

accept(2): Mention inheritance of O_ASYNC and signal destination.

While almost nobody uses O_ASYNC, and rightly so, the inheritance of the
related properties across accept() is a portability issue like the
inheritance of O_NONBLOCK.

show more ...

Attempt to reduce accidental foot-shooting by pointing out that
accept(2)ed sockets do not necessarily inherit O_NONBLOCK from
listening sockets on non-FreeBSD platforms.

Feet shot: cperciva
MFC aft

Attempt to reduce accidental foot-shooting by pointing out that
accept(2)ed sockets do not necessarily inherit O_NONBLOCK from
listening sockets on non-FreeBSD platforms.

Feet shot: cperciva
MFC after: 1 month

show more ...

Add Xr to getsockname(2)

Per Regents of the University of Calfornia letter, remove advertising
clause.

# If I've done so improperly on a file, please let me know.

Document the fact that accept(2) may return EINVAL when addrlen is
negative (in addition to returning EINVAL when called on a descriptor
that is not a socket).

Submitted by: Arne H Juul <arnej@europ

Document the fact that accept(2) may return EINVAL when addrlen is
negative (in addition to returning EINVAL when called on a descriptor
that is not a socket).

Submitted by: Arne H Juul <[email protected]>
PR: docs/80587

show more ...

Mechanically kill hard sentence breaks.

Be specific about which socket properties are inherited from the original
socket upon accept(2).

PR: docs/54995, kern/45733

Add restrict qualifiers. (docs)

PR: 44394
Submitted by: Craig Rodrigues <[email protected]>

Clarify that the second argument to accept() may be a null pointer if
no peer address information is desired.

PR: 56044
Submitted by: Felix Opatz <[email protected]> and
Bernd Luevelsmeyer <bdl

Clarify that the second argument to accept() may be a null pointer if
no peer address information is desired.

PR: 56044
Submitted by: Felix Opatz <[email protected]> and
Bernd Luevelsmeyer <[email protected]>
MFC after: 1 month

show more ...

mdoc(7) police: "The .Fa argument.".

mdoc(7) police: Tidy up the syscall language.

Stop calling system calls "function calls".

Use "The .Fn system call" a-la "The .Nm utility".

When referring to a non-BSD implementation in
the HISTOR

mdoc(7) police: Tidy up the syscall language.

Stop calling system calls "function calls".

Use "The .Fn system call" a-la "The .Nm utility".

When referring to a non-BSD implementation in
the HISTORY section, call syscall a function,
to be safe.

show more ...

mdoc(7) police: sort xrefs.

Some updates to mention accept filters and how
listen queues work in a syncache world.

MFC after: 3 days

Nuke the paragraph that says "One can obtain user connection request
data without confirming the connection by issuing a recvmsg(2) [...]".
There's no such code in the kernel.

PR: 26861
Submitted b

Nuke the paragraph that says "One can obtain user connection request
data without confirming the connection by issuing a recvmsg(2) [...]".
There's no such code in the kernel.

PR: 26861
Submitted by: Richard A Steenbergen <[email protected]>,
Tom Rhodes <[email protected]>

show more ...

Remove the internal implementation details of wrapping syscalls,
which do not match the reality anyway.

Approved by: deischen, bde

mdoc(7) police: Use the new .In macro for #include statements.

mdoc(7) police: removed HISTORY info from the .Os call.