By now, the following are documented:
fopencookie(3)
freeifaddrs(3)
rawmemchr(3)
readdir_r(3)
getutmp(3)
getutmpx(3)
utmpxname(3)
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554819
Reported-by: Bella Lubkin <filbo@armory.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
These pages used "Copyright Terms"; the other intro.? pages
used "Copyright Conditions". Make these pages like the others.
Reported-by: Yuri Kozlov <yoray@komyakino.ru>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Clarify that this signal really is synonymous with SIGSYS.
See http://bugzilla.kernel.org/show_bug.cgi?id=14449
Reported-by: Garrett Cooper <yaneurabeya@yahoo.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
SUSv3 permits, but does not require CLOCK_THREAD_CPUTIME_ID and
CLOCK_PROCESS_CPUTIME_ID to be settable.
See http://bugzilla.kernel.org/show_bug.cgi?id=11972.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This system call is by design completely unsuitable for any data
integrity operations. Make that very clear in the manpage.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The RFC 822-compliant date format given in the description
of `%z' is now moved to the `EXAMPLES' section (note: `EXAMPLE'
has been renamed `EXAMPLES').
Furthermore, that format example is now actually
RFC 822-compliant (using `%y' instead of `%Y') and has been
qualified as being correct only when in the context of at least
an English locale. Also, `%T' is used in place of `%H:%M:%S'.
For completeness, an RFC 2822-compliant format example has been
similarly added.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
All definitions of the Epoch have been refactored to the following:
1970-01-01 00:00:00 +0000 (UTC)
That form is more consistent, logical, precise, and internationally
recognizable than the other variants.
Also, some wording has been altered as well.
Signed-off-by: Michael Witten <mfwitten@gmail.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The tendency in English, as prescribed in style guides like
Chicago MoS, is towards removing hyphens after prefixes
like "multi-" etc.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The tendency in English, as prescribed in style guides like
Chicago MoS, is towards removing hyphens after prefixes
like "re-" etc.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The tendency in English, as prescribed in style guides like
Chicago MoS, is towards removing hyphens after prefixes
like "pre-" etc.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The tendency in English, as prescribed in style guides like
Chicago MoS, is towards removing hyphens after prefixes
like "sub-" etc.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The tendency in English, as prescribed in style guides like
Chicago MoS, is towards removing hyphens after prefixes
like "non-" etc.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The tendency in English, as prescribed in style guides like
Chicago MoS, is towards removing hyphens after prefixes
like "non-" etc.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The tendency in English, as prescribed in style guides like
Chicago MoS, is towards removing hyphens after prefixes
like "non-" etc.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The tendency in English, as prescribed in style guides like
Chicago MoS, is towards removing hyphens after prefixes
like "non-" etc.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>