Because of the "sem." prefix added by glibc to a semaphore
name, the limit on the length of the name (excluding the
terminating null byte) is 251 characters.
Reported-by: Jens Thoms Toerring <jt@toerring.de>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
ISO 8602 week-based dates are relevant for %G, %g, and %V,
and the existing details on these dates are a little thin.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The text mentioned the 1988 8601 standard, but there have
already been two revisions of the standard since then, so
simply remove mention of the year.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
No actual change to formatted output, but this makes the
page sources more consistent for the purpose of grepping, etc.
Reported-by: Sam Varshavchik <mrsam@courier-mta.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
For a non-blocking socket, POSIX.1-2001/2008 allow either
EAGAIN or EWOULDBLOCK to be returned in cases where a call
would have blocked. Although these constants are defined
with the same value on most Linux architectures (PA-RISC
is the exception), POSIX.1 does not require them to have
the same value. Therefore, a portable application using
the sockets API should test for both errors when checking
this case.
(NB POSIX.1 only mentions EWOULDBLOCK in the context of
the sockets interfaces.)
Change made after a note cross-posted on linux-arch@vger,
http://thread.gmane.org/gmane.linux.debian.ports.hppa/5615
and a suggestion for write(2) from Carlos O'Donell
Reported-by: Carlos O'Donell <carlos@systemhalted.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
In the kernel, the error on encountering a mandatory lock is
EAGAIN. Although EAGAIN and EWOULDBLOCK are the same on
most Linux architectures, on some they are not, so don't
mention EWOULDBLOCK as it is misleading. (Mea culpa.)
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The SYNOPSIS showed the right function name (getnetbyaddr_r),
but the text repeatedly used the wrong name (getnetbynumber_r).
Probably, this was a cut-and-paste error.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Although the page already mentioned the resolved_path==NULL
feature, and that this feature was added in POSIX.1-2008, there
was still some crufty text in BUGS that hadn't been updated to
reflect the POSIX.1-2008 changes.
Also, some other minor wording and grammar fixes.
Reported-by: Reuben Thomas <rrt@femur.dyndns.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Target file cannot be opened in append (O_APPEND) mode
In kernels prior to v2.6.27 splice() to a file in append mode is broken,
and since that version it is disallowed. It is possible this behaviour
may change in the future; see the kernel commit message
(efc968d450e013049a662d22727cf132618dcb2f) for more information.
Signed-off-by: Mark Hills <mark@pogo.org.uk>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Michael Kerrisk