-==================== Changes in man-pages-3.68 ====================
+==================== Changes in man-pages-3.75 ====================
-Released: 2014-05-28, Munich
+Released: 2014-10-15, Düsseldorf
-Alastair McKinstry <mckinstry@computer.org>
-Carsten Grohmann <carstengrohmann@gmx.de>
-Colin Williams <colinwilliams1968@gmail.com>
-Heinrich Schuchardt <xypron.glpk@gmx.de>
-Lars Wirzenius <liw@iki.fi>
-Marko Myllynen <myllynen@redhat.com>
-Michael Kerrisk <mtk.manpages@gmail.com>
-Peng Haitao <penght@cn.fujitsu.com>
-Rasmus Villemoes <rv@rasmusvillemoes.dk>
-Richard Braakman <richard.braakman@jollamobile.com>
-Simon Paillard <spaillard@debian.org>
Contributors
------------
in the changelog below) reports, notes, and ideas that have been
incorporated in changes in this release:
+Jonny Grant <jg@jguk.org>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Robert Schweikert <rjschwei@suse.com>
+Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
+Walter Harms <wharms@bfs.de>
Apologies if I missed anyone!
New and rewritten pages
-----------------------
-localedef.1
- Marko Myllynen [Richard Braakman, Alastair McKinstry, Lars Wirzenius]
- New page for localedef(1)
- Add new page based on Debian localedef(1) page.
+pthread_rwlockattr_setkind_np.3
+ Robert Schweikert [MMichael Kerrisk]
+ New page documenting pthread_rwlockattr_[sg]etkind_np(3)
+ Documents pthread_rwlockattr_setkind_np(3) and
+ pthread_rwlockattr_getkind_np(3).
New and changed links
---------------------
-procfs.5
- New link to proc.5
- Since the term "procfs" is widely used, it seems reasonable to have
- a link from that name to proc(5).
+pthread_rwlockattr_getkind_np.3
+ Robert Schweikert
+ New link to pthread_rwlockattr_setkind_np(3)
Changes to individual pages
---------------------------
-locale.1
- Marko Myllynen
- Provide a step-by-step example of how to use a custom locale
- Marko Myllynen
- Use LC_TELEPHONE instead of LC_MESSAGES in the example
- yesstr/nostr in LC_MESSAGES are planned to be changed at some
- point [1], so it's better to provide an example which won't
- be obsoleted by that change.
-
- [1] https://sourceware.org/bugzilla/show_bug.cgi?id=16975
-
-adjtimex.2
- Michael Kerrisk
- Add featute test macro requirements
-
-clone.2
- Michael Kerrisk
- ERRORS: add cross-reference to fork(2) for explanation of EAGAIN
-
-fork.2
- Michael Kerrisk
- ERRORS: add pid_max and threads-max to EAGAIN
- And rewrite text to be the same as pthread_create(3).
-
-getrlimit.2
- Michael Kerrisk
- RLIMIT_NPROC is not enforced if CAP_SYS_ADMIN or CAP_SYS_RESOURCE
-
-remap_file_pages.2
- Rasmus Villemoes
- Fix prototype
- The pgoff argument has type size_t, not ssize_t (and in the
- kernel it is unsigned long).
-
-set_mempolicy.2
- Rasmus Villemoes
- Fix prototype for set_mempolicy(2)
- The nodemask argument is const. The return type in numaif.h is long.
-
-swapon.2
- Rasmus Villemoes
- Remove header from synopsis
- The <asm/page.h> header is not readily available, and the comment
- seems to indicate that it is for getting PAGE_SIZE. But it is
- never mentioned why one would need to know that, and it is in any
- case better obtained using sysconf(), provided by <unistd.h>.
-
-a64l.3
- Rasmus Villemoes
- Fix prototype for a64l()
- The argument is const, both according to POSIX and the
- glibc headers.
-
-adjtime.3
- Rasmus Villemoes
- Add required header
- The prototype for adjtime(3) is declared in <sys/time.h>.
-
-argz_add.3
- Rasmus Villemoes
- Fix prototypes
- Update the prototypes of argz_{delete,extract,next} to agree with
- glibc headers and manual.
-
-bstring.3
- Rasmus Villemoes
- Fix prototypes
- The length parameter n has type size_t in bcmp(), bcopy() and
- bzero().
-
-envz_add.3
- Rasmus Villemoes
- Fix prototypes
- The envz_len parameters for envz_entry() and envz_get() are not
- passed by reference.
-
-fpathconf.3
- Rasmus Villemoes
- Fix prototype
- The path argument to pathconf() is const.
+readlink.2
+ Michael Kerrisk [Jonny Grant]
+ Add free() call to example program
-fseek.3
- Rasmus Villemoes
- Fix prototype
- The pos argument to fsetpos() is const.
-
-gcvt.3
- Rasmus Villemoes
- Fix prototype
- The ndigit paramenter to gcvt() has type int.
-
-getaddrinfo_a.3
- Rasmus Villemoes
- Fix prototype
- The pointer arguments to gai_suspend() are const.
-
-getauxval.3
- Rasmus Villemoes
- Fix permissions
- There doesn't seem to be any reason for getauxval.3 to be
- executable...
-
-getnameinfo.3
- Rasmus Villemoes
- Fix prototype
- The hostlen and servlen parameters have type socklet_t.
- (The types changed in glibc 2.2)
+readv.2
Michael Kerrisk
- Note types of 'hostlen'; and 'servlen' in glibc < 2.2
-
-getrpcent.3
- Rasmus Villemoes
- Fix prototype
- The argument to getrpcbyname() is const.
-
-getrpcport.3
- Rasmus Villemoes
- Add #include and fix prototype
- The prototype for getrpcport() is obtained by #include'ing
- <rpc/rpc.h>. Also, update its prototype.
-
-getspnam.3
- Rasmus Villemoes
- Fix prototype
- The struct spwd argument to putspent() is const.
-
-getutent.3
- Rasmus Villemoes
- Fix prototypes
- The arguments to getutid(), getutline(), and pututline()
- are const.
-
-inet.3
- Rasmus Villemoes
- Fix prototype
- The parameters to inet_makeaddr have type in_addr_t.
-
-inet_net_pton.3
- Rasmus Villemoes
- srcfix, cfix
- Use a consistent style throughout the man-pages.
+ The raw preadv() and pwritev() syscalls split 'offset' into 2 arguments
-key_setsecret.3
- Rasmus Villemoes
- Fix prototypes
- Remove const qualifiers from arguments to key_decryptsession,
- key_encryptsession, and key_setsecret.
-
-makecontext.3
- Rasmus Villemoes
- Fix prototype
- The second argument to swapcontext() is const.
-
-makedev.3
- Rasmus Villemoes
- Fix prototype
- gnu_dev_makedev, and hence its trivial macro wrapper makedev, takes
- two unsigned int parameters; this is consistent with it being the
- inverse of (gnu_dev_)major/minor, which return unsigned int.
-
-malloc_trim.3
- Rasmus Villemoes
- Fix prototype
- As mentioned further down, malloc_trim returns an integer.
-
-mq_getattr.3
- Rasmus Villemoes
- Fix prototype
- The newattr parameter to mq_setattr is const.
-
-newlocale.3
- Marko Myllynen
- List all available category masks
+signal.7
Michael Kerrisk
- Add LC_ALL_MASK description
-
-nl_langinfo.3
- Marko Myllynen
- Expand the example code a bit
- Better illustrate querying elements from different categories.
-
-perror.3
- Rasmus Villemoes
- Fix declaration
- The elements of the array sys_errlist are also const.
-
-pthread_attr_setaffinity_np.3
-pthread_attr_setdetachstate.3
-pthread_attr_setguardsize.3
-pthread_attr_setinheritsched.3
-pthread_attr_setschedparam.3
-pthread_attr_setschedpolicy.3
-pthread_attr_setscope.3
-pthread_attr_setstack.3
-pthread_attr_setstackaddr.3
-pthread_attr_setstacksize.3
- Rasmus Villemoes
- Constify parameters
- Each of the pthread_attr_get* functions extract some piece of
- information from a pthread_attr_t, which is passed by const
- reference. Add the const keyword to the prototypes of these
- functions.
-
-pthread_cleanup_push_defer_np.3
- Michael Kerrisk [Rasmus Villemoes]
- Add feature test macro requirements
-
-pthread_create.3
- Michael Kerrisk [Carsten Grohmann]
- Add pid_max limit to EAGAIN error cases
-
-pthread_equal.3
- Peng Haitao
- ATTRIBUTES: Note function that is thread-safe
- The function pthread_equal() is thread safe.
-
-pthread_exit.3
- Peng Haitao
- ATTRIBUTES: Note function that is thread-safe
- The function pthread_exit() is thread safe.
-
-pthread_getcpuclockid.3
- Peng Haitao
- ATTRIBUTES: Note function that is thread-safe
- The function pthread_getcpuclockid() is thread safe.
-
-pthread_setaffinity_np.3
- Peng Haitao
- ATTRIBUTES: Note functions that are thread-safe
- The functions pthread_setaffinity_np() and
- pthread_getaffinity_np() are thread safe.
-
-pthread_setconcurrency.3
- Peng Haitao
- ATTRIBUTES: Note functions that are thread-safe
- The functions pthread_setconcurrency() and
- pthread_getconcurrency() are thread safe.
-
-pthread_setname_np.3
- Rasmus Villemoes
- Fix prototype
- The name parameter of pthread_getname_np is an output parameter and
- hence not const.
-
-pthread_setschedparam.3
- Rasmus Villemoes
- Fix prototypes
- Add return type for pthread_{s,g}etschedparam.
-
-pthread_setschedprio.3
- Rasmus Villemoes
- Fix prototype
- Add return type for pthread_setschedprio.
-
-pthread_sigqueue.3
- Rasmus Villemoes
- Add missing #include <signal.h>
-
-rcmd.3
- Rasmus Villemoes
- Fix prototypes
- Unlike the BSDs, the second argument of rcmd() and rcmd_af() has
- type unsigned short.
- The first argument of iruserok_af() has type const void*.
-
-re_comp.3
- Rasmus Villemoes
- Fix prototypes
- re_comp and re_exec take const char* arguments.
-
-resolver.3
- Rasmus Villemoes
- Fix prototypes and extern-declaration
- Fix const- and signedness of various char* parameters.
-
- Also, there is no "struct state", but _res is a struct
- __res_state. (Actually, _res is errno-like in that it is really a
- macro expanding to (*__res_state()).)
-
-rexec.3
- Rasmus Villemoes
- Fix prototypes
- The user, passwd and cmd arguments to rexec and rexec_af are all
- const.
-
-rtime.3
- Rasmus Villemoes
- Replace header
- The header <rpc/des_crypt.h> does not provide rtime();
- <rpc/auth_des.h> does, as is also implied in both the NOTES and
- EXAMPLE sections.
-
-scandir.3
- Rasmus Villemoes
- Fix prototypes
- The alphasort and versionsort functions take arguments of type
- const struct dirent **, not const void *.
-
-setlocale.3
- Michael Kerrisk [Marko Myllynen]
- Simplify locale category listing and add GNU-specific locale categories
- Some information that was here will move to locale(7).
- Marko Myllynen
- Remove now obsolete NOTES section
-
-setnetgrent.3
- Rasmus Villemoes
- Fix prototype
- The buflen argument to getnetgrent_r has type size_t.
-
-sigvec.3
- Rasmus Villemoes
- Fix prototype
- The vec argument to sigvec is const.
-
-tsearch.3
- Rasmus Villemoes
- Fix prototype
- The rootp argument to tfind is "void * const *",
- not "const void **".
-
-core.5
- Michael Kerrisk
- Core dump files are nowadays core.pid by default
-
-locale.5
- Marko Myllynen
- Document mon_grouping and grouping properly
- Michael Kerrisk
- Note default value for 'first_workday'
- Michael Kerrisk [Marko Myllynen]
- Add brief descriptions of collating-element and collating-symbol
- Marko Myllynen
- t_fmt_ampm is needed only for locales that employ AM/PM convention
- Michael Kerrisk [Marko Myllynen]
- Remove crufty reference to /usr/lib/nls/src
- That file is nowhere to be found
- Marko Myllynen
- Clarify LC_TIME/am_pm and LC_NAME keywords usage
- am_pm should be defined only if AM/PM convention is used to signal
- applications they should not try to print them when using them in
- unwanted.
-
- Same for all LC_NAME keywords expect for name_fmt which should be
- always defined.
- Marko Myllynen
- Clarify lang_term / lang_lib
- As noted by Keld Simonsen in the lib-locales@sourceware mailing
- list:
-
- https://sourceware.org/ml/libc-locales/2014-q2/msg00008.html
- From: Keld Simonsen <keld at rap dot rap dot dk>
- To: Marko Myllynen <myllynen at redhat dot com>
- Date: Tue, 29 Apr 2014 17:02:09 +0200
-
- lang_term reflects ISO 639-2/T (terminology) codes, while
- lang_lib reflects ISO 639-2/B (bibliographic) codes.
- lang_term is preferred over lang_lib codes for locale names.
- There are 20 specific ISO 639-2/B codes.
- Marko Myllynen
- Correct the FILES section
-
-proc.5
- Michael Kerrisk
- 'pid_max' is a system-wide limit on number of threads and processes
- Since PIDs > /proc/sys/kernel/pid_max are not allocated, this
- file thus also imposes a system-wide limit on the number of
- threads and processes.
-
-capabilities.7
- Michael Kerrisk
- CAP_SYS_ADMIN allows overriding RLIMIT_NPROC
- Michael Kerrisk
- CAP_SYS_PTRACE allows process_vm_readv(2) and process_vm_writev(2)
-
-charsets.7
- Michael Kerrisk [Marko Myllynen]
- Remove crufty statement that Romanian may be switching to ISO 8859-16
- Michael Kerrisk
- Remove ancient paragraph on charsets supported in glibc 2.3.2
- That test is rather ancient, and probably of little use.
-
-fanotify.7
- Heinrich Schuchardt
- Fix to example program: fanotifyi read() should use aligned buffer
-
-inotify.7
- Heinrich Schuchardt
- Add example program
- This example of the usage of the inotify API shows the
- usage of inotify_init1(2) and inotify_add_watch(2) as well
- as polling and reading from the inotify file descriptor.
- Heinrich Schuchardt
- munmap() does not generate inotify events
-
-locale.7
- Marko Myllynen [Michael Kerrisk]
- Document the LOCPATH environment variable
- Michael Kerrisk
- Add further details on various categories
-
+ pthread_mutex_lock() and pthread_cond_wait() are restartable
+ pthread_mutex_lock(, pthread_cond_wait(), and related APIs are
+ automatically restarted if interrupted by a signal handler.
+
+unix.7
+ Michael Kerrisk [Carlos O'Donell, David Miller, Tetsuo Handa]
+ Various additions and rewordings
+ Notable changes:
+ * Clarify some details for pathname sockets.
+ * Add some advice on portably coding with pathname sockets.
+ * Note the "buggy" behavior for pathname sockets when
+ the supplied pathname is 108 bytes (after a report by
+ Tetsuo Handa).
Angelo Borsotti <angelo.borsotti@gmail.com>
Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
Brian M. Carlson <sandals@crustytoothpaste.ath.cx>
-Casper.Dik@oracle.com
+Casper Dik <Casper.Dik@oracle.com>
David Prévot <taffit@debian.org>
D. Barbier <bouzim@gmail.com>
Eric Blake <eblake@redhat.com>
should have been trimmed from this page.
Michael Kerrisk
SEE ALSO: Mention more files in Documentation/scheduler/ directory
+
+
+==================== Changes in man-pages-3.68 ====================
+
+Released: 2014-05-28, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Alastair McKinstry <mckinstry@computer.org>
+Carsten Grohmann <carstengrohmann@gmx.de>
+Colin Williams <colinwilliams1968@gmail.com>
+Heinrich Schuchardt <xypron.glpk@gmx.de>
+Lars Wirzenius <liw@iki.fi>
+Marko Myllynen <myllynen@redhat.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Peng Haitao <penght@cn.fujitsu.com>
+Rasmus Villemoes <rv@rasmusvillemoes.dk>
+Richard Braakman <richard.braakman@jollamobile.com>
+Simon Paillard <spaillard@debian.org>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+localedef.1
+ Marko Myllynen, Richard Braakman, Alastair McKinstry, Lars Wirzenius
+ New page for localedef(1)
+ Add new page based on Debian localedef(1) page.
+
+
+New and changed links
+---------------------
+
+procfs.5
+ New link to proc.5
+ Since the term "procfs" is widely used, it seems reasonable to have
+ a link from that name to proc(5).
+
+
+Changes to individual pages
+---------------------------
+
+locale.1
+ Marko Myllynen
+ Provide a step-by-step example of how to use a custom locale
+ Marko Myllynen
+ Use LC_TELEPHONE instead of LC_MESSAGES in the example
+ yesstr/nostr in LC_MESSAGES are planned to be changed at some
+ point [1], so it's better to provide an example which won't
+ be obsoleted by that change.
+
+ [1] https://sourceware.org/bugzilla/show_bug.cgi?id=16975
+
+adjtimex.2
+ Michael Kerrisk
+ Add feature test macro requirements
+
+clone.2
+ Michael Kerrisk
+ ERRORS: add cross-reference to fork(2) for explanation of EAGAIN
+
+fork.2
+ Michael Kerrisk
+ ERRORS: add pid_max and threads-max to EAGAIN
+ And rewrite text to be the same as pthread_create(3).
+
+getrlimit.2
+ Michael Kerrisk
+ RLIMIT_NPROC is not enforced if CAP_SYS_ADMIN or CAP_SYS_RESOURCE
+
+remap_file_pages.2
+ Rasmus Villemoes
+ Fix prototype
+ The pgoff argument has type size_t, not ssize_t (and in the
+ kernel it is unsigned long).
+
+set_mempolicy.2
+ Rasmus Villemoes
+ Fix prototype for set_mempolicy(2)
+ The nodemask argument is const. The return type in numaif.h is long.
+
+swapon.2
+ Rasmus Villemoes
+ Remove header from synopsis
+ The <asm/page.h> header is not readily available, and the comment
+ seems to indicate that it is for getting PAGE_SIZE. But it is
+ never mentioned why one would need to know that, and it is in any
+ case better obtained using sysconf(), provided by <unistd.h>.
+
+a64l.3
+ Rasmus Villemoes
+ Fix prototype for a64l()
+ The argument is const, both according to POSIX and the
+ glibc headers.
+
+adjtime.3
+ Rasmus Villemoes
+ Add required header
+ The prototype for adjtime(3) is declared in <sys/time.h>.
+
+argz_add.3
+ Rasmus Villemoes
+ Fix prototypes
+ Update the prototypes of argz_{delete,extract,next} to agree with
+ glibc headers and manual.
+
+bstring.3
+ Rasmus Villemoes
+ Fix prototypes
+ The length parameter n has type size_t in bcmp(), bcopy() and
+ bzero().
+
+envz_add.3
+ Rasmus Villemoes
+ Fix prototypes
+ The envz_len parameters for envz_entry() and envz_get() are not
+ passed by reference.
+
+fpathconf.3
+ Rasmus Villemoes
+ Fix prototype
+ The path argument to pathconf() is const.
+
+fseek.3
+ Rasmus Villemoes
+ Fix prototype
+ The pos argument to fsetpos() is const.
+
+gcvt.3
+ Rasmus Villemoes
+ Fix prototype
+ The ndigit parameter to gcvt() has type int.
+
+getaddrinfo_a.3
+ Rasmus Villemoes
+ Fix prototype
+ The pointer arguments to gai_suspend() are const.
+
+getauxval.3
+ Rasmus Villemoes
+ Fix permissions
+ There doesn't seem to be any reason for getauxval.3 to be
+ executable...
+
+getnameinfo.3
+ Rasmus Villemoes
+ Fix prototype
+ The hostlen and servlen parameters have type socklen_t.
+ (The types changed in glibc 2.2)
+ Michael Kerrisk
+ Note types of 'hostlen'; and 'servlen' in glibc < 2.2
+
+getrpcent.3
+ Rasmus Villemoes
+ Fix prototype
+ The argument to getrpcbyname() is const.
+
+getrpcport.3
+ Rasmus Villemoes
+ Add #include and fix prototype
+ The prototype for getrpcport() is obtained by #include'ing
+ <rpc/rpc.h>. Also, update its prototype.
+
+getspnam.3
+ Rasmus Villemoes
+ Fix prototype
+ The struct spwd argument to putspent() is const.
+
+getutent.3
+ Rasmus Villemoes
+ Fix prototypes
+ The arguments to getutid(), getutline(), and pututline()
+ are const.
+
+inet.3
+ Rasmus Villemoes
+ Fix prototype
+ The parameters to inet_makeaddr have type in_addr_t.
+
+inet_net_pton.3
+ Rasmus Villemoes
+ srcfix, cfix
+ Use a consistent style throughout the man-pages.
+
+key_setsecret.3
+ Rasmus Villemoes
+ Fix prototypes
+ Remove const qualifiers from arguments to key_decryptsession,
+ key_encryptsession, and key_setsecret.
+
+makecontext.3
+ Rasmus Villemoes
+ Fix prototype
+ The second argument to swapcontext() is const.
+
+makedev.3
+ Rasmus Villemoes
+ Fix prototype
+ gnu_dev_makedev, and hence its trivial macro wrapper makedev, takes
+ two unsigned int parameters; this is consistent with it being the
+ inverse of (gnu_dev_)major/minor, which return unsigned int.
+
+malloc_trim.3
+ Rasmus Villemoes
+ Fix prototype
+ As mentioned further down, malloc_trim returns an integer.
+
+mq_getattr.3
+ Rasmus Villemoes
+ Fix prototype
+ The newattr parameter to mq_setattr is const.
+
+newlocale.3
+ Marko Myllynen
+ List all available category masks
+ Michael Kerrisk
+ Add LC_ALL_MASK description
+
+nl_langinfo.3
+ Marko Myllynen
+ Expand the example code a bit
+ Better illustrate querying elements from different categories.
+
+perror.3
+ Rasmus Villemoes
+ Fix declaration
+ The elements of the array sys_errlist are also const.
+
+pthread_attr_setaffinity_np.3
+pthread_attr_setdetachstate.3
+pthread_attr_setguardsize.3
+pthread_attr_setinheritsched.3
+pthread_attr_setschedparam.3
+pthread_attr_setschedpolicy.3
+pthread_attr_setscope.3
+pthread_attr_setstack.3
+pthread_attr_setstackaddr.3
+pthread_attr_setstacksize.3
+ Rasmus Villemoes
+ Constify parameters
+ Each of the pthread_attr_get* functions extract some piece of
+ information from a pthread_attr_t, which is passed by const
+ reference. Add the const keyword to the prototypes of these
+ functions.
+
+pthread_cleanup_push_defer_np.3
+ Michael Kerrisk [Rasmus Villemoes]
+ Add feature test macro requirements
+
+pthread_create.3
+ Michael Kerrisk [Carsten Grohmann]
+ Add pid_max limit to EAGAIN error cases
+
+pthread_equal.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function pthread_equal() is thread safe.
+
+pthread_exit.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function pthread_exit() is thread safe.
+
+pthread_getcpuclockid.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function pthread_getcpuclockid() is thread safe.
+
+pthread_setaffinity_np.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions pthread_setaffinity_np() and
+ pthread_getaffinity_np() are thread safe.
+
+pthread_setconcurrency.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions pthread_setconcurrency() and
+ pthread_getconcurrency() are thread safe.
+
+pthread_setname_np.3
+ Rasmus Villemoes
+ Fix prototype
+ The name parameter of pthread_getname_np is an output parameter and
+ hence not const.
+
+pthread_setschedparam.3
+ Rasmus Villemoes
+ Fix prototypes
+ Add return type for pthread_{s,g}etschedparam.
+
+pthread_setschedprio.3
+ Rasmus Villemoes
+ Fix prototype
+ Add return type for pthread_setschedprio.
+
+pthread_sigqueue.3
+ Rasmus Villemoes
+ Add missing #include <signal.h>
+
+rcmd.3
+ Rasmus Villemoes
+ Fix prototypes
+ Unlike the BSDs, the second argument of rcmd() and rcmd_af() has
+ type unsigned short.
+ The first argument of iruserok_af() has type const void*.
+
+re_comp.3
+ Rasmus Villemoes
+ Fix prototypes
+ re_comp and re_exec take const char* arguments.
+
+resolver.3
+ Rasmus Villemoes
+ Fix prototypes and extern-declaration
+ Fix const- and signedness of various char* parameters.
+
+ Also, there is no "struct state", but _res is a struct
+ __res_state. (Actually, _res is errno-like in that it is really a
+ macro expanding to (*__res_state()).)
+
+rexec.3
+ Rasmus Villemoes
+ Fix prototypes
+ The user, passwd and cmd arguments to rexec and rexec_af are all
+ const.
+
+rtime.3
+ Rasmus Villemoes
+ Replace header
+ The header <rpc/des_crypt.h> does not provide rtime();
+ <rpc/auth_des.h> does, as is also implied in both the NOTES and
+ EXAMPLE sections.
+
+scandir.3
+ Rasmus Villemoes
+ Fix prototypes
+ The alphasort and versionsort functions take arguments of type
+ const struct dirent **, not const void *.
+
+setlocale.3
+ Michael Kerrisk [Marko Myllynen]
+ Simplify locale category listing and add GNU-specific locale categories
+ Some information that was here will move to locale(7).
+ Marko Myllynen
+ Remove now obsolete NOTES section
+
+setnetgrent.3
+ Rasmus Villemoes
+ Fix prototype
+ The buflen argument to getnetgrent_r has type size_t.
+
+sigvec.3
+ Rasmus Villemoes
+ Fix prototype
+ The vec argument to sigvec is const.
+
+tsearch.3
+ Rasmus Villemoes
+ Fix prototype
+ The rootp argument to tfind is "void * const *",
+ not "const void **".
+
+core.5
+ Michael Kerrisk
+ Core dump files are nowadays core.pid by default
+
+locale.5
+ Marko Myllynen
+ Document mon_grouping and grouping properly
+ Michael Kerrisk
+ Note default value for 'first_workday'
+ Michael Kerrisk [Marko Myllynen]
+ Add brief descriptions of collating-element and collating-symbol
+ Marko Myllynen
+ t_fmt_ampm is needed only for locales that employ AM/PM convention
+ Michael Kerrisk [Marko Myllynen]
+ Remove crufty reference to /usr/lib/nls/src
+ That file is nowhere to be found
+ Marko Myllynen
+ Clarify LC_TIME/am_pm and LC_NAME keywords usage
+ am_pm should be defined only if AM/PM convention is used to signal
+ applications they should not try to print them when using them in
+ unwanted.
+
+ Same for all LC_NAME keywords expect for name_fmt which should be
+ always defined.
+ Marko Myllynen
+ Clarify lang_term / lang_lib
+ As noted by Keld Simonsen in the lib-locales@sourceware mailing
+ list:
+
+ https://sourceware.org/ml/libc-locales/2014-q2/msg00008.html
+ From: Keld Simonsen <keld at rap dot rap dot dk>
+ To: Marko Myllynen <myllynen at redhat dot com>
+ Date: Tue, 29 Apr 2014 17:02:09 +0200
+
+ lang_term reflects ISO 639-2/T (terminology) codes, while
+ lang_lib reflects ISO 639-2/B (bibliographic) codes.
+ lang_term is preferred over lang_lib codes for locale names.
+ There are 20 specific ISO 639-2/B codes.
+ Marko Myllynen
+ Correct the FILES section
+
+proc.5
+ Michael Kerrisk
+ 'pid_max' is a system-wide limit on number of threads and processes
+ Since PIDs > /proc/sys/kernel/pid_max are not allocated, this
+ file thus also imposes a system-wide limit on the number of
+ threads and processes.
+
+capabilities.7
+ Michael Kerrisk
+ CAP_SYS_ADMIN allows overriding RLIMIT_NPROC
+ Michael Kerrisk
+ CAP_SYS_PTRACE allows process_vm_readv(2) and process_vm_writev(2)
+
+charsets.7
+ Michael Kerrisk [Marko Myllynen]
+ Remove crufty statement that Romanian may be switching to ISO 8859-16
+ Michael Kerrisk
+ Remove ancient paragraph on charsets supported in glibc 2.3.2
+ That test is rather ancient, and probably of little use.
+
+fanotify.7
+ Heinrich Schuchardt
+ Fix to example program: fanotify read() should use aligned buffer
+
+inotify.7
+ Heinrich Schuchardt
+ Add example program
+ This example of the usage of the inotify API shows the
+ usage of inotify_init1(2) and inotify_add_watch(2) as well
+ as polling and reading from the inotify file descriptor.
+ Heinrich Schuchardt
+ munmap() does not generate inotify events
+
+locale.7
+ Marko Myllynen [Michael Kerrisk]
+ Document the LOCPATH environment variable
+ Michael Kerrisk
+ Add further details on various categories
+
+
+
+==================== Changes in man-pages-3.69 ====================
+
+Released: 2014-06-14, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Cyril Hrubis <chrubis@suse.cz>
+Jan Chaloupka <jchaloup@redhat.com>
+Jeff Layton <jlayton@poochiereds.net>
+Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
+KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
+Marko Myllynen <myllynen@redhat.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+NeilBrown <neilb@suse.de>
+Peng Haitao <penght@cn.fujitsu.com>
+Petr Gajdos <pgajdos@suse.cz>
+Qian Lei <qianl.fnst@cn.fujitsu.com>
+Rasmus Villemoes <rv@rasmusvillemoes.dk>
+Vasiliy Kulikov <segoon@openwall.com>
+Walter Harms <wharms@bfs.de>
+Yuri Kozlov <yuray@komyakino.ru>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+iconv.1
+ Marko Myllynen [Michael Kerrisk]
+ New page for the iconv(1) command
+
+iconvconfig.8
+ Marko Myllynen
+ New page for iconvconfig(8)
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+fcntl.2
+ Jeff Layton, Michael Kerrisk
+ Document open file description locks
+ As provided by the fcntl() operations F_OFD_SETLK,
+ F_OFD_SETLKW, and F_OFD_GETLK
+
+
+Changes to individual pages
+---------------------------
+
+locale.1
+ Marko Myllynen
+ Add FILES section, add charmap(5) reference
+ Marko Myllynen
+ Align with recent charmap(5) / repertoiremap(5) changes
+
+execve.2
+ Michael Kerrisk [NeilBrown]
+ Before kernel 2.6.0, RLIMIT_NPROC had no effect for set*uid()
+ Michael Kerrisk [Vasiliy Kulikov]
+ RLIMIT_NPROC is checked only if preceded by set*uid()
+ Michael Kerrisk [Vasiliy Kulikov, NeilBrown, KOSAKI Motohiro]
+ Document EAGAIN error
+ See also https://bugzilla.kernel.org/show_bug.cgi?id=42704
+
+fcntl.2
+ Michael Kerrisk
+ Detail the limitations of traditional (process-associated) locks
+ Michael Kerrisk [Jeff Layton]
+ Describe how to check whether the kernel supports a particular command
+ Michael Kerrisk
+ ERRORS: add EINVAL for invalid 'cmd'
+ Michael Kerrisk
+ Add para introducing advisory locks and noting existence of OFD locks
+ Michael Kerrisk [Jeff Layton]
+ Add notes on F_SETLKW deadlock detection and its limitations
+ Michael Kerrisk
+ Add an explicit note that mandatory locking is not in POSIX
+ Michael Kerrisk
+ Rewrite introductory paragraphs on mandatory locking
+ Make the structure more logical, and also explicitly mention
+ OFD locks.
+ Michael Kerrisk [Jeff Layton]
+ Reword discussion of mandatory lock bug a little
+ Jeff Layton confirmed that the bug remains even in modern kernels.
+ Michael Kerrisk
+ Explain POSIX background to EACCES/EAGAIN error for F_GETLK
+ Michael Kerrisk
+ Add NOTES subhead for record locking and NFS
+ Michael Kerrisk [NeilBrown]
+ Note treatment of locks when an NFS client loses contact with the server
+ Michael Kerrisk [Jeff Layton]
+ nfsv4leasetime controls the "contact lost" interval for NFSv4
+
+flock.2
+ Michael Kerrisk
+ In some modern BSDs, fcntl() and flock() locks do interact
+ So, reword and extend the discussion of this topic in NOTES.
+ Michael Kerrisk
+ Move NOTES text describing implementation of flock()
+ Michael Kerrisk [NeilBrown]
+ Add more details on NFS, including Linux 2.6.37 changes
+ Also: move NOTES text describing interaction of fcntl()
+ and flock() locks.
+
+fork.2
+ Michael Kerrisk
+ Add notes on inheritance of flock() and OFD locks across fork()
+
+lseek.2
+ Michael Kerrisk
+ Add reference to open(2) for discussion of file descriptors and OFDs
+
+open.2
+ Michael Kerrisk
+ Rework and extend the discussion of open file descriptions
+
+open_by_handle_at.2
+ Rasmus Villemoes
+ Add reference to feature_test_macros(7)
+
+recvmmsg.2
+ Rasmus Villemoes
+ Add reference to feature_test_macros(7)
+
+remap_file_pages.2
+ Michael Kerrisk [Kirill A. Shutemov]
+ Note that remap_file_pages() is deprecated
+
+sendmmsg.2
+ Rasmus Villemoes
+ Add reference to feature_test_macros(7)
+
+seteuid.2
+ Michael Kerrisk
+ seteuid() and setegid() are implemented as library functions
+ Michael Kerrisk
+ Error checking should always be performed, even when caller is UID 0
+
+setresuid.2
+ Michael Kerrisk
+ Document EAGAIN error that can occur after kernel alloc_uid() failure
+ Michael Kerrisk
+ Since Linux 3.1, the EAGAIN case for RLIMIT_NPROC no longer occurs
+ Michael Kerrisk
+ Correct the description of the EAGAIN error
+ Michael Kerrisk
+ Error checking should always be performed, even when caller is UID 0
+
+setreuid.2
+ Michael Kerrisk
+ Document EAGAIN error that can occur after kernel alloc_uid() failure
+ Michael Kerrisk
+ Error checking should always be performed, even when caller is UID 0
+ Michael Kerrisk
+ Add EAGAIN error for hitting RLIMIT_NPROC limit
+ Michael Kerrisk
+ Since Linux 3.1, the EAGAIN case for RLIMIT_NPROC no longer occurs
+
+setuid.2
+ Michael Kerrisk
+ Document EAGAIN error that can occur after kernel alloc_uid() failure
+ Michael Kerrisk
+ Correct the description of the EAGAIN error
+ Michael Kerrisk
+ Error checking should always be performed, even when caller is UID 0
+ Michael Kerrisk
+ Since Linux 3.1, the EAGAIN case for RLIMIT_NPROC no longer occurs
+
+statfs.2
+ Cyril Hrubis
+ Update MAGIC constants
+ Most of the updates are taken from /usr/include/linux/magic.h,
+ some were found by grepping the Linux source code.
+ Cyril Hrubis [Michael Kerrisk]
+ fstatfs(2) was broken on file descriptors from pipe(2)
+
+syscalls.2
+ Michael Kerrisk
+ Note that remap_file_pages() is deprecated
+
+basename.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions basename() and dirname() are thread safe.
+
+catgets.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function catgets() is thread safe.
+
+getdate.3
+ Rasmus Villemoes
+ Use blank definition of _GNU_SOURCE in example program
+
+getdirentries.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function getdirentries() is thread safe.
+
+getdtablesize.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function getdtablesize() is thread safe.
+
+iconv.3
+ Qian Lei [Peng Haitao]
+ ATTRIBUTES: Note function that is thread-safe
+ The function iconv() is thread safe.
+ Michael Kerrisk
+ SEE ALSO: add iconvconfig(8)
+
+lockf.3
+ Qian Lei [Peng Haitao]
+ ATTRIBUTES: Note function that is thread-safe
+ The function lockf() is thread safe.
+
+malloc_get_state.3
+ Rasmus Villemoes
+ SYNOPSIS: use correct header
+ The nonstandard functions malloc_set_state() and
+ malloc_get_state() are provided by <malloc.h> not <stdlib.h>.
+
+malloc_usable_size.3
+ Qian Lei
+ ATTRIBUTES: Note function that is thread-safe
+ The function malloc_usable_size() is thread safe.
+
+matherr.3
+ Qian Lei [Peng Haitao]
+ ATTRIBUTES: Note function that is thread-safe
+ The function matherr() is thread safe.
+
+mkdtemp.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function mkdtemp() is thread safe.
+
+mkstemp.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions mkstemp(), mkostemp(), mkstemps() and mkostemps()
+ are thread safe.
+
+mq_close.3
+ Qian Lei
+ ATTRIBUTES: Note function that is thread-safe
+ The function mq_close() is thread safe.
+
+mq_getattr.3
+ Qian Lei
+ ATTRIBUTES: Note function that is thread-safe
+ The functions mq_getattr() and mq_setattr() are thread safe.
+
+mq_open.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function mq_open() is thread safe.
+
+mq_receive.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions mq_receive() and mq_timedreceive() are thread safe.
+
+mq_send.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions mq_send() and mq_timedsend() are thread safe.
+
+mq_unlink.3
+ Qian Lei
+ ATTRIBUTES: Note function that is thread-safe
+ The function mq_unlink() is thread safe.
+
+posix_fallocate.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function posix_fallocate() is thread safe.
+
+posix_openpt.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function posix_openpt() is thread safe.
+
+siginterrupt.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is not thread-safe
+ The function siginterrupt() is not thread safe.
+
+system.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function system() is thread safe.
+
+charmap.5
+ Marko Myllynen
+ Update to match current glibc
+ charmap(5) was outdated, bring it to closer to reality by fixing
+ syntax descriptions to match current glibc code and practices,
+ adding missing options, removing obsolete comments and references,
+ and removing now incorrect examples.
+
+locale.5
+ Marko Myllynen
+ Clarify AM/PM settings a bit
+ localedef(1) complains if really undefined, should be empty instead.
+ Also: add some SEE ALSO references.
+ Marko Myllynen
+ Document glibc conventions regarding days and week
+ Based on existing practice and glibc community wiki page at
+ https://sourceware.org/glibc/wiki/Locales
+
+proc.5
+ Michael Kerrisk [Jan Chaloupka, Walter Harms]
+ Add a brief description of /proc/fs
+
+repertoiremap.5
+ Marko Myllynen
+ New page for repertoiremap(5)
+ Rather obsolete feature but localedef(1) refers to repertoiremaps.
+
+bootparam.7
+ Petr Gajdos
+ Describe 'rootflags' and 'rootdelay' kernel parameters
+ Patch based on text from Documentation/kernel-parameters.txt
+
+charsets.7
+ Marko Myllynen
+ Update to reflect past developments
+ Rewrite the introduction to make Unicode's prominence more obvious.
+ Reformulate parts of the text to reflect current Unicode world.
+ Minor clarification for ASCII/ISO sections, some other minor fixes.
+ Marko Myllynen
+ List CJK encodings in the order of C, J, K
+
+environ.7
+ Michael Kerrisk
+ SEE ALSO: add env(1), printenv(1), ld.so(8)
+
+locale.7
+ Marko Myllynen
+ Add some SEE ALSO references
+
+man-pages.7
+ Michael Kerrisk
+ Note that .TH 'date' field is nowadays automatically updated by scripts
+
+signal.7
+ Michael Kerrisk
+ Describe EINTR semantics for recvmmsg(2)
+ Michael Kerrisk
+ Clarify text describing EINTR semantics for socket interfaces
+
+unicode.7
+ Marko Myllynen
+ Update to reflect past developments
+ The unicode(7) page will look more modern with few small changes:
+
+ - drop old BUGS section, editors cope with UTF-8 ok these days,
+ and perhaps the state-of-the-art is better described elsewhere
+ anyway than in a man page
+ - drop old suggestion about avoiding combined characters
+ - refer to LANANA for Linux zone, add registry file reference
+ - drop a reference to an inactive/dead mailing list
+ - update some reference URLs
+
+utf-8.7
+ Marko Myllynen
+ Drop an old comment about UTF-8 replacing ISO 8859
+ And add locale(1) under SEE ALSO.
+
+
+==================== Changes in man-pages-3.70 ====================
+
+Released: 2014-07-08, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Carlos O'Donell <carlos@redhat.com>
+Elie De Brauwer <eliedebrauwer@gmail.com>
+Florian Weimer <fweimer@redhat.com>
+Heinrich Schuchardt <xypron.glpk@gmx.de>
+Marko Myllynen <myllynen@redhat.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Nadav Har'El <nyh@math.technion.ac.il>
+NeilBrown <neilb@suse.de>
+Rich Felker <dalias@libc.org>
+Robert P. J. Day <rpjday@crashcourse.ca>
+Simon Paillard <spaillard@debian.org>
+Tomi Salminen <tlsalmin@gmail.com>
+Walter Harms <wharms@bfs.de>
+Yuri Kozlov <yuray@komyakino.ru>
+Кирилл <kirillnow@gmail.com>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+sprof.1
+ Michael Kerrisk [Marko Myllynen]
+ New page for the glibc sprof(1) command
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+epoll_ctl.2
+ NeilBrown
+ Document EPOLLWAKEUP
+
+epoll.7
+ NeilBrown
+ Document EPOLLWAKEUP
+
+
+Changes to individual pages
+---------------------------
+
+iconv.1
+iconvconfig.8
+ Marko Myllynen
+ Clarify gconv file terminology a bit
+
+ldd.1
+ Michael Kerrisk
+ SEE ALSO: add sprof(1)
+
+connect.2
+ Michael Kerrisk
+ ERRORS: add EPROTOTYPE
+ See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708394
+
+dup.2
+ Michael Kerrisk [Rich Felker]
+ Fix erroneous discussion regarding closing 'newfd' before calling dup2()
+ And propose a workaround if the caller cares about catching
+ close() time errors.
+
+ See http://stackoverflow.com/questions/23440216/race-condition-when-using-dup2#comment36888604_23444465
+ and http://austingroupbugs.net/view.php?id=411
+ Michael Kerrisk
+ Rework and enhance discussion of dup2()
+ In particular, note that dup2() performs the steps of closing
+ and reusing 'newfd' atomically.
+ Michael Kerrisk
+ Add subhead for dup3()
+
+epoll_ctl.2
+ Michael Kerrisk
+ BUGS: EPOLLWAKEUP is silently ignored without CAP_BLOCK_SUSPEND
+ If the caller does not have CAP_BLOCK_SUSPEND, then EPOLLWAKEUP
+ is silently ignored.
+
+fcntl.2
+ Michael Kerrisk [Tomi Salminen]
+ The return value for F_SETPIPE_SZ is the pipe capacity
+ Michael Kerrisk
+ ERRORS: Document ENOTDIR error for F_NOTIFY
+ Michael Kerrisk
+ Use proper page cross-references in F_NOTIFY discussion
+ Michael Kerrisk
+ Suggest the use of real-time signals with F_NOTIFY
+
+getitimer.2
+ Michael Kerrisk
+ Rewrite a few pieces to clarify some details
+
+inotify_add_watch.2
+ Michael Kerrisk
+ Clarify that the target of a watch is an i-node
+ The target of a watch is an i-node, not a pathname. Clarify
+ the text to prevent the reader possibly misunderstanding
+ that establishing watches by two different links to the same
+ file might create different watch descriptors.
+
+open.2
+ Michael Kerrisk [Кирилл]
+ O_CLOEXEC is also one the flags not ignored when O_PATH is specified
+
+pipe.2
+ Elie De Brauwer
+ PIPE_BUF is defined in limits.h
+ To make use of PIPE_BUF in an application one should include
+ <limits.h>. Adding a reference to this inclusion.
+
+poll.2
+ Michael Kerrisk [Nadav Har'El]
+ The negate-fd-to-ignore technique does not work for file descriptor 0
+ See https://bugzilla.kernel.org/show_bug.cgi?id=79411
+
+set_tid_address.2
+ Michael Kerrisk [Rich Felker]
+ Use "thread" rather than "process" in DESCRIPTION
+ Michael Kerrisk
+ SEE ALSO: add gettid(2)
+
+shmop.2
+ Michael Kerrisk
+ Explain SHMLBA in much more detail
+
+splice.2
+ Michael Kerrisk
+ Document EAGAIN error
+ See https://bugzilla.kernel.org/show_bug.cgi?id=48641
+
+syscalls.2
+ Carlos O'Donell
+ Add prlimit64(2)
+ While trying to reconcile the new features in glibc with the
+ documented entries in the linux kernel man pages I noticed that
+ glibc exports prlimit64 for use by 32-bit applications (as does
+ the linux kernel), but that prlimit64 was not defined in the
+ syscalls list or in the prlimit-related page.
+
+ This is not the complete fix for this, but I don't have the time
+ to explain why and when prlimit64 should be used (or how it should
+ be used safely). Therefore I'm just patching the syscalls.2 list
+ to show that prlimit64 exists and was added in 2.6.36 (verified
+ with git by checking out the tags before and after).
+
+syslog.2
+ Michael Kerrisk
+ Rework introductory paragraph
+ Michael Kerrisk [Robert P. J. Day]
+ Rework text describing loglevels
+ The kernel header file mentioned in the discussion of the KERN_*
+ constants has morphed and is no longer exported inside glibc.
+ And the definitions of the constants themselves changed subtly
+ with kernel commit 04d2c8c83d0e3ac5f78aeede51babb3236200112.
+ So, rewrite the description of the constants to be a bit more
+ abstract.
+ Michael Kerrisk
+ Rewrite parts of the page, and import /proc/sys/kernel/printk
+ * Move /proc/sys/kernel/printk from proc(5) to this page,
+ and correct various details in the discussion of that file.
+ * Rewrite and correct various other details on the page.
+ * Clean out some crufty text.
+ * Miscellaneous minor fixes.
+ Michael Kerrisk
+ Update SYSLOG_ACTION_CONSOLE_OFF + SYSLOG_ACTION_CONSOLE_ON description
+ Details changed in Linux 2.6.32
+
+tee.2
+ Michael Kerrisk
+ Document EAGAIN error
+ See https://bugzilla.kernel.org/show_bug.cgi?id=48641
+
+vmsplice.2
+ Michael Kerrisk
+ Document EAGAIN error
+ See https://bugzilla.kernel.org/show_bug.cgi?id=48641
+
+ether_aton.3
+ Michael Kerrisk
+ Make description of ether_line() bug a little more informative
+
+mallopt.3
+ Michael Kerrisk [Florian Weimer]
+ MALLOC_MMAP_THRESHOLD_ and MALLOC_MMAP_MAX_ *do* work in setgid programs
+ My testing on this point was bogus, overlooking details of
+ strace(1)'s behavior with setuid programs.
+
+ See https://sourceware.org/bugzilla/show_bug.cgi?id=12155
+
+printf.3
+ Michael Kerrisk [Rich Felker]
+ Remove libc4 and libc5 details
+ Rich Felker noted that "scare text" in the man page warned about
+ the use of snprintf() on libc, and that some people had cited
+ this as a reason not to use snprintf(). Linux libc is now
+ ancient history, so there is no real need to keep that text.
+ But, while we're at it, we may as well clear out all of the
+ other ancient libc4 and libc5 pieces in the page. They are
+ nowadays more clutter than help.
+ Michael Kerrisk
+ SUSv3 and later agree with C99 for the snprintf() return value
+ Determined by inspection of the SUSv3 and SUSv4 specifications.
+ Michael Kerrisk
+ Remove some old text about glibc 2.0 changes
+ We probably don't now need such ancient info.
+ Michael Kerrisk
+ Update references to standards for C and S conversion specifiers
+
+profil.3
+ Michael Kerrisk
+ SEE ALSO: add sprof(1)
+
+charmap.5
+ Marko Myllynen
+ Various minor updates and improvements
+ - more precise title
+ - extend description a bit
+ - document previously omitted WIDTH_DEFAULT
+ Marko Myllynen
+ Remove accidental ISO C compliance reference
+ glibc refers in locale/programs/charmap.c to ISO C 99 section
+ 7.17.(2) and ISO C 99 section 5.2.1.(3) that if a character map
+ is not ASCII compatible then the locale using it is not ISO C
+ compliant. This does not state anything about the character set
+ itself.
+
+proc.5
+ Michael Kerrisk
+ Replace /proc/sys/kernel/printk discussion with reference to syslog(2)
+ It makes more sense to have the /proc/sys/kernel/printk with
+ the related material in syslog(2).
+ Michael Kerrisk
+ Rewrite /proc/sys/kernel/printk description
+
+inotify.7
+ Michael Kerrisk
+ Clarify which events are generated for watched directories
+ Really, with respect to watched directories, events fall into
+ three classes (not two, as was shown):
+
+ * Events that can be generated only for the watched directory.
+ * Events that can be generated only for objects that are inside
+ the watched directory.
+ * Events that can be generated both for the watched directory
+ and for objects inside the directory.
+
+ So, mark these three classes more clearly in the list of inotify
+ events.
+ Heinrich Schuchardt [Michael Kerrisk]
+ BUGS: Note possible bug triggered by watch descriptor reuse
+ Watch descriptor IDs are returned by inotify_add_watch().
+ When calling inotify_rm_watch() an IN_IGNORE is placed on the
+ inotify queue pointing to the ID of the removed watch.
+
+ inotify_add_watchi() should not return a watch descriptor ID for
+ which events are still on the queue but should return an
+ unused ID.
+
+ Unfortunately, the existing Kernel code does not provide such a
+ guarantee.
+
+ Actually, in rare cases watch descriptor IDs are returned by
+ inotify_add_watch() for which events are still on the inotify
+ queue.
+
+ See https://bugzilla.kernel.org/show_bug.cgi?id=77111
+ Michael Kerrisk
+ Add further detail to the watch descriptor reuse bug
+ As well as inotify_rm_watch(), file deletion and unmounting a
+ filesystem can also cause a watch descriptor to be deleted.
+ Michael Kerrisk
+ The watch descriptor reuse bug may be hard to hit in practice
+ Explain the circumstances in detail, indicating that the
+ bug may be very unlikely to occur in practice.
+ Michael Kerrisk
+ Clarify description of IN_EXCL_UNLINK
+ Clarify the text a little, in particular making it clearer
+ that the target of a watch is an i-node (not a pathname).
+ Michael Kerrisk
+ Clarify IN_ONESHOT explanation
+ Make it clearer that the target of monitoring is an i-node,
+ not a pathname.
+ Michael Kerrisk
+ Make comment on 'mask' field more accurate
+
+libc.7
+ Michael Kerrisk
+ Clarify man-pages policy on documenting C libraries other tahn glibc
+ Michael Kerrisk
+ Use absolute dates in discussion of libc vs glibc
+
+pipe.7
+ Elie De Brauwer
+ Add reference that the pipe capacity can be changed
+ In fcntl(2) F_SETPIPE_SZ, F_GETPIPE_SZ and
+ /proc/sys/fs/pipe-max-size are defined, however
+ pipe(7) still defines the pipe capacity as being
+ a static entity. Adding a reference to fcntl(2).
+ Michael Kerrisk [Walter Harms]
+ Clarify that since 2.6.35, 65535 bytes is the default pipe capacity
+
+ld.so.8
+ Michael Kerrisk
+ Clarify that LD_PROFILE can specify just a single shared object
+ Michael Kerrisk
+ Clarify that LD_PROFILE output is appended to target file
+ The LD_PROFILE output is appended to any existing
+ contents of the target file.
+ Michael Kerrisk
+ SEE ALSO: add sprof(1)
+
+
+==================== Changes in man-pages-3.71 ====================
+
+Released: 2014-08-17, Chicago
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Adrian Bunk <bunk@kernel.org>
+Damir Nedzibovic <d.nedzibovic@anoxtech.com>
+David Prévot <taffit@debian.org>
+D. Barbier <bouzim@gmail.com>
+Jakub Wilk <jwilk@debian.org>
+Jan Chaloupka <jchaloup@redhat.com>
+Marko Myllynen <myllynen@redhat.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Mike Frysinger <vapier@gentoo.org>
+NeilBrown <neilb@suse.de>
+Paul Jackson <pj@usa.net>
+Peng Haitao <penght@cn.fujitsu.com>
+Rahul Bedarkar <rahulbedarkar89@gmail.com>
+Rob Landley <rob@landley.net>
+Ryan Hammonds <rhammonds@unicoi.com>
+Simon Paillard <spaillard@debian.org>
+Ville Ylenius <ville@ylenius.net>
+Vince Weaver <vincent.weaver@maine.edu>
+Yuri Kozlov <yuray@komyakino.ru>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+group_member.3
+ Michael Kerrisk
+ New page documenting group_member(3)
+
+isfdtype.3
+ Michael Kerrisk
+ New page documenting isfdtype(3)
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+perf_event_open.2
+ Vince Weaver
+ Document new comm_exec flag
+ Linux 3.16 (more specifically, commit 82b897782d10fcc4 )
+ added support for differentiating between process renames
+ caused by exec versus those caused by other methods.
+ Vince Weaver
+ Document new mmap2 record type
+ Linux 3.16 (more specifically, commit a5a5ba72843dd05f9 )
+ enabled the enhanced mmap2 record support.
+ The interface was added in Linux 3.12 but disabled until
+ Linux 3.16.
+ Vince Weaver
+ Document PERF_SAMPLE_BRANCH_COND
+ Linux 3.16 (more specifically, commit bac52139f0b7ab31330 )
+ adds support for gathering PERF_SAMPLE_BRANCH_COND
+ conditional branch values when doing PERF_SAMPLE_BRANCH_STACK
+ sampling.
+
+proc.5
+ Michael Kerrisk
+ Document /proc/PID/comm
+ Michael Kerrisk
+ Document /proc/PID/pagemap
+ Michael Kerrisk
+ Document /proc/PID/personality
+ Michael Kerrisk
+ Document /proc/PID/syscall
+ Michael Kerrisk
+ Document /proc/kpagecount
+ Michael Kerrisk
+ Document /proc/kpageflags
+ Michael Kerrisk
+ Document /proc/sys/vm/overcommit_kbytes
+
+capabilities.7
+ Michael Kerrisk
+ Add CAP_AUDIT_READ
+ CAP_AUDIT_READ is new in Linux 3.16.
+
+
+Global changes
+--------------
+
+ldd.1
+clone.2
+execve.2
+getpagesize.2
+ioperm.2
+msgop.2
+readv.2
+recv.2
+select.2
+send.2
+seteuid.2
+shmop.2
+signal.2
+sync.2
+sysinfo.2
+utime.2
+abs.3
+atoi.3
+catopen.3
+clearenv.3
+ctime.3
+des_crypt.3
+ecvt.3
+flockfile.3
+fseeko.3
+ftime.3
+ftok.3
+ftw.3
+getcwd.3
+getdtablesize.3
+getline.3
+getpass.3
+getpass.3
+getutent.3
+glob.3
+insque.3
+lseek64.3
+memmem.3
+mkstemp.3
+mktemp.3
+on_exit.3
+openpty.3
+putenv.3
+putenv.3
+qecvt.3
+realpath.3
+realpath.3
+remove.3
+setbuf.3
+sigpause.3
+strftime.3
+strptime.3
+tzset.3
+xcrypt.3
+utmp.5
+environ.7
+ipv6.7
+packet.7
+ Michael Kerrisk
+ Remove ancient Linux libc details
+
+access.2
+brk.2
+chmod.2
+eventfd.2
+gethostname.2
+getpriority.2
+mmap.2
+poll.2
+ptrace.2
+readv.2
+sched_setaffinity.2
+select.2
+seteuid.2
+signalfd.2
+sync_file_range.2
+timer_create.2
+uname.2
+wait.2
+ Michael Kerrisk
+ NOTES: add "C library/kernel ABI differences" subheading
+
+
+Changes to individual pages
+---------------------------
+
+access.2
+ Michael Kerrisk
+ Glibc falls back to using access() on kernels that lack faccessat()
+
+bdflush.2
+fsync.2
+sync.2
+proc.5
+ Adrian Bunk
+ Change "sync(1)" to "sync(8)"
+
+bind.2
+ Michael Kerrisk [Ryan Hammonds]
+ Correct EINVAL error description
+ As pointed out by Ryan:
+
+ My application is trying to bind an IPv4 UDP socket to an
+ address. I've found that passing an invalid address length
+ to bind() causes bind to return EINVAL. According to the
+ bind(2) manpage, this should only occur when using unix
+ domain sockets (which I am not).
+
+chmod.2
+ Michael Kerrisk
+ Glibc falls back to chmod() on kernels that don't support fchmodat()
+ Michael Kerrisk
+ Glibc falls back to chown()/lchown() on kernels that lack fchownat()
+
+epoll_wait.2
+ Michael Kerrisk
+ NOTES: describe raw epoll_pwait() system call differences
+
+getgroups.2
+ Michael Kerrisk
+ SEE ALSO: add group_member(3)
+
+getpriority.2
+ Michael Kerrisk
+ Enhance discussion of kernel nice range versus user-space nice range
+ Michael Kerrisk
+ Move text describing nice range on other systems
+
+getrlimit.2
+ Michael Kerrisk
+ Add cross reference to core(5) in discussion of RLIMIT_CORE
+ Michael Kerrisk
+ Describe the "large" resource limit bug on 32-bit platforms
+ See https://bugzilla.kernel.org/show_bug.cgi?id=5042.
+ Michael Kerrisk
+ Glibc's setrlimit() and getrlimit() are implemented using prlimit()
+
+kexec_load.2
+ Michael Kerrisk
+ Note limit of 16 for 'nr_segments'
+ Michael Kerrisk
+ Clarify the 'flags' bits that contain the architecture
+ Michael Kerrisk
+ Add KEXEC_ARCH_68K to list of architectures for 'flags'
+ Michael Kerrisk
+ Reword description of 'flags' a little
+
+link.2
+ Michael Kerrisk
+ Glibc falls back to link() on kernels that lack linkat()
+ Unless 'flags' contains AT_SYMLINK_FOLLOW.
+
+mkdir.2
+ Michael Kerrisk
+ Glibc falls back to mkdir() on kernels that don't support mkdirat()
+
+perf_event_open.2
+ Vince Weaver
+ Clarify PERF_SAMPLE_STACK_USER usage
+ This clarifies the PERF_SAMPLE_STACK_USER section.
+ I found these issue while implementing some code that uses
+ the option. The important change is fixing the name of the
+ sample_stack_user parameter, the rest is just some wording
+ fixes and minor clarifications.
+ Vince Weaver
+ Clarify PERF_SAMPLE_DATA_SRC usage
+ When checking the fields in the PERF_SAMPLE_DATA_SRC type samples
+ you need to shift the masks before doing the compare.
+
+ Although the value you are checking (perf_mem_data_src) is
+ specified as a bitfield so this might all fall apart if trying
+ to access the field in a cross-endian way. The Power people
+ were working on this issue, not sure if they resolved it.
+
+poll.2
+ Michael Kerrisk
+ Describe fifth argument (sigsetsize) of raw ppoll() system call
+
+process_vm_readv.2
+ Michael Kerrisk [Ville Ylenius]
+ Fix typo in example program
+
+readlink.2
+ Michael Kerrisk
+ Glibc falls back to readlink() on kernels that lack readlinkat()
+
+recv.2
+ Michael Kerrisk
+ 'addrlen' should be NULL (not 0) if we don't need sender address
+
+rename.2
+ Michael Kerrisk
+ Glibc falls back to rename() when the kernel doesn't have renameat()
+
+sigwaitinfo.2
+ Michael Kerrisk
+ The raw sigtimedwait() system call has a fifth argument
+
+symlink.2
+ Michael Kerrisk
+ Glibc falls back to symlink() on kernels that lack symlinkat()
+
+sysinfo.2
+ Michael Kerrisk
+ Add VERSIONS section
+
+unlink.2
+ Michael Kerrisk
+ Glibc falls back to unlink() or rmdir() on kernels that lack unlinkat()
+
+atoi.3
+ Michael Kerrisk
+ Downgrade discussion of atoq()
+ Remove most references to atoq() in this page, since this function
+ was present only in Linux libc (not glibc).
+
+cerf.3
+cexp2.3
+clog2.3
+ Michael Kerrisk
+ Update version number on "Not yet in glibc" sentence
+
+fgetgrent.3
+getgrent.3
+getgrent_r.3
+getgrnam.3
+ Michael Kerrisk [Rob Landley]
+ Clarify that 'gr_mem' is a NULL-terminated array of pointers
+
+fseeko.3
+ Michael Kerrisk
+ Add VERSIONS section
+
+ftw.3
+ Michael Kerrisk
+ Add VERSIONS section
+
+getauxval.3
+ Michael Kerrisk
+ Document ENOENT error
+ And add an entry to BUGS explaining the ambiguity that was
+ present before the addition of this error.
+
+getgrouplist.3
+ Michael Kerrisk
+ SEE ALSO: add group_member(3)
+
+getline.3
+ Rahul Bedarkar
+ Close opened file at end of example program
+
+memmem.3
+ Michael Kerrisk
+ Rewrite text of glibc 2.0 bug
+
+printf.3
+ Michael Kerrisk [Jakub Wilk]
+ Clarify details of the %n conversion specifier
+ See http://bugs.debian.org/756602
+ Michael Kerrisk [Jakub Wilk]
+ Note use of 'j', 'z', and 't' length modifiers for '%n'
+ See http://bugs.debian.org/756602
+ Michael Kerrisk
+ Update with some SUSv3 details
+
+setbuf.3
+ Michael Kerrisk
+ Remove ancient Linux libc and 4.x BSD details
+
+strstr.3
+ Michael Kerrisk
+ Remove discussion of Linux libc bugs
+ Linux libc is old enough that we needn't care any longer.
+
+strtod.3
+ Michael Kerrisk
+ Explain NAN(n-char-sequence)
+
+strtod.3
+ Michael Kerrisk
+ SEE ALSO: add nan(3), nanf(3), NANL(3)
+
+updwtmp.3
+ Michael Kerrisk
+ Replace AVAILABILITY section with note to link logwtmp() using -lutil
+ Linux libc details are no longer needed these days.
+
+core.5
+ Rahul Bedarkar
+ Close opened file in example program
+
+proc.5
+ Michael Kerrisk
+ Fix kernel version numbers for /proc/PID/stat fields
+
+proc.5
+ Jan Chaloupka
+ Add missing proc stats fields
+ Adding missing proc stats fields from
+ https://www.kernel.org/doc/Documentation/filesystems/proc.txt
+ Michael Kerrisk [Simon Paillard]
+ Remove crufty text under 'timer_stats'
+ Michael Kerrisk
+ Update /proc/PID/stat 'state' field documentation
+ Michael Kerrisk
+ Improve description of /proc/PID/stat fields added in Linux 3.3 and 3.5
+ Michael Kerrisk
+ Refer to getauxval(3) in discussion of /proc/PID/auxv
+ Michael Kerrisk
+ Rework formatting of /proc/PID/stat list
+ Make the field numbers more prominent.
+ Michael Kerrisk
+ Note that /proc/PID/cmdline is read-only
+ Michael Kerrisk
+ Rework discussion of CommitLimit and /proc/sys/vm/overcommit_memory
+ Michael Kerrisk
+ Improve discussion of /proc/sys/vm/overcommit_ratio
+
+charsets.7
+ David Prévot [Marko Myllynen]
+ Tidy up list
+ Remove German from main list, to be consistent with earlier
+ removal of Dutch and French (in commit a8ed5f7430e0d1).
+
+inotify.7
+ Michael Kerrisk
+ Note that IN_ONLY_DIR can be used to avoid races
+ Michael Kerrisk
+ Note that insertion of IN_MOVED_FROM+IN_MOVED_TO pair is not atomic
+ Michael Kerrisk
+ Mention use of timeout when reading IN_MOVED_TO after IN_MOVED_FROM
+
+man-pages.7
+ Michael Kerrisk
+ Add description of "C library/kernel ABI differences" subsection
+ Michael Kerrisk
+ Rework text describing sections (stylistic improvements)
+
+vdso.7
+ Mike Frysinger
+ Add new i386 vdso symbols in Linux 3.15
+ Michael Kerrisk
+ Note kernel version that exports new i386 symbols (Linux 3.15)
+
+
+==================== Changes in man-pages-3.72 ====================
+
+Released: 2014-09-07, Mountain View
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Christian von Roques <roques@mti.ag>
+Holger Hans Peter Freyther <holger@moiji-mobile.com>
+Michael Haardt <michael@moria.de>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Mike Frysinger <vapier@gentoo.org>
+Peter Schiffer <pschiffe@redhat.com>
+Rusty Russell <rusty@rustcorp.com.au>
+Sorin Dumitru <sdumitru@ixiacom.com>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+memusage.1
+ Peter Schiffer, Michael Kerrisk [Jan Chaloupka]
+ New page for glibc memusage(1) command
+
+memusagestat.1
+ Peter Schiffer [Jan Chaloupka, Michael Kerrisk]
+ New page for glibc memusagestat(1) command
+
+mtrace.1
+ Peter Schiffer [Jan Chaloupka]
+ New page describing the glibc mtrace(1) command
+
+
+Changes to individual pages
+---------------------------
+
+connect.2
+ Michael Haardt
+ Note that a new socket should be used if connect() fails
+
+fcntl.2
+ Michael Kerrisk
+ One must define _GNU_SOURCE to get the F_OFD_* definitions
+
+poll.2, select.2
+ Rusty Russell
+ Fix erroneous description of "available for write".
+ POSIX says: "POLLOUT Normal data may be written without
+ blocking.". This "may" is misleading, see the POSIX
+ write page:
+
+ Write requests to a pipe or FIFO shall be handled in the
+ same way as a regular file with the following exceptions:
+ ...
+ If the O_NONBLOCK flag is clear, a write request may cause
+ the thread to block, but on normal completion it shall
+ return nbyte.
+ ...
+ When attempting to write to a file descriptor (other than a
+ pipe or FIFO) that supports non-blocking writes and cannot
+ accept the data immediately:
+
+ If the O_NONBLOCK flag is clear, write() shall block the
+ calling thread until the data can be accepted.
+
+ If the O_NONBLOCK flag is set, write() shall not block the
+ thread. If some data can be written without blocking the
+ thread, write() shall write what it can and return the
+ number of bytes written. Otherwise, it shall return -1 and
+ set errno to [EAGAIN].
+
+ The net result is that write() of more than 1 byte on a
+ socket, pipe or FIFO which is "ready" may block: write()
+ (unlike read!) will attempt to write the entire buffer and
+ only return a short write under exceptional circumstances.
+
+ Indeed, this is the behaviour we see in Linux:
+
+ https://github.com/rustyrussell/ccan/commit/897626152d12d7fd13a8feb36989eb5c8c1f3485
+ https://plus.google.com/103188246877163594460/posts/BkTGTMHDFgZ
+
+errno.3
+ Michael Kerrisk
+ SEE ALSO: add errno(1)
+
+rtnetlink.3
+ Holger Hans Peter Freyther
+ Fix parameters for the send() call in the example
+
+inotify.7
+ Michael Kerrisk
+ IN_OPEN and IN_CLOSE_NOWRITE can also occur for directories
+ Michael Kerrisk
+ IN_CLOSE_WRITE occurs only for files (not monitored directory)
+ Michael Kerrisk
+ IN_MODIFY is generated for files only (not monitored directories)
+ Michael Kerrisk
+ IN_ACCESS occurs only for files inside directories
+ IN_ACCESS does not occur for monitored directory.
+
+packet.7
+ Sorin Dumitru
+ Fix include file
+ It looks like most of the socket options from this man pages
+ are not defined in <netpacket/packet.h>. They are defined in
+ <linux/if_packet.h> so we should include that one.
+
+
+==================== Changes in man-pages-3.73 ====================
+
+Released: 2014-09-21, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+David Prévot <taffit@debian.org>
+Eric W. Biederman <ebiederm@xmission.com>
+J. Bruce Fields <bfields@fieldses.org>
+Justin Cormack <justin@street-vision.com>
+Lorenzo Beretta <lory.fulgi@infinito.it>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Rob Landley <rob@landley.net>
+Serge E. Hallyn <serge@hallyn.com>
+Serge Hallyn <serge.hallyn@ubuntu.com>
+Vasily Kulikov <segoon@openwall.com>
+Vincent Lefevre <vincent@vinc17.net>
+Vitaly Rybnikov <frodox@zoho.com>
+Yuri Kozlov <yuray@komyakino.ru>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+namespaces.7
+ Michael Kerrisk [Eric W. Biederman]
+ New page providing overview of Linux namespaces
+
+pid_namespaces.7
+ Michael Kerrisk [Eric W. Biederman, Vasily Kulikov, Rob Landley,
+ Serge Hallyn]
+ New page describing PID namespaces
+
+user_namespaces.7
+ Michael Kerrisk [Eric W. Biederman, Andy Lutomirski, Serge Hallyn]
+ New page describing user namespaces.
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+clone.2
+ Eric W. Biederman [Michael Kerrisk]
+ Document CLONE_NEWUSER for creating a new user namespace
+
+setns.2
+ Eric W. Biederman, Michael Kerrisk
+ Document the PID, user, and mount namespace support
+ Document CLONE_NEWPID, CLONE_NEWUSER, and CLONE_NEWNS flags.
+
+unshare.2
+ Michael Kerrisk [Eric W. Biederman]
+ Document CLONE_NEWPID
+ Michael Kerrisk [Eric W. Biederman]
+ Document CLONE_NEWUSER
+ Michael Kerrisk
+ Document CLONE_THREAD, CLONE_SIGHAND, and CLONE_VM
+
+
+Changes to individual pages
+---------------------------
+
+clone.2
+ Michael Kerrisk
+ Move some CLONE_NEWNET text to namespaces.7
+ Michael Kerrisk
+ Move some CLONE_NEWUTS text 2 to namespaces.7
+ Michael Kerrisk
+ Move some CLONE_NEWIPC text to namespaces.7
+ Michael Kerrisk
+ Reword discussion of CLONE_NEWNS, removing text also in namespaces(7)
+ Michael Kerrisk
+ Standardize text on CLONE_NEW* flags and CAP_SYS_ADMIN
+ Michael Kerrisk
+ EINVAL if (CLONE_NEWUSER|CLONE_NEWPID) && (CLONE_THREAD|CLONE_PARENT)
+ Michael Kerrisk
+ Add more detail on the meaning of CLONE_SYSVSEM
+
+flock.2
+ Michael Kerrisk [J. Bruce Fields]
+ Don't mention "classical BSD" in discussion of fcntl()/flock interaction
+ The noninteraction of flock(2) and fcntl(2) locks does
+ not seem to be classical BSD semantics (at least, checking
+ the 4.4BSD sources suggest that the lock types do interact,
+ although there have been other systems also where fcntl()
+ and flock() locks do not interact). So, fix the text
+ discussing "classical BSD" lock semantics.
+
+getunwind.2
+ Michael Kerrisk [Yuri Kozlov]
+ Fix description of return value
+ s/size of unwind table/size of the unwind data/
+
+mount.2
+ Eric W. Biederman
+ Clarify use of 'mountflags' and 'data' for MS_REMOUNT
+
+reboot.2
+ Michael Kerrisk [Justin Cormack, Eric W. Biederman]
+ Document effect of reboot() inside PID namespaces
+
+semop.2
+ Michael Kerrisk
+ Refer to clone(2) for semantics of CLONE_SYSVSEM and semadj lists
+
+seteuid.2
+setgid.2
+setresuid.2
+setreuid.2
+setuid.2
+ Michael Kerrisk
+ EINVAL can occur if UID/GID is not valid in caller's user namespace
+
+setns.2
+ Michael Kerrisk [Eric W. Biederman]
+ Clarify capabilities required for reassociating with a mount namespace
+ Michael Kerrisk
+ Specify kernel version on each CLONE_NEW* flag
+ And remove text on flags from VERSIONS.
+
+unshare.2
+ Michael Kerrisk
+ Add an example program
+ Michael Kerrisk
+ Clarify semantics of CLONE_SYSVSEM
+ Michael Kerrisk
+ CLONE_SYSVSEM does not require CAP_SYS_ADMIN
+ Michael Kerrisk
+ Note flags implied by CLONE_THREAD and CLONE_VM
+
+clock.3
+ Michael Kerrisk [Vincent Lefevre]
+ The implementation uses clock_gettime() was to improve *accuracy*
+ (The man page text mistakenly used the word "precision".)
+
+drand48.3
+ Michael Kerrisk [Lorenzo Beretta]
+ Remove crufty text about SVID 3 marking drand48() obsolete
+ See http://bugs.debian.org/758293
+
+proc.5
+ Michael Kerrisk
+ Move /proc/[pid]/mounts text to namespaces.7
+ Michael Kerrisk
+ Move /proc/[pid]/mountstats text to namespaces.7
+
+capabilities.7
+ Michael Kerrisk
+ Refer reader to user_namespaces(7) for a discussion of capabilities
+ Michael Kerrisk
+ Document CAP_SETUID and CAP_SETGID for user namespace mappings
+ Michael Kerrisk
+ setns() needs CAP_SYS_ADMIN in the *target* namespace
+ Michael Kerrisk
+ Since Linux 3.8, user namespaces no longer require CAP_SYS_ADMIN
+
+mq_overview.7
+ Michael Kerrisk
+ Refer to namespaces(7) for info on POSIX MQs and IPC namespaces
+
+svipc.7
+ Michael Kerrisk
+ Refer to namespaces(7) for info on System V IPC and IPC namespaces
+
+
+==================== Changes in man-pages-3.74 ====================
+
+Released: 2014-10-03, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Arto Bendiken <arto@bendiken.net>
+Ben Hutchings <ben@decadent.org.uk>
+Benjamin Herr <ben@0x539.de>
+C. Alex North-Keys <erlkonig@talisman.org>
+Carlos O'Donell <carlos@redhat.com>
+Cyril Hrubis <chrubis@suse.cz>
+Davidlohr Bueso <dave@stgolabs.net>
+Doug Ledford <dledford@redhat.com>
+Elie De Brauwer <eliedebrauwer@gmail.com>
+Heinrich Schuchardt <xypron.glpk@gmx.de>
+Jonny Grant <jg@jguk.org>
+Lanchon <lanchon@gmail.com>
+Manfred Spraul <manfred@colorfullife.com>
+Marko Myllynen <myllynen@redhat.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Shriramana Sharma <samjnaa@gmail.com>
+Thomas Mack <mack@ifis.cs.tu-bs.de>
+Wieland Hoffmann <themineo@gmail.com>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+pldd.1
+ Michael Kerrisk
+ New page for pldd(1) command added to glibc in version 2.15
+
+cp1252.7
+ Marko Myllynen
+ New page documenting CP 1252
+ CP 1252 is probably one of the most used Windows Code Pages so
+ let's add a page for it alongside with the already provided
+ CP 1251 page.
+
+ Table generated from /usr/share/i18n/charmaps/CP1252.
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+mq_overview.7
+ Michael Kerrisk
+ Document /proc/sys/fs/mqueue/msgsize_default
+ Michael Kerrisk
+ Document /proc/sys/fs/mqueue/msg_default
+
+
+Changes to individual pages
+---------------------------
+
+ldd.1
+ Michael Kerrisk
+ SEE ALSO: add pldd(1)
+
+execve.2
+ Michael Kerrisk [C. Alex North-Keys]
+ Remove unneeded ".sh" extension in interpreter script example
+ See https://bugzilla.kernel.org/show_bug.cgi?id=84701
+
+fanotify_init.2
+ Heinrich Schuchardt
+ BUGS: O_CLOEXEC is ignored
+ Michael Kerrisk [Heinrich Schuchardt]
+ The 'event_f_flags' failure to check invalid flags was fixed in 3.15
+
+fanotify_mark.2
+ Michael Kerrisk
+ Note that various bugs were fixed in Linux 3.16
+
+getrlimit.2
+ Michael Kerrisk [Doug Ledford]
+ Since Linux 3.5, the accounting formula for RLIMIT_MSGQUEUE has changed
+
+open.2
+ Michael Kerrisk [Shriramana Sharma]
+ Fix number and formula in description of EOVERFLOW error
+
+readlink.2
+ Michael Kerrisk [Ben Hutchings]
+ Fix description of readlinkat() with empty 'pathname'
+ Michael Kerrisk
+ SEE ALSO: add realpath(3)
+
+sched_setattr.2
+sched_setscheduler.2
+ Michael Kerrisk
+ SEE ALSO: add chrt(1)
+
+shmget.2
+ Manfred Spraul [Michael Kerrisk, Davidlohr Bueso]
+ Update for increase of SHMALL and SHMMAX
+ The default values of SHMALL and SHMMAX have been increased.
+
+syscalls.2
+ Michael Kerrisk
+ Add 3 new system calls added in Linux 3.17
+
+vmsplice.2
+ Cyril Hrubis
+ vmsplice() does not fail when nr_segs==0
+ This nr_segs==0 case is no-op; the call succeeds and no
+ EINVAL error is returned.
+
+dlopen.3
+ Michael Kerrisk
+ SEE ALSO: add pldd(1)
+
+fseeko.3
+ Michael Kerrisk [Thomas Mack]
+ _FILE_OFFSET_BITS must be defined before including any header file
+
+getgrent.3
+ Carlos O'Donell
+ Add ENOENT and EAGAIN to error list
+
+mq_getattr.3
+ Michael Kerrisk
+ Add an example program
+ The example program can be used to discover the default
+ 'mq_maxmsg' and 'mq_msgsize' values used to create a queue with
+ a mq_open(3) call in which 'attr' is NULL.
+
+mq_open.3
+ Michael Kerrisk
+ Two /proc files control the defaults for the attrp==NULL case
+ Refer the reader to the discussion in mq_overview(7) for a
+ discussion of these files, which exist since Linux 3.5.
+
+realpath.3
+ Michael Kerrisk
+ SEE ALSO: add realpath(1)
+
+proc.5
+ Elie De Brauwer
+ Document /proc/buddyinfo
+ This patch adds a short description about the contents of
+ /proc/buddyinfo and how this file can be used to assist
+ in checking for memory fragmentation issues.
+ Michael Kerrisk
+ Mention pmap(1) in discussion of /proc/PID/smaps
+
+armscii-8.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+ascii.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+ This and [the related *.7] patches will provide unification of
+ charset pages, minor cleanups, and some unifying cosmetic
+ changes. References are adjusted so that all pages include
+ a reference to charsets(7), which contains a description of
+ these sets, stray comments are removed, some obsolete
+ statements (like ISO 8859-1 being the de-facto ASCII
+ replacement) are removed, and some minor reformatting
+ to minimize diff's between the pages are done.
+
+ The actual substance, the character tables, remain unchanged.
+
+ This series changes the following pages (under man7): ascii,
+ armscii, cp1251, koi8-r, koi8-u, and all of iso_8859-*.
+
+cp1251.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-10.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-11.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-13.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-14.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-15.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-16.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-1.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-2.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-3.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-4.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-5.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-6.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-7.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-8.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+iso_8859-9.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+
+koi8-r.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+ - remove stray comments, streamline description
+ (charsets(7) and Wikipedia provide more detailed
+ and up-to-date description)
+ - list differences between koi8-r.7 vs koi8-u.7
+
+koi8-u.7
+ Marko Myllynen
+ Charset pages unification, minor cleanups
+ - remove stray comments, streamline description
+ (charsets(7) and Wikipedia provide more detailed
+ and up-to-date description)
+ - list differences between koi8-r.7 vs koi8-u.7
+
+mq_overview.7
+ Michael Kerrisk
+ Update queues_max details for Linux 3.14
+ And in general rework the text a little.
+ Michael Kerrisk
+ Update discussion of HARD_MSGMAX
+ The limit has changed in 2.6.33 and then again in 3.5.
+ Michael Kerrisk [Arto Bendiken]
+ Update details for 'queues_max' limit
+ Things changed in Linux 3.5.
+ See https://bugs.launchpad.net/bugs/1155695
+ Michael Kerrisk
+ Update details on defaults and ceiling for 'msgsize_max' limit
+ Michael Kerrisk
+ Rework discussion of HARD_MSGMAX
+ Michael Kerrisk [Davidlohr Bueso]
+ Various fixes after review from Davidlohr Bueso
+
+sched.7
+ Michael Kerrisk
+ SEE ALSO: add taskset(1)
+
+ld.so.8
+ Michael Kerrisk
+ SEE ALSO: add pldd(1)
+ Michael Kerrisk
+ SEE ALSO: add dlopen(3)
+ Michael Kerrisk
+ SEE ALSO: add ld(1)
+
RELEASE
The Linux man page maintainer proudly announces. . .
- man-pages-3.68.tar.gz - man pages for Linux
+ man-pages-3.75.tar.gz - man pages for Linux
Differences from the previous manual pages release are listed in
the file "Changes".
Begin3
Title: Section 2, 3, 4, 5 and 7 man pages for Linux
-Version: 3.68
-Entered-date: 2014-05-28
+Version: 3.75
+Entered-date: 2014-10-15
Description: Linux manual pages
Keywords: man pages
Author: several
Maintained-by: Michael Kerrisk <mtk.manpages@gmail.com>
Primary-site: ftp://ftp.kernel.org/pub/linux/docs/man-pages
- 1992k man-pages-3.68.tar.gz
+ 2058k man-pages-3.75.tar.gz
Alternate-site: ftp://ftp.win.tue.nl/pub/linux-local/manpages
Copying-policy: several; the pages are all freely distributable as long as
nroff source is provided
.SH SEE ALSO
.BR nsswitch.conf (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
--- /dev/null
+'\" t -*- coding: UTF-8 -*-
+.\"
+.\" Copyright (C) 2014 Marko Myllynen <myllynen@redhat.com>
+.\"
+.\" %%%LICENSE_START(GPLv2+_DOC_FULL)
+.\" This is free documentation; you can redistribute it and/or
+.\" modify it under the terms of the GNU General Public License as
+.\" published by the Free Software Foundation; either version 2 of
+.\" the License, or (at your option) any later version.
+.\"
+.\" The GNU General Public License's references to "object code"
+.\" and "executables" are to be interpreted as the output of any
+.\" document formatting or typesetting system, including
+.\" intermediate and printed output.
+.\"
+.\" This manual is distributed in the hope that it will be useful,
+.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
+.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+.\" GNU General Public License for more details.
+.\"
+.\" You should have received a copy of the GNU General Public
+.\" License along with this manual; if not, see
+.\" <http://www.gnu.org/licenses/>.
+.\" %%%LICENSE_END
+.\"
+.TH ICONV 1 2014-07-08 "GNU" "Linux User Manual"
+.SH NAME
+iconv \- convert text from one character encoding to another
+.SH SYNOPSIS
+.B iconv
+.RI [ options ]
+.RI "[-f " from-encoding "]"
+.RI "[-t " to-encoding "]"
+.RI [ inputfile ]...
+.SH DESCRIPTION
+The
+.B iconv
+program reads in text in one encoding and outputs the text in another
+encoding.
+If no input files are given, or if it is given as a dash (\-),
+.B iconv
+reads from standard input.
+If no output file is given,
+.B iconv
+writes to standard output.
+.PP
+If no
+.I from-encoding
+is given, the default is derived
+from the current locale's character encoding.
+If no
+.I to-encoding
+is given, the default is derived
+from the current locale's character
+encoding.
+.SH OPTIONS
+.TP
+.BI \-f " from-encoding" ", \-\-from-code=" from-encoding
+Use
+.I from-encoding
+for input characters.
+.TP
+.BI \-t " to-encoding" ", \-\-to-code=" to-encoding
+Use
+.I to-encoding
+for output characters.
+
+If the string
+.BR //IGNORE
+is appended to
+.IR to-encoding ,
+characters that cannot be converted are discarded and an error is
+printed after conversion.
+
+If the string
+.BR //TRANSLIT
+is appended to
+.IR to-encoding ,
+characters being converted are transliterated when needed and possible.
+This means that when a character cannot be represented in the target
+character set, it can be approximated through one or several similar
+looking characters.
+Characters that are outside of the target character set and cannot be
+transliterated are replaced with a question mark (?) in the output.
+.TP
+.BR \-l ", " \-\-list
+List all known character set encodings.
+.TP
+.B "\-c"
+Silently discard characters that cannot be converted instead of
+terminating when encountering such characters.
+.TP
+.BI \-o " outputfile" ", \-\-output=" outputfile
+Use
+.I outputfile
+for output.
+.TP
+.BR \-s ", " \-\-silent
+This option is ignored; it is provided only for compatibility.
+.TP
+.B "\-\-verbose"
+Print progress information on standard error when processing
+multiple files.
+.TP
+.BR \-? ", " \-\-help
+Print a usage summary and exit.
+.TP
+.B "\-\-usage"
+Print a short usage summary and exit.
+.TP
+.BR \-V ", " \-\-version
+Print the version number, license, and disclaimer of warranty for
+.BR iconv .
+.SH EXIT STATUS
+Zero on success, non-zero on errors.
+.SH ENVIRONMENT
+Internally, the
+.B iconv
+program uses the
+.BR iconv (3)
+function which in turn uses
+.I gconv
+modules (dynamically loaded shared libraries)
+to convert to and from a character set.
+Before calling
+.BR iconv (3),
+the
+.B iconv
+program must first allocate a conversion descriptor using
+.BR iconv_open (3).
+The operation of the latter function is influenced by the setting of the
+.B GCONV_PATH
+environment variable:
+.IP * 3
+If
+.B GCONV_PATH
+is not set,
+.BR iconv_open (3)
+loads the system gconv module configuration cache file created by
+.BR iconvconfig (8)
+and then, based on the configuration,
+loads the gconv modules needed to perform the conversion.
+If the system gconv module configuration cache file is not available
+then the system gconv module configuration file is used.
+.IP *
+If
+.B GCONV_PATH
+is defined (as a colon-separated list of pathnames),
+the system gconv module configuration cache is not used.
+Instead,
+.BR iconv_open (3)
+first tries to load the configuration files by searching the directories in
+.BR GCONV_PATH
+in order,
+followed by the system default gconv module configuration file.
+If a directory does not contain a gconv module configuration file,
+any gconv modules that it may contain are ignored.
+If a directory contains a gconv module configuration file
+and it is determined that a module needed for this conversion is
+available in the directory,
+then the needed module is loaded from that directory,
+the order being such that the first suitable module found in
+.B GCONV_PATH
+is used.
+This allows users to use custom modules and even replace system-provided
+modules by providing such modules in
+.B GCONV_PATH
+directories.
+.SH FILES
+.TP
+.I /usr/lib/gconv
+Usual default gconv module path.
+.TP
+.I /usr/lib/gconv/gconv-modules
+Usual system default gconv module configuration file.
+.TP
+.I /usr/lib/gconv/gconv-modules.cache
+Usual system gconv module configuration cache.
+.SH CONFORMING TO
+POSIX.1-2001.
+.SH EXAMPLE
+Convert text from the ISO 8859-15 character encoding to UTF-8:
+
+.in +4n
+.nf
+$ \fBiconv \-f ISO\-8859\-15 -t UTF\-8 < input.txt > output.txt\fP
+.fi
+.in
+.PP
+The next example converts from UTF-8 to ASCII, transliterating when
+possible:
+
+.in +4n
+.nf
+$ \fBecho abc ß α € àḃç | iconv \-f UTF\-8 \-t ASCII//TRANSLIT\fP
+abc ss ? EUR abc
+.fi
+.in
+.SH "SEE ALSO"
+.BR locale (1),
+.BR iconv (3),
+.BR nl_langinfo (3),
+.BR charsets (7),
+.BR iconvconfig (8)
+.SH COLOPHON
+This page is part of release 3.75 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.
all user commands under UNIX work precisely the same under
Linux (and FreeBSD and lots of other UNIX-like systems).
.LP
-Under Linux there are GUIs (graphical user interfaces), where you
+Under Linux, there are GUIs (graphical user interfaces), where you
can point and click and drag, and hopefully get work done without
first reading lots of documentation.
The traditional UNIX environment
.SH SEE ALSO
.BR standards (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" May be distributed under the GNU General Public License
.\" %%%LICENSE_END
.\"
-.TH LDD 1 2012-07-16 "" "Linux Programmer's Manual"
+.TH LDD 1 2014-10-02 "" "Linux Programmer's Manual"
.SH NAME
ldd \- print shared library dependencies
.SH SYNOPSIS
-.BR ldd " [OPTION]... FILE..."
+.BR ldd " [\fIoption\fP]... \fIfile\fP..."
.SH DESCRIPTION
.B ldd
prints the shared libraries required by each program or shared library
.TP
.B \-\-help
Usage information.
-.SH NOTES
-The standard version of
-.B ldd
-comes with glibc2.
-Libc5 came with an older version, still present
-on some systems.
-The long options are not supported by the libc5 version.
-On the other hand, the glibc2 version does not support
-.B \-V
-and only has the equivalent
-.BR \-\-version .
-.LP
-The libc5 version of this program will use the name of a library given
-on the command line as-is when it contains a \(aq/\(aq; otherwise it
-searches for the library in the standard locations.
-To run it
-on a shared library in the current directory, prefix the name with "./".
+.\" .SH NOTES
+.\" The standard version of
+.\" .B ldd
+.\" comes with glibc2.
+.\" Libc5 came with an older version, still present
+.\" on some systems.
+.\" The long options are not supported by the libc5 version.
+.\" On the other hand, the glibc2 version does not support
+.\" .B \-V
+.\" and only has the equivalent
+.\" .BR \-\-version .
+.\" .LP
+.\" The libc5 version of this program will use the name of a library given
+.\" on the command line as-is when it contains a \(aq/\(aq; otherwise it
+.\" searches for the library in the standard locations.
+.\" To run it
+.\" on a shared library in the current directory, prefix the name with "./".
.SH BUGS
.B ldd
does not work on a.out shared libraries.
.\" David Engel.
.\" Roland McGrath and Ulrich Drepper.
.SH SEE ALSO
+.BR sprof (1),
+.BR pldd (1),
.BR ld.so (8),
.BR ldconfig (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH LOCALE 1 2014-05-28 "Linux" "Linux Programmer's Manual"
+.TH LOCALE 1 2014-05-28 "Linux" "Linux User Manual"
.SH NAME
locale \- get locale-specific information
.SH SYNOPSIS
.nf
-.BR locale " [OPTION]"
-.BR locale " [OPTION] \-a"
-.BR locale " [OPTION] \-m"
-.BR locale " [OPTION] NAME..."
+.BR locale " [\fIoption\fP]"
+.BR locale " [\fIoption\fP] \-a"
+.BR locale " [\fIoption\fP] \-m"
+.BR locale " [\fIoption\fP] \fIname\fP..."
.fi
.SH DESCRIPTION
The
.TP
.BR \-V ", " \-\-version
Display the program version and exit.
+.SH FILES
+.TP
+.I /usr/lib/locale/locale-archive
+Usual default locale archive location.
+.TP
+.I /usr/share/i18n/locales
+Usual default path for locale definition files.
.SH CONFORMING TO
-POSIX.1-2001, POSIX.1-2008
+POSIX.1-2001, POSIX.1-2008.
.SH EXAMPLE
.nf
$ \fBlocale\fP
.fi
.SH SEE ALSO
.BR localedef (1),
+.BR charmap (5),
.BR locale (5),
.BR locale (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Lars Wirzenius to document new functionality (as of GNU
.\" C library 2.3.5).
.\"
-.TH LOCALEDEF 1 2014-05-26 "Linux" "Linux Programmer's Manual"
+.TH LOCALEDEF 1 2014-06-13 "Linux" "Linux User Manual"
.SH NAME
localedef \- compile locale definition files
.SH SYNOPSIS
generally, it should be self-evident which ones.
.TP
.BI \-f " charmapfile" ", \-\-charmap=" charmapfile
-Specify the file that defines the symbolic character names
-that are used by the input file.
+Specify the file that defines the character set
+that is used by the input file.
If
.I charmapfile
contains a slash character ('/'),
.BR "localedef \-\-help" .
.TP
.BI \-u " repertoirefile" ", \-\-repertoire-map=" repertoirefile
-Read mappings from symbolic names to Unicode UCS4 values from
+Read mappings from symbolic names to Unicode code points from
.IR repertoirefile .
If
.I repertoirefile
the archive would be placed in
.IR foo/usr/lib/locale/locale-archive .
.TP
-.B "\-c, \-\-force"
+.BR \-c ", " \-\-force
Write the output files even if warnings were generated about the input
file.
.TP
.B \-\-old\-style
Create old-style hash tables instead of 3-level access tables.
.TP
-.B "\-v, \-\-verbose"
+.BR \-v ", " \-\-verbose
Generate extra warnings about errors that are normally ignored.
.TP
.B \-\-quiet
as a subdirectory in the same directory as the locale archive file,
and create separate output files for locale categories in it.
.TP
-.B "\-\-help"
+.BR \-? ", " \-\-help
Print a usage summary and exit.
Also prints the default paths used by
.BR localedef .
.B "\-\-usage"
Print a short usage summary and exit.
.TP
-.B "\-V, \-\-version"
+.BR \-V ", " \-\-version
Print the version number, license, and disclaimer of warranty for
.BR localedef .
.SH EXIT STATUS
Usual default locale archive location.
.TP
.I outputpath/LC_ADDRESS
-An output file that contains contains information about formatting of
+An output file that contains information about formatting of
addresses and geography-related items.
.TP
.I outputpath/LC_COLLATE
.RE
.SH "SEE ALSO"
.BR locale (1),
+.BR charmap (5),
.BR locale (5),
+.BR repertoiremap (5),
.BR locale (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
--- /dev/null
+.\" Copyright (c) 2013, Peter Schiffer <pschiffe@redhat.com>
+.\" and Copyright (C) 2014, Michael Kerrisk <mtk.manpages@gmail.com>
+.\"
+.\" %%%LICENSE_START(GPLv2+_DOC_FULL)
+.\" This is free documentation; you can redistribute it and/or
+.\" modify it under the terms of the GNU General Public License as
+.\" published by the Free Software Foundation; either version 2 of
+.\" the License, or (at your option) any later version.
+.\"
+.\" The GNU General Public License's references to "object code"
+.\" and "executables" are to be interpreted as the output of any
+.\" document formatting or typesetting system, including
+.\" intermediate and printed output.
+.\"
+.\" This manual is distributed in the hope that it will be useful,
+.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
+.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+.\" GNU General Public License for more details.
+.\"
+.\" You should have received a copy of the GNU General Public
+.\" License along with this manual; if not, see
+.\" <http://www.gnu.org/licenses/>.
+.\" %%%LICENSE_END
+.TH MEMUSAGE 1 2014-09-06 "GNU" "Linux user manual"
+.SH NAME
+memusage \- profile memory usage of a program
+.SH SYNOPSIS
+.BR memusage " [\fIoption\fR]... \fIprogram\fR [\fIprogramoption\fR]..."
+.SH DESCRIPTION
+.B memusage
+is a bash script which profiles memory usage of the program,
+.IR program .
+It preloads the
+.B libmemusage.so
+library into the caller's environment (via the
+.B LD_PRELOAD
+environment variable; see
+.BR ld.so (8)).
+The
+.B libmemusage.so
+library traces memory allocation by intercepting calls to
+.BR malloc (3),
+.BR calloc (3),
+.BR free (3),
+and
+.BR realloc (3);
+optionally, calls to
+.BR mmap (2),
+.BR mremap (2),
+and
+.BR munmap (2)
+can also be intercepted.
+.PP
+.B memusage
+can output the collected data in textual form, or it can use
+.BR memusagestat (1)
+(see the
+.B -p
+option, below)
+to create a PNG file containing graphical representation
+of the collected data.
+.SS Memory usage summary
+The "Memory usage summary" line output by
+.BR memusage
+contains three fields:
+.RS 4
+.TP
+\fBheap total\fR
+Sum of \fIsize\fR arguments of all
+.BR malloc (3)
+calls,
+products of arguments (\fInmemb\fR*\fIsize\fR) of all
+.BR calloc (3)
+calls,
+and sum of \fIlength\fR arguments of all
+.BR mmap (2)
+calls.
+In the case of
+.BR realloc (3)
+and
+.BR mremap (2),
+if the new size of an allocation is larger than the previous size,
+the sum of all such differences (new size minus old size) is added.
+.TP
+.B "heap peak"
+Maximum of all \fIsize\fR arguments of
+.BR malloc (3),
+all products of \fInmemb\fR*\fIsize\fR of
+.BR calloc (3),
+all \fIsize\fR arguments of
+.BR realloc (3),
+.I length
+arguments of
+.BR mmap (2),
+and
+\fInew_size\fR arguments of
+.BR mremap (2).
+.TP
+.B "stack peak"
+Before the first call to any monitored function,
+the stack pointer address (base stack pointer) is saved.
+After each function call, the actual stack pointer address is read and
+the difference from the base stack pointer computed.
+The maximum of these differences is then the stack peak.
+.RE
+.PP
+Immediately following this summary line, a table shows the number calls,
+total memory allocated or deallocated,
+and number of failed calls for each intercepted function.
+For
+.BR realloc (3)
+and
+.BR mremap (2),
+the additional field "nomove" shows reallocations that
+changed the address of a block,
+and the additional "dec" field shows reallocations that
+decreased the size of the block.
+For
+.BR realloc (3),
+the additional field "free" shows reallocations that
+caused a block to be freed (i.e., the reallocated size was 0).
+
+
+The "realloc/total memory" of the table output by
+.B memusage
+does not reflect cases where
+.BR realloc (3)
+is used to reallocate a block of memory
+to have a smaller size than previously.
+This can cause sum of all "total memory" cells (excluding "free")
+to be larger than the "free/total memory" cell.
+.SS Histogram for block sizes
+The "Histogram for block sizes" provides a breakdown of memory
+allocations into various bucket sizes.
+.SH OPTIONS
+.TP
+.BI \-n\ name \fR,\ \fB\-\-progname= name
+Name of the program file to profile.
+.TP
+.BI \-p\ file \fR,\ \fB\-\-png= file
+Generate PNG graphic and store it in
+.IR file .
+.TP
+.BI \-d\ file \fR,\ \fB\-\-data= file
+Generate binary data file and store it in
+.IR file .
+.TP
+.BI \-u\fR,\ \fB\-\-unbuffered
+Do not buffer output.
+.TP
+.BI \-b\ size \fR,\ \fB\-\-buffer= size
+Collect
+.I size
+entries before writing them out.
+.TP
+.BI \fB\-\-no-timer
+Disable timer-based
+.RB ( SIGPROF )
+sampling of stack pointer value.
+.TP
+.BI \-m\fR,\ \fB\-\-mmap
+Also trace
+.BR mmap (2),
+.BR mremap (2),
+and
+.BR mmap (2).
+.TP
+.BI \-?\fR,\ \fB\-\-help
+Print help and exit.
+.TP
+.BI \fB\-\-usage
+Print a short usage message and exit.
+.TP
+.BI \-V\fR,\ \fB\-\-version
+Print version information and exit.
+.TP
+The following options only apply when generating graphical output:
+.TP
+.BI \-t\fR,\ \fB\-\-time\-based
+Use time (rather than number of function calls) as the scale for the X axis.
+.TP
+.BI \-T\fR,\ \fB\-\-total
+Also draw a graph of total memory use.
+.TP
+.BI \fB\-\-title= name
+Use
+.I name
+as the title of the graph.
+.TP
+.BI \-x\ size \fR,\ \fB\-\-x\-size= size
+Make the graph
+.I size
+pixels wide.
+.TP
+.BI \-y\ size \fR,\ \fB\-\-y\-size= size
+Make the graph
+.I size
+pixels high.
+.SH EXIT STATUS
+Exit status is equal to the exit status of profiled program.
+.SH EXAMPLE
+Below is a simple program that reallocates a block of
+memory in cycles that rise to a peak before then cyclically
+reallocating the memory in smaller blocks that return to zero.
+After compiling the program and running the following commands,
+a graph of the memory usage of the program can be found in the file
+.IR memusage.png :
+
+.in +4n
+.nf
+$ \fBmemusage --data=memusage.dat ./a.out\fP
+\&...
+Memory usage summary: heap total: 45200, heap peak: 6440, stack peak: 224
+ total calls total memory failed calls
+ malloc| 1 400 0
+realloc| 40 44800 0 (nomove:40, dec:19, free:0)
+ calloc| 0 0 0
+ free| 1 440
+Histogram for block sizes:
+ 192-207 1 2% ================
+\&...
+ 2192-2207 1 2% ================
+ 2240-2255 2 4% =================================
+ 2832-2847 2 4% =================================
+ 3440-3455 2 4% =================================
+ 4032-4047 2 4% =================================
+ 4640-4655 2 4% =================================
+ 5232-5247 2 4% =================================
+ 5840-5855 2 4% =================================
+ 6432-6447 1 2% ================
+$ \fBmemusagestat memusage.dat memusage.png\fP
+.fi
+.in
+.SS Program source
+.nf
+#include <stdio.h>
+#include <stdlib.h>
+
+#define CYCLES 20
+
+int
+main(int argc, char *argv[])
+{
+ int i, j;
+ int *p;
+
+ printf("malloc: %zd\\n", sizeof(int) * 100);
+ p = malloc(sizeof(int) * 100);
+
+ for (i = 0; i < CYCLES; i++) {
+ if (i < CYCLES / 2)
+ j = i;
+ else
+ j--;
+
+ printf("realloc: %zd\\n", sizeof(int) * (j * 50 + 110));
+ p = realloc(p, sizeof(int) * (j * 50 + 100));
+
+ printf("realloc: %zd\\n", sizeof(int) * ((j+1) * 150 + 110));
+ p = realloc(p, sizeof(int) * ((j + 1) * 150 + 110));
+ }
+
+ free(p);
+ exit(EXIT_SUCCESS);
+}
+.fi
+.SH BUGS
+To report bugs, see
+.UR http://www.gnu.org/software/libc/bugs.html
+.UE
+.SH SEE ALSO
+.BR memusagestat (1),
+.BR mtrace (1)
+.BR ld.so (8)
+.SH COLOPHON
+This page is part of release 3.75 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.
--- /dev/null
+.\" Copyright (c) 2013, Peter Schiffer <pschiffe@redhat.com>
+.\"
+.\" %%%LICENSE_START(GPLv2+_DOC_FULL)
+.\" This is free documentation; you can redistribute it and/or
+.\" modify it under the terms of the GNU General Public License as
+.\" published by the Free Software Foundation; either version 2 of
+.\" the License, or (at your option) any later version.
+.\"
+.\" The GNU General Public License's references to "object code"
+.\" and "executables" are to be interpreted as the output of any
+.\" document formatting or typesetting system, including
+.\" intermediate and printed output.
+.\"
+.\" This manual is distributed in the hope that it will be useful,
+.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
+.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+.\" GNU General Public License for more details.
+.\"
+.\" You should have received a copy of the GNU General Public
+.\" License along with this manual; if not, see
+.\" <http://www.gnu.org/licenses/>.
+.\" %%%LICENSE_END
+.TH MEMUSAGESTAT 1 2014-09-06 "GNU" "Linux programmer's manual"
+.SH NAME
+memusagestat \- generate graphic from memory profiling data
+.SH SYNOPSIS
+.BR memusagestat " [\fIoption\fR]... \fIdatafile\fR [\fIoutfile\fR]"
+.SH DESCRIPTION
+.B memusagestat
+creates a PNG file containing a graphical representation of the
+memory profiling data in the file
+.IR datafile ;
+that file is generated via the
+.I -d
+(or
+.IR --data )
+option of
+.BR memusage (1).
+
+The red line in the graph shows the heap usage (allocated memory)
+and the green line shows the stack usage.
+The x-scale is either the number of memory-handling function calls or
+(if the
+.I -t
+option is specified)
+time.
+.SH OPTIONS
+.TP
+.BI \-o\ file \fR,\ \fB\-\-output= file
+Name of the output file.
+.TP
+.BI \-s\ string \fR,\ \fB\-\-string= string
+Use
+.I string
+as the title inside the output graph.
+.TP
+.BI \-t\fR,\ \fB\-\-time
+Use time (rather than number of function calls) as the scale for the X axis.
+.TP
+.BI \-T\fR,\ \fB\-\-total
+Also draw a graph of total memory consumption.
+.TP
+.BI \-x\ size \fR,\ \fB\-\-x-size= size
+Make the output graph
+.I size
+pixels wide.
+.TP
+.BI \-y\ size \fR,\ \fB\-\-y\-size= size
+Make the output graph
+.I size
+pixels high.
+.TP
+.BI \-?\fR,\ \fB\-\-help
+Print a help message and exit.
+.TP
+.BI \fB\-\-usage
+Print a short usage message and exit.
+.TP
+.BI \-V\fR,\ \fB\-\-version
+Print version information and exit.
+.SH EXAMPLE
+See
+.BR memusage (1).
+.SH BUGS
+To report bugs, see
+.UR http://www.gnu.org/software/libc/bugs.html
+.UE
+.SH SEE ALSO
+.BR memusage (1),
+.BR mtrace (1)
+.SH COLOPHON
+This page is part of release 3.75 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.
--- /dev/null
+.\" Copyright (c) 2013, Peter Schiffer (pschiffe@redhat.com)
+.\"
+.\" %%%LICENSE_START(GPLv2+_DOC_FULL)
+.\" This is free documentation; you can redistribute it and/or
+.\" modify it under the terms of the GNU General Public License as
+.\" published by the Free Software Foundation; either version 2 of
+.\" the License, or (at your option) any later version.
+.\"
+.\" The GNU General Public License's references to "object code"
+.\" and "executables" are to be interpreted as the output of any
+.\" document formatting or typesetting system, including
+.\" intermediate and printed output.
+.\"
+.\" This manual is distributed in the hope that it will be useful,
+.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
+.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+.\" GNU General Public License for more details.
+.\"
+.\" You should have received a copy of the GNU General Public
+.\" License along with this manual; if not, see
+.\" <http://www.gnu.org/licenses/>.
+.\" %%%LICENSE_END
+.TH MTRACE 1 2014-09-01 "GNU" "Linux user manual"
+.SH NAME
+mtrace \- interpret the malloc trace log
+.SH SYNOPSIS
+.BR mtrace " [\fIoption\fR]... [\fIbinary\fR] \fImtracedata\fR"
+.SH DESCRIPTION
+.B mtrace
+is a Perl script used to interpret and provide human readable output
+of the trace log contained in the file
+.IR mtracedata ,
+whose contents were produced by
+.BR mtrace (3).
+If
+.I binary
+is provided, the output of
+.B mtrace
+also contains the source file name with line number information
+for problem locations
+(assuming that
+.I binary
+was compiled with debugging information).
+
+For more information about the
+.BR mtrace (3)
+function and
+.B mtrace
+script usage, see
+.BR mtrace (3).
+.SH OPTIONS
+.TP
+.BI \fB\-\-help
+Print help and exit.
+.TP
+.BI \fB\-\-version
+Print version information and exit.
+.SH BUGS
+For bug reporting instructions, please see:
+<http://www.gnu.org/software/libc/bugs.html>.
+.SH SEE ALSO
+.BR memusage (1),
+.BR mtrace (3)
+.SH COLOPHON
+This page is part of release 3.75 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.
--- /dev/null
+.\" Copyright (C) 2014 Michael Kerrisk <mtk.manpages@gmail.com>
+.\"
+.\" %%%LICENSE_START(VERBATIM)
+.\" Permission is granted to make and distribute verbatim copies of this
+.\" manual provided the copyright notice and this permission notice are
+.\" preserved on all copies.
+.\"
+.\" Permission is granted to copy and distribute modified versions of this
+.\" manual under the conditions for verbatim copying, provided that the
+.\" entire resulting derived work is distributed under the terms of a
+.\" permission notice identical to this one.
+.\"
+.\" Since the Linux kernel and libraries are constantly changing, this
+.\" manual page may be incorrect or out-of-date. The author(s) assume no
+.\" responsibility for errors or omissions, or for damages resulting from
+.\" the use of the information contained herein. The author(s) may not
+.\" have taken the same level of care in the production of this manual,
+.\" which is licensed free of charge, as they might when working
+.\" professionally.
+.\"
+.\" Formatted or processed versions of this manual, if unaccompanied by
+.\" the source, must acknowledge the copyright and authors of this work.
+.\" %%%LICENSE_END
+.\"
+.TH PLDD 1 2014-09-27 "GNU" "Linux User Manual"
+.SH NAME
+pldd \- display dynamic shared objects linked into a process
+.SH SYNOPSIS
+.nf
+.BI "pldd " "PID"
+.BR pldd " OPTION"
+.fi
+.SH DESCRIPTION
+The
+.B pldd
+command displays a list of the dynamic shared objects that are
+linked into the process with the specified process ID.
+The list includes the libraries that have been dynamically loaded using
+.BR dlopen (3).
+.SH OPTIONS
+.TP
+.BR \-? ", " \-\-help
+Display program help message.
+.TP
+.BR \-\-usage
+Display a short usage message.
+.TP
+.BR \-V ", " \-\-version
+Display the program version.
+.SH VERSIONS
+.B pldd
+is available since glibc 2.15.
+.SH CONFORMING TO
+The
+.B pldd
+command is not specified by POSIX.1.
+Some other systems
+.\" There are man pages on Solaris and HP-UX.
+have a similar command.
+.SH EXIT STATUS
+On success,
+.B pldd
+exits with the status 0.
+If the specified process does not exist,
+the user does not have permission to access
+its dynamic shared object list,
+or no command-line arguments are supplied,
+.B pldd
+exists with a status of 1.
+If given an invalid option, it exits with the status 64.
+.SH EXAMPLE
+.nf
+$ \fBecho $$\fP # Display PID of shell
+1143
+$ \fBpldd $$\fP # Display DSOs linked into the shell
+1143: /usr/bin/bash
+linux\-vdso.so.1
+/lib64/libtinfo.so.5
+/lib64/libdl.so.2
+/lib64/libc.so.6
+/lib64/ld\-linux\-x86\-64.so.2
+/lib64/libnss_files.so.2
+.fi
+.SH NOTES
+The command
+
+ lsof -p PID
+
+also shows output that includes the dynamic shared objects
+that are linked into a process.
+.SH SEE ALSO
+.BR ldd (1),
+.BR lsof (1),
+.BR dlopen (3),
+.BR ld.so (8)
+.SH COLOPHON
+This page is part of release 3.75 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.
--- /dev/null
+.\" Copyright (C) 2014 Michael Kerrisk <mtk.manpages@gmail.com>
+.\"
+.\" %%%LICENSE_START(VERBATIM)
+.\" Permission is granted to make and distribute verbatim copies of this
+.\" manual provided the copyright notice and this permission notice are
+.\" preserved on all copies.
+.\"
+.\" Permission is granted to copy and distribute modified versions of this
+.\" manual under the conditions for verbatim copying, provided that the
+.\" entire resulting derived work is distributed under the terms of a
+.\" permission notice identical to this one.
+.\"
+.\" Since the Linux kernel and libraries are constantly changing, this
+.\" manual page may be incorrect or out-of-date. The author(s) assume no
+.\" responsibility for errors or omissions, or for damages resulting from
+.\" the use of the information contained herein. The author(s) may not
+.\" have taken the same level of care in the production of this manual,
+.\" which is licensed free of charge, as they might when working
+.\" professionally.
+.\"
+.\" Formatted or processed versions of this manual, if unaccompanied by
+.\" the source, must acknowledge the copyright and authors of this work.
+.\" %%%LICENSE_END
+.\"
+.TH SPROF 1 2014-06-24 "Linux" "Linux User Manual"
+.SH NAME
+sprof \- read and display shared object profiling data
+.SH SYNOPSIS
+.nf
+.BR sprof " [\fIoption\fP]... \fIshared-object-path\fP \
+[\fIprofile-data-path\fP]"
+.fi
+.SH DESCRIPTION
+The
+.B sprof
+command displays a profiling summary for the
+shared object specified as its first command-line argument.
+The profiling summary is created using previously generated
+profiling data in the (optional) second command-line argument.
+If the profiling data pathname is omitted, then
+.B sprof
+will attempt to deduce it using the soname of the shared object,
+looking for a file with the name
+.IR <soname>.profile
+in the current directory.
+.SH OPTIONS
+The following command-line options specify the profile output
+to be produced:
+.TP
+.BR \-c ", " \-\-call\-pairs
+Print a list of pairs of call paths for the interfaces exported
+by the shared object,
+along with the number of times each path is used.
+.TP
+.BR \-p ", " \-\-flat\-profile
+Generate a flat profile of all of the functions in the monitored object,
+with counts and ticks.
+.TP
+.BR \-q ", " \-\-graph
+Generate a call graph.
+.PP
+If none of the above options is specified,
+then the default behavior is to display a flat profile and a call graph.
+.PP
+The following additional command-line options are available:
+.TP
+.BR \-? ", " \-\-help
+Display a summary of command-line options and arguments and exit.
+.TP
+.BR \-\-usage
+Display a short usage message and exit.
+.TP
+.BR \-V ", " \-\-version
+Display the program version and exit.
+.SH CONFORMING TO
+The
+.B sprof
+command is a GNU extension, not present in POSIX.1.
+.SH EXAMPLE
+The following example demonstrates the use of
+.BR sprof .
+The example consists of a main program that calls two functions
+in a shared library.
+First, the code of the main program:
+
+.in +4n
+.nf
+$ \fBcat prog.c\fP
+#include <stdlib.h>
+
+void x1(void);
+void x2(void);
+
+int
+main(int argc, char *argv[])
+{
+ x1();
+ x2();
+ exit(EXIT_SUCCESS);
+}
+.fi
+.in
+.PP
+The functions
+.IR x1()
+and
+.IR x2()
+are defined in the following source file that is used to
+construct the shared library:
+
+.in +4n
+.nf
+$ \fBcat libdemo.c\fP
+#include <unistd.h>
+
+void
+consumeCpu1(int lim)
+{
+ int j;
+
+ for (j = 0; j < lim; j++)
+ getppid();
+}
+
+void
+x1(void) {
+ int j;
+
+ for (j = 0; j < 100; j++)
+ consumeCpu1(200000);
+}
+
+void
+consumeCpu2(int lim)
+{
+ int j;
+
+ for (j = 0; j < lim; j++)
+ getppid();
+}
+
+void
+x2(void)
+{
+ int j;
+
+ for (j = 0; j < 1000; j++)
+ consumeCpu2(10000);
+}
+.fi
+.in
+.PP
+Now we construct the shared library with the real name
+.IR libdemo.so.1.0.1 ,
+and the soname
+.IR libdemo.so.1 :
+
+.in +4n
+.nf
+$ \fBcc \-g \-fPIC \-shared \-Wl,\-soname,libdemo.so.1 \e\fP
+ \fB\-o libdemo.so.1.0.1 libdemo.c\fP
+.fi
+.in
+.PP
+Then we construct symbolic links for the library soname and
+the library linker name:
+
+.in +4n
+.nf
+$ \fBln \-sf libdemo.so.1.0.1 libdemo.so.1\fP
+$ \fBln \-sf libdemo.so.1 libdemo.so\fP
+.fi
+.in
+.PP
+Next, we compile the main program, linking it against the shared library,
+and then list the dynamic dependencies of the program:
+
+.in +4n
+.nf
+$ \fBcc \-g \-o prog prog.c \-L. \-ldemo\fP
+$ \fBldd prog\fP
+ linux\-vdso.so.1 => (0x00007fff86d66000)
+ libdemo.so.1 => not found
+ libc.so.6 => /lib64/libc.so.6 (0x00007fd4dc138000)
+ /lib64/ld\-linux\-x86\-64.so.2 (0x00007fd4dc51f000)
+.fi
+.in
+.PP
+In order to get profiling information for the shared library,
+we define the environment variable
+.BR LD_PROFILE
+with the soname of the library:
+
+.in +4n
+.nf
+$ \fBexport LD_PROFILE=libdemo.so.1\fP
+.fi
+.in
+.PP
+We then define the environment variable
+.BR LD_PROFILE_OUTPUT
+with the pathname of the directory where profile output should be written,
+and create that directory if it does not exist already:
+
+.in +4n
+.nf
+$ \fBexport LD_PROFILE_OUTPUT=$(pwd)/prof_data\fP
+$ \fBmkdir \-p $LD_PROFILE_OUTPUT\fP
+.fi
+.in
+.PP
+.B LD_PROFILE
+causes profiling output to be
+.I appended
+to the output file if it already exists,
+so we ensure that there is no preexisting profiling data:
+
+.in +4n
+.nf
+$ \fBrm \-f $LD_PROFILE_OUTPUT/$LD_PROFILE.profile\fP
+.fi
+.in
+.PP
+We then run the program to produce the profiling output,
+which is written to a file in the directory specified in
+.BR LD_PROFILE_OUTPUT :
+
+.in +4n
+.nf
+$ \fBLD_LIBRARY_PATH=. ./prog\fP
+$ \fBls prof_data\fP
+libdemo.so.1.profile
+.fi
+.in
+.PP
+We then use the
+.BR "sprof \-p"
+option to generate a flat profile with counts and ticks:
+
+.in +4n
+.nf
+$ \fBsprof \-p libdemo.so.1 $LD_PROFILE_OUTPUT/libdemo.so.1.profile\fP
+Flat profile:
+
+Each sample counts as 0.01 seconds.
+ % cumulative self self total
+ time seconds seconds calls us/call us/call name
+ 60.00 0.06 0.06 100 600.00 consumeCpu1
+ 40.00 0.10 0.04 1000 40.00 consumeCpu2
+ 0.00 0.10 0.00 1 0.00 x1
+ 0.00 0.10 0.00 1 0.00 x2
+.fi
+.in
+.PP
+The
+.BR "sprof \-q"
+option generates a call graph:
+
+.in +4n
+.nf
+$ \fBsprof \-q libdemo.so.1 $LD_PROFILE_OUTPUT/libdemo.so.1.profile\fP
+
+index % time self children called name
+
+ 0.00 0.00 100/100 x1 [1]
+[0] 100.0 0.00 0.00 100 consumeCpu1 [0]
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+ 0.00 0.00 1/1 <UNKNOWN>
+[1] 0.0 0.00 0.00 1 x1 [1]
+ 0.00 0.00 100/100 consumeCpu1 [0]
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+ 0.00 0.00 1000/1000 x2 [3]
+[2] 0.0 0.00 0.00 1000 consumeCpu2 [2]
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+ 0.00 0.00 1/1 <UNKNOWN>
+[3] 0.0 0.00 0.00 1 x2 [3]
+ 0.00 0.00 1000/1000 consumeCpu2 [2]
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+.fi
+.in
+.PP
+Above and below, the "<UNKNOWN>" strings represent identifiers that
+are outside of the profiled object (in this example, these are instances of
+.IR main() ).
+.PP
+The
+.BR "sprof \-c"
+option generates a list of call pairs and the number of their occurrences:
+
+.in +4n
+.nf
+$ \fBsprof \-c libdemo.so.1 $LD_PROFILE_OUTPUT/libdemo.so.1.profile\fP
+<UNKNOWN> x1 1
+x1 consumeCpu1 100
+<UNKNOWN> x2 1
+x2 consumeCpu2 1000
+.fi
+.in
+.SH SEE ALSO
+.BR gprof (1),
+.BR ldd (1),
+.BR ld.so (8)
+.SH COLOPHON
+This page is part of release 3.75 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.
.BR times (2),
.BR wait3 (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR on_exit (3),
.BR termios (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR syscall (2),
.BR errno (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR socket (2),
.BR socket (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 2004-06-23 by Michael Kerrisk
.\" 2007-06-10, mtk, various parts rewritten, and added BUGS section.
.\"
-.TH ACCESS 2 2014-02-21 "Linux" "Linux Programmer's Manual"
+.TH ACCESS 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
access, faccessat \- check user's permissions for a file
.SH SYNOPSIS
Similar problems can occur to FUSE mounts.
.\"
.\"
-.SS faccessat ()
+.SS C library/kernel ABI differences
The raw
.BR faccessat ()
system call takes only the first three arguments.
If either of these flags is specified, then the wrapper function employs
.BR fstatat (2)
to determine access permissions.
+.SS Glibc notes
+On older kernels where
+.BR faccessat ()
+is unavailable (and when the
+.B AT_EACCESS
+and
+.B AT_SYMLINK_NOFOLLOW
+flags are not specified),
+the glibc wrapper function falls back to the use of
+.BR access ().
+When
+.I pathname
+is a relative pathname,
+glibc constructs a pathname based on the symbolic link in
+.IR /proc/self/fd
+that corresponds to the
+.IR dirfd
+argument.
.SH BUGS
In kernel 2.4 (and earlier) there is some strangeness in the handling of
.B X_OK
.BR path_resolution (7),
.BR symlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR acct (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR keyctl (2),
.BR request_key (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 1997-07-30 by Paul Slootman <paul@wurtel.demon.nl>
.\" Modified 2004-05-27 by Michael Kerrisk <mtk.manpages@gmail.com>
.\"
-.\" FIXME 2.6.26 added ADJ_TAI
+.\" FIXME Document ADJ_TAI (added in Linux 2.6.26)
.\" commit 153b5d054ac2d98ea0d86504884326b6777f683d
-.\" FIXME 2.6.26 added ADJ_MICOR and ADJ_NANO
+.\"
+.\" FIXME Document ADJ_MICRO and ADJ_NANO (added in Linux 2.6.26)
.\" commit eea83d896e318bda54be2d2770d2c5d6668d11db
.\" Author: Roman Zippel <zippel@linux-m68k.org>
-.\" FIXME 2.6.39 added ADJ_SETOFFSET
+.\"
+.\" FIXME Document ADJ_SETOFFSET (added in Linux 2.6.39)
.\" commit 094aa1881fdc1b8889b442eb3511b31f3ec2b762
.\" Author: Richard Cochran <richardcochran@gmail.com>
.\"
int modes; /* mode selector */
long offset; /* time offset (usec) */
long freq; /* frequency offset (scaled ppm) */
-.\" FIXME -- what is the scaling unit? 2^16 ?
+.\" FIXME What is the scaling unit of timex.freq? 2^16 ?
long maxerror; /* maximum error (usec) */
long esterror; /* estimated error (usec) */
int status; /* clock command/status */
.BR time (7),
.BR adjtimex (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sleep (3),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" mount -t hugetlbfs hugetlbfs /huge
.\" SHM_HUGETLB
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
AMD X86-64 Programmer's manual
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 1997-01-31 by Eric S. Raymond <esr@thyrsus.com>
.\" Modified 2004-06-17 by Michael Kerrisk <mtk.manpages@gmail.com>
.\"
-.TH BDFLUSH 2 2014-04-06 "Linux" "Linux Programmer's Manual"
+.TH BDFLUSH 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
bdflush \- start, flush, or tune buffer-dirty-flush daemon
.SH SYNOPSIS
.SH SEE ALSO
.BR fsync (2),
.BR sync (2),
-.BR sync (8)
+.BR sync (1)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" $Id: bind.2,v 1.3 1999/04/23 19:56:07 freitag Exp $
.\" Modified 2004-06-23 by Michael Kerrisk <mtk.manpages@gmail.com>
.\"
-.TH BIND 2 2014-05-10 "Linux" "Linux Programmer's Manual"
+.TH BIND 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
bind \- bind a name to a socket
.SH SYNOPSIS
.\" This may change in the future: see
.\" .I linux/unix/sock.c for details.
.TP
+.B EINVAL
+.I addrlen
+is wrong, or
+.I addr
+is not a valid address for this socket's domain.
+.TP
.B ENOTSOCK
.I sockfd
is a descriptor for a file, not a socket.
.I addr
points outside the user's accessible address space.
.TP
-.B EINVAL
-The
-.I addrlen
-is wrong, or the socket was not in the
-.B AF_UNIX
-family.
-.TP
.B ELOOP
Too many symbolic links were encountered in resolving
.IR addr .
.BR accept (2).
.SH BUGS
The transparent proxy options are not described.
-.\" FIXME What *are* transparent proxy options?
+.\" FIXME Document transparent proxy options
.SH EXAMPLE
An example of the use of
.BR bind ()
.BR socket (7),
.BR unix (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified Wed Jul 21 19:52:58 1993 by Rik Faith <faith@cs.unc.edu>
.\" Modified Sun Aug 21 17:40:38 1994 by Rik Faith <faith@cs.unc.edu>
.\"
-.TH BRK 2 2010-09-20 "Linux" "Linux Programmer's Manual"
+.TH BRK 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
brk, sbrk \- change data segment size
.SH SYNOPSIS
.I errno
is set to
.BR ENOMEM .
-(But see \fILinux Notes\fP below.)
On success,
.BR sbrk ()
.\" \fIptrdiff_t\fP (libc4, libc5, ulibc, glibc 2.0, 2.1),
.\" \fIintptr_t\fP (e.g., XPGv5, AIX, SunOS 5.8, 5.9, FreeBSD 4.7, NetBSD 1.6,
.\" Tru64 5.1, glibc2.2).
-.SS Linux notes
+.SS C library/kernel ABI differences
The return value described above for
.BR brk ()
is the behavior provided by the glibc wrapper function for the Linux
.BR end (3),
.BR malloc (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR BCACHE .
.SH CONFORMING TO
This Linux-specific system call is available only on MIPS-based systems.
-.\" FIXME This system call was only on MIPS back in 1.2 days, but
-.\" by now it is on a number of other architectures (but not i386).
+.\" FIXME The cacheflush() system call was only on MIPS back in 1.2 days,
+.\" but by now it is on a number of other architectures (but not i386).
.\" Investigate the details and update this page.
It should not be used in programs intended to be portable.
.\" Irix 6.5 appears to have a cacheflush() syscall -- mtk
arguments.
Therefore, the whole cache is always flushed.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.I pid
can also be: \-1, meaning perform the change on all threads except the
caller and
-.BR init (8);
+.BR init (1);
or a value less than \-1, in which case the change is applied
to all members of the process group whose ID is \-\fIpid\fP.
.BR gettid (2),
.BR capabilities (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getcwd (3),
.BR path_resolution (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" <michael@cantor.informatik.rwth-aachen.de>: NFS details
.\" Modified 2004-06-23 by Michael Kerrisk <mtk.manpages@gmail.com>
.\"
-.TH CHMOD 2 2014-02-21 "Linux" "Linux Programmer's Manual"
+.TH CHMOD 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
chmod, fchmod, fchmodat \- change permissions of a file
.SH SYNOPSIS
.BR fchmodat ():
POSIX.1-2008.
.SH NOTES
+.SS C library/kernel ABI differences
The GNU C library
.BR fchmodat ()
wrapper function implements the POSIX-specified
have a
.I flags
argument.
+.SS Glibc notes
+On older kernels where
+.BR fchmodat ()
+is unavailable, the glibc wrapper function falls back to the use of
+.BR chmod ().
+When
+.I pathname
+is a relative pathname,
+glibc constructs a pathname based on the symbolic link in
+.IR /proc/self/fd
+that corresponds to the
+.IR dirfd
+argument.
.SH SEE ALSO
.BR chown (2),
.BR execve (2),
.BR path_resolution (7),
.BR symlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" (bsdgroups versus sysvgroups, and the effect of the parent
.\" directory's set-group-ID permission bit).
.\"
-.TH CHOWN 2 2014-05-21 "Linux" "Linux Programmer's Manual"
+.TH CHOWN 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
chown, fchown, lchown, fchownat \- change ownership of a file
.SH SYNOPSIS
Filesystems that don't support these mount options follow the
.IR "\-o\ nogrpid"
rules.
+.SS Glibc notes
+On older kernels where
+.BR fchownat ()
+is unavailable, the glibc wrapper function falls back to the use of
+.BR chown ()
+and
+.BR lchown ().
+When
+.I pathname
+is a relative pathname,
+glibc constructs a pathname based on the symbolic link in
+.IR /proc/self/fd
+that corresponds to the
+.IR dirfd
+argument.
.SS NFS
The
.BR chown ()
.BR path_resolution (7),
.BR symlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR chdir (2),
.BR path_resolution (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sysconf (3),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR usleep (3),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2008-11-19, mtk, document CLONE_NEWIPC
.\" 2008-11-19, Jens Axboe, mtk, document CLONE_IO
.\"
-.\" FIXME Document CLONE_NEWUSER, which is new in 2.6.23
-.\" (also supported for unshare()?)
-.\"
-.TH CLONE 2 2014-05-28 "Linux" "Linux Programmer's Manual"
+.TH CLONE 2 2014-09-21 "Linux" "Linux Programmer's Manual"
.SH NAME
clone, __clone2 \- create a child process
.SH SYNOPSIS
(i.e., when the last process that is a member of the namespace terminates),
all IPC objects in the namespace are automatically destroyed.
-Use of this flag requires: a kernel configured with the
-.B CONFIG_SYSVIPC
-and
-.B CONFIG_IPC_NS
-options and that the process be privileged
-.RB ( CAP_SYS_ADMIN ).
+Only a privileged process
+.RB ( CAP_SYS_ADMIN )
+can employ
+.BR CLONE_NEWIPC .
This flag can't be specified in conjunction with
.BR CLONE_SYSVSEM .
+
+For further information on IPC namespaces, see
+.BR namespaces (7).
.TP
.BR CLONE_NEWNET " (since Linux 2.6.24)"
-.\" FIXME Check when the implementation was completed
(The implementation of this flag was completed only
by about kernel version 2.6.29.)
.B CLONE_NEWNET
is set, then create the process in a new network namespace.
If this flag is not set, then (as with
-.BR fork (2)),
+.BR fork (2))
the process is created in the same network namespace as
the calling process.
This flag is intended for the implementation of containers.
A physical network device can live in exactly one
network namespace.
A virtual network device ("veth") pair provides a pipe-like abstraction
-.\" FIXME Add pointer to veth(4) page when it is eventually completed
+.\" FIXME . Add pointer to veth(4) page when it is eventually completed
that can be used to create tunnels between network namespaces,
and can be used to create a bridge to a physical network device
in another namespace.
(i.e., when the last process in the namespace terminates),
its physical network devices are moved back to the
initial network namespace (not to the parent of the process).
+For further information on network namespaces, see
+.BR namespaces (7).
-Use of this flag requires: a kernel configured with the
-.B CONFIG_NET_NS
-option and that the process be privileged
-.RB ( CAP_SYS_ADMIN ).
+Only a privileged process
+.RB ( CAP_SYS_ADMIN )
+can employ
+.BR CLONE_NEWNET .
.TP
.BR CLONE_NEWNS " (since Linux 2.4.19)"
-Start the child in a new mount namespace.
-
-Every process lives in a mount namespace.
-The
-.I namespace
-of a process is the data (the set of mounts) describing the file hierarchy
-as seen by that process.
-After a
-.BR fork (2)
-or
-.BR clone ()
-where the
+If
+.B CLONE_NEWNS
+is set, the cloned child is started in a new mount namespace,
+initialized with a copy of the namespace of the parent.
+If
.B CLONE_NEWNS
-flag is not set, the child lives in the same mount
+is not set, the child lives in the same mount
namespace as the parent.
-The system calls
-.BR mount (2)
-and
-.BR umount (2)
-change the mount namespace of the calling process, and hence affect
-all processes that live in the same namespace, but do not affect
-processes in a different mount namespace.
-After a
-.BR clone ()
-where the
-.B CLONE_NEWNS
-flag is set, the cloned child is started in a new mount namespace,
-initialized with a copy of the namespace of the parent.
+For further information on mount namespaces, see
+.BR namespaces (7).
-Only a privileged process (one having the \fBCAP_SYS_ADMIN\fP capability)
-may specify the
-.B CLONE_NEWNS
-flag.
+Only a privileged process
+.RB ( CAP_SYS_ADMIN )
+can employ
+.BR CLONE_NEWNS .
It is not permitted to specify both
.B CLONE_NEWNS
and
.B CLONE_FS
+.\" See https://lwn.net/Articles/543273/
in the same
.BR clone ()
call.
.B CLONE_NEWPID
is set, then create the process in a new PID namespace.
If this flag is not set, then (as with
-.BR fork (2)),
+.BR fork (2))
the process is created in the same PID namespace as
the calling process.
This flag is intended for the implementation of containers.
-A PID namespace provides an isolated environment for PIDs:
-PIDs in a new namespace start at 1,
-somewhat like a standalone system, and calls to
-.BR fork (2),
-.BR vfork (2),
+For further information on PID namespaces, see
+.BR namespaces (7)
+and
+.BR pid_namespaces (7)
+
+Only a privileged process
+.RB ( CAP_SYS_ADMIN )
+can employ
+.BR CLONE_NEWPID .
+This flag can't be specified in conjunction with
+.BR CLONE_THREAD
or
+.BR CLONE_PARENT .
+.TP
+.BR CLONE_NEWUSER
+(This flag first became meaningful for
.BR clone ()
-will produce processes with PIDs that are unique within the namespace.
+in Linux 2.6.23,
+the current
+.BR clone()
+semantics were merged in Linux 3.5,
+and the final pieces to make the user namespaces completely usable were
+merged in Linux 3.8.)
-The first process created in a new namespace
-(i.e., the process created using the
-.BR CLONE_NEWPID
-flag) has the PID 1, and is the "init" process for the namespace.
-Children that are orphaned within the namespace will be reparented
-to this process rather than
-.BR init (8).
-Unlike the traditional
-.B init
-process, the "init" process of a PID namespace can terminate,
-and if it does, all of the processes in the namespace are terminated.
-
-PID namespaces form a hierarchy.
-When a new PID namespace is created,
-the processes in that namespace are visible
-in the PID namespace of the process that created the new namespace;
-analogously, if the parent PID namespace is itself
-the child of another PID namespace,
-then processes in the child and parent PID namespaces will both be
-visible in the grandparent PID namespace.
-Conversely, the processes in the "child" PID namespace do not see
-the processes in the parent namespace.
-The existence of a namespace hierarchy means that each process
-may now have multiple PIDs:
-one for each namespace in which it is visible;
-each of these PIDs is unique within the corresponding namespace.
-(A call to
-.BR getpid (2)
-always returns the PID associated with the namespace in which
-the process lives.)
-
-After creating the new namespace,
-it is useful for the child to change its root directory
-and mount a new procfs instance at
-.I /proc
-so that tools such as
-.BR ps (1)
-work correctly.
-.\" mount -t proc proc /proc
-(If
-.BR CLONE_NEWNS
-is also included in
-.IR flags ,
-then it isn't necessary to change the root directory:
-a new procfs instance can be mounted directly over
-.IR /proc .)
+If
+.B CLONE_NEWUSER
+is set, then create the process in a new user namespace.
+If this flag is not set, then (as with
+.BR fork (2))
+the process is created in the same user namespace as the calling process.
+
+For further information on user namespaces, see
+.BR namespaces (7)
+and
+.BR user_namespaces (7)
+
+Before Linux 3.8, use of
+.BR CLONE_NEWUSER
+required that the caller have three capabilities:
+.BR CAP_SYS_ADMIN ,
+.BR CAP_SETUID ,
+and
+.BR CAP_SETGID .
+.\" Before Linux 2.6.29, it appears that only CAP_SYS_ADMIN was needed
+Starting with Linux 3.8,
+no privileges are needed to create a user namespace.
-Use of this flag requires: a kernel configured with the
-.B CONFIG_PID_NS
-option and that the process be privileged
-.RB ( CAP_SYS_ADMIN ).
This flag can't be specified in conjunction with
-.BR CLONE_THREAD .
+.BR CLONE_THREAD
+or
+.BR CLONE_PARENT .
+For security reasons,
+.\" commit e66eded8309ebf679d3d3c1f5820d1f2ca332c71
+.\" https://lwn.net/Articles/543273/
+.\" The fix actually went into 3.9 and into 3.8.3. However, user namespaces
+.\" were, for practical purposes, unusable in earlier 3.8.x because of the
+.\" various filesystems that didn't support userns.
+.BR CLONE_NEWUSER
+cannot be specified in conjunction with
+.BR CLONE_FS .
+
+For further information on user namespaces, see
+.BR user_namespaces (7).
.TP
.BR CLONE_NEWUTS " (since Linux 2.6.19)"
If
whose identifiers are initialized by duplicating the identifiers
from the UTS namespace of the calling process.
If this flag is not set, then (as with
-.BR fork (2)),
+.BR fork (2))
the process is created in the same UTS namespace as
the calling process.
This flag is intended for the implementation of containers.
are visible to all other processes in the same namespace,
but are not visible to processes in other UTS namespaces.
-Use of this flag requires: a kernel configured with the
-.B CONFIG_UTS_NS
-option and that the process be privileged
-.RB ( CAP_SYS_ADMIN ).
+Only a privileged process
+.RB ( CAP_SYS_ADMIN )
+can employ
+.BR CLONE_NEWUTS .
+
+For further information on UTS namespaces, see
+.BR namespaces (7).
.TP
.BR CLONE_PARENT " (since Linux 2.3.12)"
If
If
.B CLONE_SYSVSEM
is set, then the child and the calling process share
-a single list of System\ V semaphore undo values (see
+a single list of System V semaphore adjustment
+.RI ( semadj )
+values (see
.BR semop (2)).
-If this flag is not set, then the child has a separate undo list,
-which is initially empty.
+In this case, the shared list accumulates
+.I semadj
+values across all processes sharing the list,
+and semaphore adjustments are performed only when the last process
+that is sharing the list terminates (or ceases sharing the list using
+.BR unshare (2)).
+If this flag is not set, then the child has a separate
+.I semadj
+list that is initially empty.
.TP
.BR CLONE_THREAD " (since Linux 2.4.0-test8)"
If
Memory writes or file mappings/unmappings performed by one of the
processes do not affect the other, as with
.BR fork (2).
-.SS The raw system call interface
+.SS C library/kernel ABI differences
The raw
.BR clone ()
system call corresponds more closely to
.\" (Since Linux 2.6.0-test6.)
.TP
.B EINVAL
+.\" commit e66eded8309ebf679d3d3c1f5820d1f2ca332c71
Both
.B CLONE_FS
and
were specified in
.IR flags .
.TP
+.BR EINVAL " (since Linux 3.9)"
+Both
+.B CLONE_NEWUSER
+and
+.B CLONE_FS
+were specified in
+.IR flags .
+.TP
.B EINVAL
Both
.B CLONE_NEWIPC
.IR flags .
.TP
.B EINVAL
-Both
+One (or both) of
.BR CLONE_NEWPID
-and
+or
+.BR CLONE_NEWUSER
+and one (or both) of
.BR CLONE_THREAD
+or
+.BR CLONE_PARENT
were specified in
.IR flags .
.TP
.B EPERM
.B CLONE_PID
was specified by a process other than process 0.
+.TP
+.B EPERM
+.BR CLONE_NEWUSER
+was specified in
+.IR flags ,
+but either the effective user ID or the effective group ID of the caller
+does not have a mapping in the parent namespace (see
+.BR user_namespaces (7)).
+.TP
+.BR EPERM " (since Linux 3.9)"
+.\" commit 3151527ee007b73a0ebd296010f1c0454a919c7d
+.B CLONE_NEWUSER was specified in
+.I flags
+and the caller is in a chroot environment
+.\" FIXME What is the rationale for this restriction?
+(i.e., the caller's root directory does not match the root directory
+of the mount namespace in which it resides).
+.TP
+.BR EUSERS " (since Linux 3.11)"
+.B CLONE_NEWUSER
+was specified in
+.IR flags ,
+and the call would cause the limit on the number of
+nested user namespaces to be exceeded.
+See
+.BR user_namespaces (7).
.SH VERSIONS
There is no entry for
.BR clone ()
.BR unshare (2),
.BR wait (2),
.BR capabilities (7),
+.BR namespaces (7),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR unlink (2),
.BR fclose (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 1998, 1999 by Andi Kleen
.\" Modified 2004-06-23 by Michael Kerrisk <mtk.manpages@gmail.com>
.\"
-.TH CONNECT 2 2014-05-10 "Linux" "Linux Programmer's Manual"
+.TH CONNECT 2 2014-09-06 "Linux" "Linux Programmer's Manual"
.SH NAME
connect \- initiate a connection on a socket
.SH SYNOPSIS
.B ENOTSOCK
The file descriptor is not associated with a socket.
.TP
+.B EPROTOTYPE
+The socket type does not support the requested communications protocol.
+This error can occur, for example,
+on an attempt to connect a UNIX domain datagram socket to a stream socket.
+.TP
.B ETIMEDOUT
Timeout while attempting connection.
The server may be too
also used by glibc.
See also
.BR accept (2).
+
+If
+.B connect()
+fails, consider the state of the socket as unspecified.
+Portable applications should close the socket and create a new one for
+reconnecting.
.SH EXAMPLE
An example of the use of
.BR connect ()
.BR socket (2),
.BR path_resolution (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR init_module (2),
.BR query_module (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR modprobe (8),
.BR rmmod (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" This manpage is Copyright (C) 1992 Drew Eckhardt;
.\" and Copyright (C) 1993 Michael Haardt, Ian Jackson.
.\" and Copyright (C) 2005, 2008 Michael Kerrisk <mtk.manpages@gmail.com>
+.\" and Copyright (C) 2014 Michael Kerrisk <mtk.manpages@gmail.com>
.\"
.\" %%%LICENSE_START(VERBATIM)
.\" Permission is granted to make and distribute verbatim copies of this
.\" details for dup2().
.\" 2008-10-09, mtk: add description of dup3()
.\"
-.TH DUP 2 2012-02-14 "Linux" "Linux Programmer's Manual"
+.TH DUP 2 2014-07-08 "Linux" "Linux Programmer's Manual"
.SH NAME
dup, dup2, dup3 \- duplicate a file descriptor
.SH SYNOPSIS
.BI "int dup3(int " oldfd ", int " newfd ", int " flags );
.fi
.SH DESCRIPTION
-These system calls create a copy of the file descriptor
-.IR oldfd .
-
+The
.BR dup ()
-uses the lowest-numbered unused descriptor for the new descriptor.
+system call creates a copy of the file descriptor
+.IR oldfd ,
+using the lowest-numbered unused descriptor for the new descriptor.
+After a successful return,
+the old and new file descriptors may be used interchangeably.
+They refer to the same open file description (see
+.BR open (2))
+and thus share file offset and file status flags;
+for example, if the file offset is modified by using
+.BR lseek (2)
+on one of the descriptors, the offset is also changed for the other.
+
+The two descriptors do not share file descriptor flags
+(the close-on-exec flag).
+The close-on-exec flag
+.RB ( FD_CLOEXEC ;
+see
+.BR fcntl (2))
+for the duplicate descriptor is off.
+.\"
+.SS dup2()
+The
.BR dup2 ()
-.RI "makes " newfd " be the copy of " oldfd ", closing " newfd
-first if necessary, but note the following:
+system call performs the same task as
+.BR dup (),
+but instead of using the lowest-numbered unused file descriptor,
+it uses the descriptor number specified in
+.IR newfd .
+If the descriptor
+.IR newfd
+was previously open, it is silently closed before being reused.
+
+The steps of closing and reusing the file descriptor
+.IR newfd
+are performed
+.IR atomically .
+This is important, because trying to implement equivalent functionality using
+.BR close (2)
+and
+.BR dup ()
+would be
+subject to race conditions, whereby
+.I newfd
+might be reused between the two steps.
+Such reuse could happen because the main program is interrupted
+by a signal handler that allocates a file descriptor,
+or because a parallel thread allocates a file descriptor.
+
+Note the following points:
.IP * 3
If
.I oldfd
.BR dup2 ()
does nothing, and returns
.IR newfd .
-.PP
-After a successful return from one of these system calls,
-the old and new file descriptors may be used interchangeably.
-They refer to the same open file description (see
-.BR open (2))
-and thus share file offset and file status flags;
-for example, if the file offset is modified by using
-.BR lseek (2)
-on one of the descriptors, the offset is also changed for the other.
-
-The two descriptors do not share file descriptor flags
-(the close-on-exec flag).
-The close-on-exec flag
-.RB ( FD_CLOEXEC ;
-see
-.BR fcntl (2))
-for the duplicate descriptor is off.
-
+.\"
+.SS dup3()
.BR dup3 ()
is the same as
.BR dup2 (),
was open, any errors that would have been reported at
.BR close (2)
time are lost.
-A careful programmer will not use
-.BR dup2 ()
-or
-.BR dup3 ()
-without closing
+If this is of concern,
+then\(emunless the program is single-threaded and does not allocate
+file descriptors in signal handlers\(emthe correct approach is
+.I not
+to close
.I newfd
-first.
+before calling
+.BR dup2 (),
+because of the race condition described above.
+Instead, code something like the following could be used:
+
+.nf
+ /* Obtain a duplicate of 'newfd' that can subsequently
+ be used to check for close() errors; an EBADF error
+ means that 'newfd' was not open. */
+
+ tmpfd = dup(newfd);
+ if (tmpfd == \-1 && errno != EBADF) {
+ /* Handle unexpected dup() error */
+ }
+
+ /* Atomically duplicate 'oldfd' on 'newfd' */
+
+ if (dup2(oldfd, newfd) == \-1) {
+ /* Handle dup2() error */
+ }
+
+ /* Now check for close() errors on the file originally
+ referred to by 'newfd' */
+
+ if (tmpfd != \-1) {
+ if (close(tmpfd) == \-1) {
+ /* Handle errors from close */
+ }
+ }
+.fi
.SH SEE ALSO
.BR close (2),
.BR fcntl (2),
.BR open (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR epoll_wait (2),
.BR epoll (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
-.TH EPOLL_CTL 2 2012-04-15 "Linux" "Linux Programmer's Manual"
+.TH EPOLL_CTL 2 2014-07-08 "Linux" "Linux Programmer's Manual"
.SH NAME
epoll_ctl \- control interface for an epoll descriptor
.SH SYNOPSIS
with
.B EPOLL_CTL_MOD
to rearm the file descriptor with a new event mask.
+.TP
+.BR EPOLLWAKEUP " (since Linux 3.5)"
+.\" commit 4d7e30d98939a0340022ccd49325a3d70f7e0238
+If
+.B EPOLLONESHOT
+and
+.B EPOLLET
+are clear and the process has the
+.B CAP_BLOCK_SUSPEND
+capability,
+ensure that the system does not enter "suspend" or
+"hibernate" while this event is pending or being processed.
+The event is considered as being "processed" from the time
+when it is returned by a call to
+.BR epoll_wait (2)
+until the next call to
+.BR epoll_wait (2)
+on the same
+.BR epoll (7)
+file descriptor,
+the closure of that file descriptor,
+the removal of the event file descriptor with
+.BR EPOLL_CTL_DEL ,
+or the clearing of
+.B EPOLLWAKEUP
+for the event file descriptor with
+.BR EPOLL_CTL_MOD .
+See also BUGS.
.SH RETURN VALUE
When successful,
.BR epoll_ctl ()
Applications that need to be portable to kernels before 2.6.9
should specify a non-null pointer in
.IR event .
+
+If
+.B EPOLLWAKEUP
+is specified in
+.IR flags ,
+but the caller does not have the
+.BR CAP_BLOCK_SUSPEND
+capability, then the
+.B EPOLLWAKEUP
+flag is
+.IR "silently ignored" .
+This unfortunate behavior is necessary because no validity
+checks were performed on the
+.IR flags
+argument in the original implementation, and the addition of the
+.B EPOLLWAKEUP
+with a check that caused the call to fail if the caller did not have the
+.B CAP_BLOCK_SUSPEND
+capability caused a breakage in at least one existing user-space
+application that happened to randomly (and uselessly) specify this bit.
+.\" commit a8159414d7e3af7233e7a5a82d1c5d85379bd75c (behavior change)
+.\" https://lwn.net/Articles/520198/
+A robust application should therefore double check that it has the
+.B CAP_BLOCK_SUSPEND
+capability if attempting to use the
+.B EPOLLWAKEUP
+flag.
.SH SEE ALSO
.BR epoll_create (2),
.BR epoll_wait (2),
.BR poll (2),
.BR epoll (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\" 2007-04-30: mtk, Added description of epoll_pwait()
.\"
-.TH EPOLL_WAIT 2 2014-01-31 "Linux" "Linux Programmer's Manual"
+.TH EPOLL_WAIT 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
epoll_wait, epoll_pwait \- wait for an I/O event on an epoll file descriptor
.SH SYNOPSIS
.I HZ
value is 1000,
this means that timeouts greater than 35.79 minutes are treated as infinity.
+.SS C library/kernel ABI differences
+The raw
+.BR epoll_pwait ()
+system call has a sixth argument,
+.IR "size_t sigsetsize" ,
+which specifies the size in bytes of the
+.IR sigmask
+argument.
+The glibc
+.BR epoll_pwait ()
+wrapper function specifies this argument as a fixed value
+(equal to
+.IR sizeof(sigset_t) ).
.SH SEE ALSO
.BR epoll_create (2),
.BR epoll_ctl (2),
.BR epoll (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\" 2008-10-10, mtk: describe eventfd2(), and EFD_NONBLOCK and EFD_CLOEXEC
.\"
-.TH EVENTFD 2 2010-08-30 Linux "Linux Programmer's Manual"
+.TH EVENTFD 2 2014-07-08 Linux "Linux Programmer's Manual"
.SH NAME
eventfd \- create a file descriptor for event notification
.SH SYNOPSIS
The following values may be bitwise ORed in
.IR flags
-to change the behaviour of
+to change the behavior of
.BR eventfd ():
.TP
.BR EFD_CLOEXEC " (since Linux 2.6.27)"
.BR poll (2),
or
.BR epoll (7).)
-.SS Underlying Linux system calls
+.SS C library/kernel ABI differences
There are two underlying Linux system calls:
.BR eventfd ()
and the more recent
.BR epoll (7),
.BR sem_overview (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2007-09-14 Ollie Wild <aaw@google.com>, mtk
.\" Add text describing limits on command-line arguments + environment
.\"
-.TH EXECVE 2 2014-05-10 "Linux" "Linux Programmer's Manual"
+.TH EXECVE 2 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
execve \- execute program
.SH SYNOPSIS
shared libraries.
This interpreter is typically
.I /lib/ld-linux.so.2
-for binaries linked with glibc 2.
-(For binaries linked with the old Linux libc5, the interpreter was typically
-.IR /lib/ld-linux.so.1 .)
+for binaries linked with glibc.
All process attributes are preserved during an
.BR execve (),
The filesystem is mounted
.IR noexec .
.TP
+.BR EAGAIN " (since Linux 3.1)"
+.\" commit 72fa59970f8698023045ab0713d66f3f4f96945c
+Having changed its real UID using one of the
+.BR set*uid ()
+calls, the caller was\(emand is now still\(emabove its
+.BR RLIMIT_NPROC
+resource limit (see
+.BR setrlimit (2)).
+For a more detailed explanation of this error, see NOTES.
+.TP
.B EFAULT
.I filename
or one of the pointers in the vectors
Linux ignores the set-user-ID and set-group-ID bits on scripts.
.\"
+.\" .SH BUGS
+.\" Some Linux versions have failed to check permissions on ELF
+.\" interpreters. This is a security hole, because it allows users to
+.\" open any file, such as a rewinding tape device, for reading. Some
+.\" Linux versions have also had other security holes in
+.\" .BR execve ()
+.\" that could be exploited for denial of service by a suitably crafted
+.\" ELF binary. There are no known problems with 2.0.34 or 2.2.15.
+.SS execve() and EAGAIN
+A more detailed explanation of the
+.BR EAGAIN
+error that can occur (since Linux 3.1) when calling
+.BR execve ()
+is as follows.
+
+The
+.BR EAGAIN
+error can occur when a
+.I preceding
+call to
+.BR setuid (2),
+.BR setreuid (2),
+or
+.BR setresuid (2)
+caused the real user ID of the process to change,
+and that change caused the process to exceed its
+.BR RLIMIT_NPROC
+resource limit (i.e., the number of processes belonging
+to the new real UID exceeds the resource limit).
+From Linux 2.6.0 to 3.0, this caused the
+.BR set*uid ()
+call to fail.
+(Prior to 2.6,
+.\" commit 909cc4ae86f3380152a18e2a3c44523893ee11c4
+the resource limit was not imposed on processes that
+changed their user IDs.)
+
+Since Linux 3.1, the scenario just described no longer causes the
+.BR set*uid ()
+call to fail,
+because it too often led to security holes where buggy applications
+didn't check the return status and assumed
+that\(emif the caller had root privileges\(emthe call would always succeed.
+Instead, the
+.BR set*uid ()
+calls now successfully change the real UID,
+but the kernel sets an internal flag, named
+.BR PF_NPROC_EXCEEDED ,
+to note that the
+.BR RLIMIT_NPROC
+resource limit has been exceeded.
+If the
+.BR PF_NPROC_EXCEEDED
+flag is set and the resource limit is still
+exceeded at the time of a subsequent
+.BR execve ()
+call, that call fails with the error
+.BR EAGAIN .
+This kernel logic ensures that the
+.BR RLIMIT_NPROC
+resource limit is still enforced for the
+common privileged daemon workflow\(emnamely,
+.BR fork (2)
++
+.BR set*uid ()
++
+.BR execve ().
+
+If the resource limit was not still exceeded at the time of the
+.BR execve ()
+call
+(because other processes belonging to this real UID terminated between the
+.BR set*uid()
+call and the
+.BR execve ()
+call), then the
+.BR execve ()
+call succeeds and the kernel clears the
+.BR PF_NPROC_EXCEEDED
+process flag.
+The flag is also cleared if a subsequent call to
+.BR fork (2)
+by this process succeeds.
.SS Historical
With UNIX\ V6, the argument list of an
.BR exec ()
.in +4n
.nf
-.RB "$" " cat > script.sh"
-.B #! ./myecho script-arg
+.RB "$" " cat > script"
+.B #!./myecho script-arg
.B ^D
-.RB "$" " chmod +x script.sh"
+.RB "$" " chmod +x script"
.fi
.in
.in +4n
.nf
-.RB "$" " ./execve ./script.sh"
+.RB "$" " ./execve ./script"
argv[0]: ./myecho
argv[1]: script-arg
-argv[2]: ./script.sh
+argv[2]: ./script
argv[3]: hello
argv[4]: world
.fi
.BR path_resolution (7),
.BR ld.so (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR exit (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2011-09-19: Added FALLOC_FL_PUNCH_HOLE
.\" 2011-09-19: Substantial restructuring of the page
.\"
-.TH FALLOCATE 2 2014-05-08 "Linux" "Linux Programmer's Manual"
+.TH FALLOCATE 2 2014-07-08 "Linux" "Linux Programmer's Manual"
.SH NAME
fallocate \- manipulate file space
.SH SYNOPSIS
but the file size will not be changed even if
.IR offset + len
is greater than the file size.
-This behaviour is the same as when preallocating space with
+This behavior is the same as when preallocating space with
.B FALLOC_FL_KEEP_SIZE
specified.
.I offset
was less than 0, or
.I len
-.\" FIXME (raise a kernel bug) Probably the len==0 case should be
+.\" FIXME . (raise a kernel bug) Probably the len==0 case should be
.\" a no-op, rather than an error. That would be consistent with
.\" similar APIs for the len==0 case.
.\" See "Re: [PATCH] fallocate.2: add FALLOC_FL_PUNCH_HOLE flag definition"
.BR posix_fadvise (3),
.BR posix_fallocate (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Formatted or processed versions of this manual, if unaccompanied by
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
-.TH FANOTIFY_INIT 2 2014-05-18 "Linux" "Linux Programmer's Manual"
+.TH FANOTIFY_INIT 2 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
fanotify_init \- create and initialize fanotify group
.SH SYNOPSIS
.SH "CONFORMING TO"
This system call is Linux-specific.
.SH BUGS
-As of Linux 3.15,
+As of Linux 3.17,
the following bug exists:
.IP * 3
-.\" FIXME: Patch accepted to mm tree.
+.\" FIXME . Patch proposed: https://lkml.org/lkml/2014/9/24/967
+The
+.B O_CLOEXEC
+is ignored when passed in
+.IR event_f_flags .
+.PP
+The following bug was present in Linux kernels before version 3.14:
+.IP * 3
+.\" Fixed by commit 48149e9d3a7e924010a0daab30a6197b7d7b6580
The
.I event_f_flags
argument is not checked for invalid flags.
.BR fanotify_mark (2),
.BR fanotify (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Formatted or processed versions of this manual, if unaccompanied by
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
-.TH FANOTIFY_MARK 2 2014-04-24 "Linux" "Linux Programmer's Manual"
+.TH FANOTIFY_MARK 2 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
fanotify_mark \- add, remove, or modify an fanotify mark on a filesystem
object
.TP
.B FAN_ONDIR
Create events for directories\(emfor example, when
-.BR opendir (2),
-.BR readdir (2)
+.BR opendir (3),
+.BR readdir (3)
(but see BUGS), and
-.BR closedir (2)
+.BR closedir (3)
are called.
Without this flag, only events for files are created.
.TP
is relative, and
.I dirfd
has the value
-.BR AT_FDCWD,
+.BR AT_FDCWD ,
then the filesystem object to be marked is determined by interpreting
.I pathname
relative the current working directory.
.SH CONFORMING TO
This system call is Linux-specific.
.SH BUGS
-As of Linux 3.15,
-the following bugs exist:
+The following bugs were present in Linux kernels before version 3.16:
.IP * 3
-.\" FIXME: Patch is in next-20140424.
+.\" Fixed by commit 0a8dd2db579f7a0ac7033d6b857c3d5dbaa77563
If
.I flags
contains
.I pathname
must specify a valid filesystem object, even though this object is not used.
.IP *
-.\" FIXME: Patch is in next-20140424.
+.\" Fixed by commit d4c7cf6cffb1bc711a833b5e304ba5bcfe76398b
.BR readdir (2)
does not generate a
.B FAN_ACCESS
event.
.IP *
-.\" FIXME: Patch proposed.
+.\" Fixed by commit cc299a98eb13a9853675a9cbb90b30b4011e1406
If
.BR fanotify_mark (2)
is called with
-.B FAN_MARK_FLUSH,
+.BR FAN_MARK_FLUSH ,
.I flags
is not checked for invalid values.
.SH SEE ALSO
.BR fanotify_init (2),
.BR fanotify (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
'\" t
.\" This manpage is Copyright (C) 1992 Drew Eckhardt;
-.\" and Copyright (C) 1993 Michael Haardt, Ian Jackson;
-.\" and Copyright (C) 1998 Jamie Lokier;
-.\" and Copyright (C) 2002-2010 Michael Kerrisk.
+.\" and Copyright (C) 1993 Michael Haardt, Ian Jackson;
+.\" and Copyright (C) 1998 Jamie Lokier;
+.\" and Copyright (C) 2002-2010, 2014 Michael Kerrisk;
+.\" and Copyright (C) 2014 Jeff Layton
.\"
.\" %%%LICENSE_START(VERBATIM)
.\" Permission is granted to make and distribute verbatim copies of this
.\" 2010-06-17, Michael Kerrisk
.\" Document F_SETPIPE_SZ and F_GETPIPE_SZ.
.\"
-.TH FCNTL 2 2014-05-21 "Linux" "Linux Programmer's Manual"
+.TH FCNTL 2 2014-09-06 "Linux" "Linux Programmer's Manual"
.SH NAME
fcntl \- manipulate file descriptor
.SH SYNOPSIS
or
.I void
is specified if the argument is not required.
+
+Certain of the operations below are supported only since a particular
+Linux kernel version.
+The preferred method of checking whether the host kernel supports
+a particular operation is to invoke
+.BR fcntl ()
+with the desired
+.IR cmd
+value and then test whether the call failed with
+.BR EINVAL ,
+indicating that the kernel does not recognize this value.
.SS Duplicating a file descriptor
.TP
.BR F_DUPFD " (\fIint\fP)"
and
.BR O_SYNC
flags; see BUGS, below.
-.SS Advisory locking
+.SS Advisory record locking
+Linux implements traditional ("process-associated") UNIX record locks,
+as standardized by POSIX.
+For a Linux-specific alternative with better semantics,
+see the discussion of open file description locks below.
+
.BR F_SETLK ,
.BR F_SETLKW ,
and
.BR F_GETLK
are used to acquire, release, and test for the existence of record
-locks (also known as file-segment or file-region locks).
+locks (also known as byte-range, file-segment, or file-region locks).
The third argument,
.IR lock ,
is a pointer to a structure that has at least the following fields
off_t l_start; /* Starting offset for lock */
off_t l_len; /* Number of bytes to lock */
pid_t l_pid; /* PID of process blocking our lock
- (F_GETLK only) */
+ (set by F_GETLK and F_OFD_GETLK) */
...
};
.fi
.B EACCES
or
.BR EAGAIN .
+(The error returned in this case differs across implementations,
+so POSIX requires a portable application to check for both errors.)
.TP
.BR F_SETLKW " (\fIstruct flock *\fP)"
As for
field of
.I lock
and leaves the other fields of the structure unchanged.
+
If one or more incompatible locks would prevent
this lock being placed, then
.BR fcntl ()
-returns details about one of these locks in the
+returns details about one of those locks in the
.IR l_type ", " l_whence ", " l_start ", and " l_len
fields of
-.I lock
-and sets
+.IR lock .
+If the conflicting lock is a traditional (process-associated) record lock,
+then the
.I l_pid
-to be the PID of the process holding that lock.
-Note that the information returned by
-.BR F_GETLK
+field is set to the PID of the process holding that lock.
+If the conflicting lock is an open file description lock, then
+.I l_pid
+is set to \-1.
+Note that the returned information
may already be out of date by the time the caller inspects it.
.P
In order to place a read lock,
.I fd
must be open for writing.
To place both types of lock, open a file read-write.
-.P
+
+When placing locks with
+.BR F_SETLKW ,
+the kernel detects
+.IR deadlocks ,
+whereby two or more processes have their
+lock requests mutually blocked by locks held by the other processes.
+For example, suppose process A holds a write lock on byte 100 of a file,
+and process B holds a write lock on byte 200.
+If each process then attempts to lock the byte already
+locked by the other process using
+.BR F_SETLKW ,
+then, without deadlock detection,
+both processes would remain blocked indefinitely.
+When the kernel detects such deadlocks,
+it causes one of the blocking lock requests to immediately fail with the error
+.BR EDEADLK ;
+an application that encounters such an error should release
+some of its locks to allow other applications to proceed before
+attempting regain the locks that it requires.
+Circular deadlocks involving more than two processes are also detected.
+Note, however, that there are limitations to the kernel's
+deadlock-detection algorithm; see BUGS.
+
As well as being removed by an explicit
.BR F_UNLCK ,
-record locks are automatically released when the process
-terminates or if it closes
-.I any
-file descriptor referring to a file on which locks are held.
-.\" (Additional file descriptors referring to the same file
-.\" may have been obtained by calls to
-.\" .BR open "(2), " dup "(2), " dup2 "(2), or " fcntl ().)
-This is bad: it means that a process can lose the locks on
-a file like
-.I /etc/passwd
-or
-.I /etc/mtab
-when for some reason a library function decides to open, read
-and close it.
+record locks are automatically released when the process terminates.
.P
Record locks are not inherited by a child created via
.BR fork (2),
and
.BR write (2)
instead.
+
+The record locks described above are associated with the process
+(unlike the open file description locks described below).
+This has some unfortunate consequences:
+.IP * 3
+If a process closes
+.I any
+file descriptor referring to a file,
+then all of the process's locks on that file are released,
+regardless of the file descriptor(s) on which the locks were obtained.
+.\" (Additional file descriptors referring to the same file
+.\" may have been obtained by calls to
+.\" .BR open "(2), " dup "(2), " dup2 "(2), or " fcntl ().)
+This is bad: it means that a process can lose its locks on
+a file such as
+.I /etc/passwd
+or
+.I /etc/mtab
+when for some reason a library function decides to open, read,
+and close the same file.
+.IP *
+The threads in a process share locks.
+In other words,
+a multithreaded program can't use record locking to ensure
+that threads don't simultaneously access the same region of a file.
+.PP
+Open file description locks solve both of these problems.
+.SS Open file description locks (non-POSIX)
+Open file description locks are advisory byte-range locks whose operation is
+in most respects identical to the traditional record locks described above.
+This lock type is Linux-specific,
+and available since Linux 3.15.
+For an explanation of open file descriptions, see
+.BR open (2).
+
+The principal difference between the two lock types
+is that whereas traditional record locks
+are associated with a process,
+open file description locks are associated with the
+open file description on which they are acquired,
+much like locks acquired with
+.BR flock (2).
+Consequently (and unlike traditional advisory record locks),
+open file description locks are inherited across
+.BR fork (2)
+(and
+.BR clone (2)
+with
+.BR CLONE_FILES ),
+and are only automatically released on the last close
+of the open file description,
+instead of being released on any close of the file.
+.PP
+Open file description locks always conflict with traditional record locks,
+even when they are acquired by the same process on the same file descriptor.
+
+Open file description locks placed via the same open file description
+(i.e., via the same file descriptor,
+or via a duplicate of the file descriptor created by
+.BR fork (2),
+.BR dup (2),
+.BR fcntl (2)
+.BR F_DUPFD ,
+and so on) are always compatible:
+if a new lock is placed on an already locked region,
+then the existing lock is converted to the new lock type.
+(Such conversions may result in splitting, shrinking, or coalescing with
+an existing lock as discussed above.)
+
+On the other hand, open file description locks may conflict with
+each other when they are acquired via different open file descriptions.
+Thus, the threads in a multithreaded program can use
+open file description locks to synchronize access to a file region
+by having each thread perform its own
+.BR open (2)
+on the file and applying locks via the resulting file descriptor.
+.PP
+As with traditional advisory locks, the third argument to
+.BR fcntl (),
+.IR lock ,
+is a pointer to an
+.IR flock
+structure.
+By contrast with traditional record locks, the
+.I l_pid
+field of that structure must be set to zero
+when using the commands described below.
+
+The commands for working with open file description locks are analogous
+to those used with traditional locks:
+.TP
+.BR F_OFD_SETLK " (\fIstruct flock *\fP)"
+Acquire an open file description lock (when
+.I l_type
+is
+.B F_RDLCK
+or
+.BR F_WRLCK )
+or release an open file description lock (when
+.I l_type
+is
+.BR F_UNLCK )
+on the bytes specified by the
+.IR l_whence ", " l_start ", and " l_len
+fields of
+.IR lock .
+If a conflicting lock is held by another process,
+this call returns \-1 and sets
+.I errno
+to
+.BR EAGAIN .
+.TP
+.BR F_OFD_SETLKW " (\fIstruct flock *\fP)"
+As for
+.BR F_OFD_SETLK ,
+but if a conflicting lock is held on the file, then wait for that lock to be
+released.
+If a signal is caught while waiting, then the call is interrupted
+and (after the signal handler has returned) returns immediately
+(with return value \-1 and
+.I errno
+set to
+.BR EINTR ;
+see
+.BR signal (7)).
+.TP
+.BR F_OFD_GETLK " (\fIstruct flock *\fP)"
+On input to this call,
+.I lock
+describes an open file description lock we would like to place on the file.
+If the lock could be placed,
+.BR fcntl ()
+does not actually place it, but returns
+.B F_UNLCK
+in the
+.I l_type
+field of
+.I lock
+and leaves the other fields of the structure unchanged.
+If one or more incompatible locks would prevent this lock being placed,
+then details about one of these locks are returned via
+.IR lock ,
+as described above for
+.BR F_GETLK .
+.PP
+In the current implementation,
+.\" commit 57b65325fe34ec4c917bc4e555144b4a94d9e1f7
+no deadlock detection is performed for open file description locks.
+(This contrasts with process-associated record locks,
+for which the kernel does perform deadlock detection.)
+.\"
.SS Mandatory locking
-(Non-POSIX.)
-The above record locks may be either advisory or mandatory,
-and are advisory by default.
+.IR Warning :
+the Linux implementation of mandatory locking is unreliable.
+See BUGS below.
+By default, both traditional (process-associated) and open file description
+record locks are advisory.
Advisory locks are not enforced and are useful only between
cooperating processes.
+Both lock types can also be mandatory.
Mandatory locks are enforced for all processes.
If a process tries to perform an incompatible access (e.g.,
.BR read (2)
If the
.B O_NONBLOCK
flag is not enabled, then
-system call is blocked until the lock is removed
+the system call is blocked until the lock is removed
or converted to a mode that is compatible with the access.
If the
.B O_NONBLOCK
and
.BR chmod (2)).
-The Linux implementation of mandatory locking is unreliable.
-See BUGS below.
+Mandatory locking is not specified by POSIX.
+Some other systems also support mandatory locking,
+although the details of how to enable it vary across systems.
.SS Managing signals
.BR F_GETOWN ,
.BR F_SETOWN ,
.PD 0
.TP 12
.B DN_ACCESS
-A file was accessed (read, pread, readv)
+A file was accessed
+.RB ( read (2),
+.BR pread (2),
+.BR readv (2),
+and similar)
.TP
.B DN_MODIFY
-A file was modified (write, pwrite, writev, truncate, ftruncate).
+A file was modified
+.RB ( write (2),
+.BR pwrite (2),
+.BR writev (2),
+.BR truncate (2),
+.BR ftruncate (2),
+and similar).
.TP
.B DN_CREATE
-A file was created (open, creat, mknod, mkdir, link, symlink, rename).
+A file was created
+.RB ( open (2),
+.BR creat (2),
+.BR mknod (2),
+.BR mkdir (2),
+.BR link (2),
+.BR symlink (2),
+.BR rename (2)
+into this directory).
.TP
.B DN_DELETE
-A file was unlinked (unlink, rename to another directory, rmdir).
+A file was unlinked
+.RB ( unlink (2),
+.BR rename (2)
+to another directory,
+.BR rmdir (2)).
.TP
.B DN_RENAME
-A file was renamed within this directory (rename).
+A file was renamed within this directory
+.RB ( rename (2)).
.TP
.B DN_ATTRIB
-The attributes of a file were changed (chown, chmod, utime[s]).
+The attributes of a file were changed
+.RB ( chown (2),
+.BR chmod (2),
+.BR utime (2),
+.BR utimensat (2),
+and similar).
.PD
.RE
.IP
.B F_SETSIG
command to
.BR fcntl ().
+(Note that
+.B SIGIO
+is one of the nonqueuing standard signals;
+switching to the use of a real-time signal means that
+multiple notifications can be queued to the process.)
In the latter case, the signal handler receives a
.I siginfo_t
structure as its second argument (if the handler was
the kernel may use a capacity larger than
.IR arg ,
if that is convenient for the implementation.
-The
-.B F_GETPIPE_SZ
-operation returns the actual size used.
+The actual capacity that is set is returned as the function result.
Attempting to set the pipe capacity smaller than the amount
of buffer space currently used to store data produces the error
.BR EBUSY .
.B SIGIO
behavior.
.TP
-.B F_GETPIPE_SZ
+.BR F_GETPIPE_SZ ", " F_SETPIPE_SZ
The pipe capacity.
.TP
All other commands
NFS), but can sometimes happen locally.
.TP
.B EINVAL
+The value specified in
+.I cmd
+is not recognized by this kernel.
+.TP
+.B EINVAL
For
.BR F_DUPFD ,
.I arg
.I arg
is not an allowable signal number.
.TP
+.B EINVAL
+.I cmd
+is
+.BR F_OFD_SETLK ,
+.BR F_OFD_SETLKW ,
+or
+.BR F_OFD_GETLK ,
+and
+.I l_pid
+was not specified as zero.
+.TP
.B EMFILE
For
.BR F_DUPFD ,
Too many segment locks open, lock table is full, or a remote locking
protocol failed (e.g., locking over NFS).
.TP
+.B ENOTDIR
+.B F_NOTIFY
+was specified in
+.IR cmd ,
+but
+.IR fd
+does not refer to a directory.
+.TP
.B EPERM
Attempted to clear the
.B O_APPEND
and
.B F_SETOWN
are specified in POSIX.1-2001.
-(To get their definitions, define
+(To get their definitions, define either
.BR _BSD_SOURCE ,
or
.BR _XOPEN_SOURCE
-with the value 500 or greater, or define
+with the value 500 or greater, or
.BR _POSIX_C_SOURCE
with the value 200809L or greater.)
macro to obtain these definitions.)
.\" .PP
.\" SVr4 documents additional EIO, ENOLINK and EOVERFLOW error conditions.
+
+.BR F_OFD_SETLK ,
+.BR F_OFD_SETLKW ,
+and
+.BR F_OFD_GETLK
+are Linux-specific (and one must define
+.BR _GNU_SOURCE
+to obtain their definitions),
+but work is being done to have them included in the next version of POSIX.1.
.SH NOTES
The errors returned by
.BR dup2 (2)
wrapper function transparently employs the more recent system call
where it is available.
+The errors returned by
+.BR dup2 (2)
+are different from those returned by
+.BR F_DUPFD .
+.SS Record locks
Since kernel 2.0, there is no interaction between the types of lock
placed by
.BR flock (2)
.IR l_sysid .
.\" e.g., Solaris 8 documents this field in fcntl(2), and Irix 6.5
.\" documents it in fcntl(5). mtk, May 2007
+.\" Also, FreeBSD documents it (Apr 2014).
Clearly,
.I l_pid
alone is not going to be very useful if the process holding the lock
may live on a different machine.
+
+The original Linux
+.BR fcntl ()
+system call was not designed to handle large file offsets
+(in the
+.I flock
+structure).
+Consequently, an
+.BR fcntl64 ()
+system call was added in Linux 2.4.
+The newer system call employs a different structure for file locking,
+.IR flock64 ,
+and corresponding commands,
+.BR F_GETLK64 ,
+.BR F_SETLK64 ,
+and
+.BR F_SETLKW64 .
+However, these details can be ignored by applications using glibc, whose
+.BR fcntl ()
+wrapper function transparently employs the more recent system call
+where it is available.
+.SS Record locking and NFS
+Before Linux 3.12, if an NFSv4 client
+loses contact with the server for a period of time
+(defined as more than 90 seconds with no communication),
+.\"
+.\" Neil Brown: With NFSv3 the failure mode is the reverse. If
+.\" the server loses contact with a client then any lock stays in place
+.\" indefinitely ("why can't I read my mail"... I remember it well).
+.\"
+it might lose and regain a lock without ever being aware of the fact.
+(The period of time after which contact is assumed lost is known as
+the NFSv4 leasetime.
+On a Linux NFS server, this can be determined by looking at
+.IR /proc/fs/nfsd/nfsv4leasetime ,
+which expresses the period in seconds.
+The default value for this file is 90.)
+.\"
+.\" Jeff Layton:
+.\" Note that this is not a firm timeout. The server runs a job
+.\" periodically to clean out expired stateful objects, and it's likely
+.\" that there is some time (maybe even up to another whole lease period)
+.\" between when the timeout expires and the job actually runs. If the
+.\" client gets a RENEW in there within that window, its lease will be
+.\" renewed and its state preserved.
+.\"
+This scenario potentially risks data corruption,
+since another process might acquire a lock in the intervening period
+and perform file I/O.
+
+Since Linux 3.12,
+.\" commit ef1820f9be27b6ad158f433ab38002ab8131db4d
+if an NFSv4 client loses contact with the server,
+any I/O to the file by a process which "thinks" it holds
+a lock will fail until that process closes and reopens the file.
+A kernel parameter,
+.IR nfs.recover_lost_locks ,
+can be set to 1 to obtain the pre-3.12 behavior,
+whereby the client will attempt to recover lost locks
+when contact is reestablished with the server.
+Because of the attendant risk of data corruption,
+.\" commit f6de7a39c181dfb8a2c534661a53c73afb3081cd
+this parameter defaults to 0 (disabled).
.SH BUGS
.SS F_SETFL
It is not possible to use
has permission to send signals to.
Despite this error return, the file descriptor owner is set,
and signals will be sent to the owner.
+.\"
+.SS Deadlock detection
+The deadlock-detection algorithm employed by the kernel when dealing with
+.BR F_SETLKW
+requests can yield both
+false negatives (failures to detect deadlocks,
+leaving a set of deadlocked processes blocked indefinitely)
+and false positives
+.RB ( EDEADLK
+errors when there is no deadlock).
+For example,
+the kernel limits the lock depth of its dependency search to 10 steps,
+meaning that circular deadlock chains that exceed
+that size will not be detected.
+In addition, the kernel may falsely indicate a deadlock
+when two or more processes created using the
+.BR clone (2)
+.B CLONE_FILES
+flag place locks that appear (to the kernel) to conflict.
+.\"
.SS Mandatory locking
-The implementation of mandatory locking in all known versions of Linux
+The Linux implementation of mandatory locking
is subject to race conditions which render it unreliable:
.\" http://marc.info/?l=linux-kernel&m=119013491707153&w=2
+.\"
+.\" Reconfirmed by Jeff Layton
+.\" From: Jeff Layton <jlayton <at> redhat.com>
+.\" Subject: Re: Status of fcntl() mandatory locking
+.\" Newsgroups: gmane.linux.file-systems
+.\" Date: 2014-04-28 10:07:57 GMT
+.\" http://thread.gmane.org/gmane.linux.file-systems/84481/focus=84518
a
.BR write (2)
call that overlaps with a lock may modify data after the mandatory lock is
is called
.IR mandatory.txt )
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Substantial rewrites and additions
.\" 2005-05-10 mtk, noted that lock conversions are not atomic.
.\"
-.\" FIXME: Maybe document LOCK_MAND, LOCK_RW, LOCK_READ, LOCK_WRITE
-.\" which only have effect for SAMBA.
+.\" FIXME Maybe document LOCK_MAND, LOCK_RW, LOCK_READ, LOCK_WRITE
+.\" which only have effect for SAMBA.
.\"
-.TH FLOCK 2 2014-04-22 "Linux" "Linux Programmer's Manual"
+.TH FLOCK 2 2014-09-21 "Linux" "Linux Programmer's Manual"
.SH NAME
flock \- apply or remove an advisory lock on an open file
.SH SYNOPSIS
.BR fcntl (2),
appears on most UNIX systems.
.SH NOTES
-.BR flock ()
-does not lock files over NFS.
-Use
-.BR fcntl (2)
-instead: that does work over NFS, given a sufficiently recent version of
-Linux and a server which supports locking.
-.PP
Since kernel 2.0,
.BR flock ()
is implemented as a system call in its own right rather
than being emulated in the GNU C library as a call to
.BR fcntl (2).
-This yields true BSD semantics:
+With this implementation,
there is no interaction between the types of lock
placed by
.BR flock ()
and
.BR flock ()
does not detect deadlock.
+(Note, however, that on some systems, such as the modern BSDs,
+.\" E.g., according to the flock(2) man page, FreeBSD since at least 5.3
+.BR flock ()
+and
+.BR fcntl (2)
+locks
+.I do
+interact with one another.)
+.PP
+In Linux kernels up to 2.6.11,
+.BR flock ()
+does not lock files over NFS
+(i.e., the scope of locks was limited to the local system).
+Instead, one could use
+.BR fcntl (2)
+byte-range locking, which does work over NFS,
+given a sufficiently recent version of
+Linux and a server which supports locking.
+Since Linux 2.6.12, NFS clients support
+.BR flock ()
+locks by emulating them as byte-range locks on the entire file.
+This means that
+.BR fcntl (2)
+and
+.BR flock ()
+locks
+.I do
+interact with one another over NFS.
+Since Linux 2.6.37,
+.\" commit 5eebde23223aeb0ad2d9e3be6590ff8bbfab0fc2
+the kernel supports a compatibility mode that allows
+.BR flock ()
+locks (and also
+.BR fcntl (2)
+byte region locks) to be treated as local;
+see the discussion of the
+.I "local_lock"
+option in
+.BR nfs (5).
.PP
.BR flock ()
places advisory locks only; given suitable permissions on a file,
.RI ( Documentation/locks.txt
in older kernels)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
The child does not inherit semaphore adjustments from its parent
.RB ( semop (2)).
.IP *
-The child does not inherit record locks from its parent
+The child does not inherit process-associated record locks from its parent
.RB ( fcntl (2)).
+(On the other hand, it does inherit
+.BR fcntl (2)
+open file description locks and
+.BR flock (2)
+locks from its parent.)
.IP *
The child does not inherit timers from its parent
.RB ( setitimer (2),
.BR capabilities (7),
.BR credentials (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2006-04-28, mtk, substantial rewrite of various parts.
.\" 2012-02-27 Various changes by Christoph Hellwig <hch@lst.de>
.\"
-.TH FSYNC 2 2014-04-06 "Linux" "Linux Programmer's Manual"
+.TH FSYNC 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
fsync, fdatasync \- synchronize a file's in-core state with storage device
.SH SYNOPSIS
.BR sync_file_range (2),
.BR hdparm (8),
.BR mount (8),
-.BR sync (8)
+.BR sync (1)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 2004-06-17 mtk
.\" Modified 2004-10-07 aeb, added FUTEX_REQUEUE, FUTEX_CMP_REQUEUE
.\"
-.\" FIXME
+.\" FIXME .
.\" See also https://bugzilla.kernel.org/show_bug.cgi?id=14303
.\" 2.6.14 adds FUTEX_WAKE_OP
.\" commit 4732efbeb997189d9f9b04708dc26bf8613ed721
.\" Author: Jakub Jelinek <jakub@redhat.com>
.\" Date: Tue Sep 6 15:16:25 2005 -0700
.\"
-.\" FIXME
+.\" FIXME .
.\" 2.6.18 adds (Ingo Molnar) priority inheritance support:
.\" FUTEX_LOCK_PI, FUTEX_UNLOCK_PI, and FUTEX_TRYLOCK_PI. These need
.\" to be documented in the manual page. Probably there is sufficient
.\"
.\" See Documentation/pi-futex.txt
.\"
-.\" FIXME
+.\" FIXME .
.\" 2.6.25 adds FUTEX_WAKE_BITSET, FUTEX_WAIT_BITSET
.\" commit cd689985cf49f6ff5c8eddc48d98b9d581d9475d
.\" Author: Thomas Gleixner <tglx@linutronix.de>
.\" Date: Fri Feb 1 17:45:14 2008 +0100
.\"
-.\" FIXME
+.\" FIXME .
.\" 2.6.31 adds FUTEX_WAIT_REQUEUE_PI, FUTEX_CMP_REQUEUE_PI
.\" commit 52400ba946759af28442dee6265c5c0180ac7122
.\" Author: Darren Hart <dvhltc@us.ibm.com>
.UR ftp://ftp.kernel.org\:/pub\:/linux\:/kernel\:/people\:/rusty/
.UE
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR futimes (3),
.BR path_resolution (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR init_module (2),
.BR query_module (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR numa (7),
.BR numactl (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
in the Linux kernel source tree
.\" http://lwn.net/Articles/172149/
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR modify_ldt (2),
.BR set_thread_area (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sched_getcpu (3),
.BR cpuset (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.IR linux_dirent
structure.
.SH EXAMPLE
-.\" FIXME: This program uses the older getdents() system call
-.\" and the structure with smaller field widths.
+.\" FIXME The example program needs to be revised, since it uses the older
+.\" getdents() system call and the structure with smaller field widths.
The program below demonstrates the use of
.BR getdents ().
The following output shows an example of what we see when running this
.BR readdir (2),
.BR readdir (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sethostname (2),
.BR uname (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR setregid (2),
.BR credentials (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2008-05-03, mtk, expanded and rewrote parts of DESCRIPTION and RETURN
.\" VALUE, made style of page more consistent with man-pages style.
.\"
-.TH GETGROUPS 2 2013-10-18 "Linux" "Linux Programmer's Manual"
+.TH GETGROUPS 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
getgroups, setgroups \- get/set list of supplementary group IDs
.SH SYNOPSIS
.BR getgid (2),
.BR setgid (2),
.BR getgrouplist (3),
+.BR group_member (3),
.BR initgroups (3),
.BR capabilities (7),
.BR credentials (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 2004-06-17 by mtk
.\" Modified 2008-11-27 by mtk
.\"
-.TH GETHOSTNAME 2 2010-09-26 "Linux" "Linux Programmer's Manual"
+.TH GETHOSTNAME 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
gethostname, sethostname \- get/set hostname
.SH SYNOPSIS
.B HOST_NAME_MAX
is defined with the value 64, which has been the limit since Linux 1.0
(earlier kernels imposed a limit of 8 bytes).
-.SS Glibc notes
+.SS C library/kernel ABI differences
The GNU C library does not employ the
.BR gethostname ()
system call; instead, it implements
.BR setdomainname (2),
.BR uname (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2005-04-06 mtk, Matthias Lang <matthias@corelatus.se>
.\" Noted MAX_SEC_IN_JIFFIES ceiling
.\"
-.TH GETITIMER 2 2012-10-01 "Linux" "Linux Programmer's Manual"
+.TH GETITIMER 2 2014-07-08 "Linux" "Linux Programmer's Manual"
.SH NAME
getitimer, setitimer \- get or set value of an interval timer
.SH SYNOPSIS
.SH DESCRIPTION
The system provides each process with three interval timers,
each decrementing in a distinct time domain.
-When any timer expires, a signal is sent to the
-process, and the timer (potentially) restarts.
+When a timer expires, a signal is sent to the
+process, and the timer is reset to the specified interval (if nonzero).
.TP 1.5i
.B ITIMER_REAL
decrements in real time, and delivers
.nf
struct itimerval {
- struct timeval it_interval; /* next value */
- struct timeval it_value; /* current value */
+ struct timeval it_interval; /* Interval for periodic timer */
+ struct timeval it_value; /* Time until next expiration */
};
struct timeval {
.BR getitimer ()
fills the structure pointed to by
.I curr_value
-with the current setting for the timer specified by
+with the current value
+(i.e., the amount of time remaining until the next expiration)
+of the timer specified by
.I which
(one of
.BR ITIMER_REAL ,
.BR ITIMER_VIRTUAL ,
or
.BR ITIMER_PROF ).
-The element
+The subfields of the field
.I it_value
-is set to the amount of time remaining on the timer, or zero if the timer
+are set to the amount of time remaining on the timer, or zero if the timer
is disabled.
-Similarly,
+The
.I it_interval
-is set to the reset value.
+field is set to the timer interval (period);
+a value of zero returned in (both subfields of) this field indicates
+that this is a single-shot timer.
The function
.BR setitimer ()
.IR new_value .
If
.I old_value
-is non-NULL, the old value of the timer is stored there.
+is non-NULL, the old value of the timer
+(i.e., the same information as returned by
+.BR getitimer ())
+is stored there.
.LP
Timers decrement from
.I it_value
.BR timerfd_create (2),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH GETPAGESIZE 2 2010-11-16 "Linux" "Linux Programmer's Manual"
+.TH GETPAGESIZE 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
getpagesize \- get memory page size
.SH SYNOPSIS
at compile time from a header file,
but use an actual system call, at least for those architectures
(like sun4) where this dependency exists.
-Here libc4, libc5, glibc 2.0 fail because their
+Here glibc 2.0 fails because its
.BR getpagesize ()
returns a statically derived value, and does not use a system call.
Things are OK in glibc 2.1.
.BR mmap (2),
.BR sysconf (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR socket (7),
.BR unix (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH GETPID 2 2008-09-23 "Linux" "Linux Programmer's Manual"
+.TH GETPID 2 2014-09-21 "Linux" "Linux Programmer's Manual"
.SH NAME
getpid, getppid \- get process identification
.SH SYNOPSIS
.BR tempnam (3),
.BR tmpfile (3),
.BR tmpnam (3),
-.BR credentials (7)
+.BR credentials (7),
+.BR pid_namespaces (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Clarified meaning of 0 value for 'who' argument
.\" Modified 2004-05-27 by Michael Kerrisk <mtk.manpages@gmail.com>
.\"
-.\" FIXME Oct 2008: Denys Vlasenko is working on a PRIO_THREAD feature that
-.\" is likely to get included in mainline; this will need to be documented.
-.\"
-.TH GETPRIORITY 2 2014-05-10 "Linux" "Linux Programmer's Manual"
+.TH GETPRIORITY 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
getpriority, setpriority \- get/set program scheduling priority
.SH SYNOPSIS
The actual priority range varies between kernel versions.
Linux before 1.3.36 had \-infinity..15.
Since kernel 1.3.43, Linux has the range \-20..19.
-Within the kernel, nice values are actually represented
-using the corresponding range 40..1
-(since negative numbers are error codes) and these are the values
-employed by the
-.BR setpriority ()
-and
-.BR getpriority ()
-system calls.
-The glibc wrapper functions for these system calls handle the
-translations between the user-land and kernel representations
-of the nice value according to the formula
-.IR "unice\ =\ 20\ \-\ knice" .
-.LP
-On some systems, the range of nice values is \-20..20.
-.LP
+On some other systems, the range of nice values is \-20..20.
+
Including
.I <sys/time.h>
is not required these days, but increases portability.
.I struct timeval
defined in
.IR <sys/time.h> .)
+.\"
+.SS C library/kernel ABI differences
+Within the kernel, nice values are actually represented
+using the range 40..1
+(since negative numbers are error codes) and these are the values
+employed by the
+.BR setpriority ()
+and
+.BR getpriority ()
+system calls.
+The glibc wrapper functions for these system calls handle the
+translations between the user-land and kernel representations
+of the nice value according to the formula
+.IR "unice\ =\ 20\ \-\ knice" .
+(Thus, the kernels 40..1 range corresponds to the
+range \-20..19 as seen by user space.)
.SH BUGS
According to POSIX, the nice value is a per-process setting.
However, under the current Linux/NPTL implementation of POSIX threads,
.I Documentation/scheduler/sched-nice-design.txt
in the Linux kernel source tree (since Linux 2.6.23)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR setuid (2),
.BR credentials (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2008-05-07, mtk / Peter Zijlstra, Added description of RLIMIT_RTTIME
.\" 2010-11-06, mtk: Added documentation of prlimit()
.\"
-.TH GETRLIMIT 2 2014-05-28 "Linux" "Linux Programmer's Manual"
+.TH GETRLIMIT 2 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
getrlimit, setrlimit, prlimit \- get/set resource limits
.SH SYNOPSIS
.\" since 2.0.27 / 2.1.12
This limit affects calls to
.BR brk (2),
-.BR mmap (2)
+.BR mmap (2),
and
.BR mremap (2),
which fail with the error
either this limit is at most 2 GiB, or this resource is unlimited.
.TP
.B RLIMIT_CORE
-Maximum size of
+Maximum size of a
.I core
-file.
+file (see
+.BR core (5)).
When 0 no core dump files are created.
When nonzero, larger dumps are truncated to this size.
.TP
against this limit according to the formula:
.nf
- bytes = attr.mq_maxmsg * sizeof(struct msg_msg *) +
- attr.mq_maxmsg * attr.mq_msgsize
+ Since Linux 3.5:
+ bytes = attr.mq_maxmsg * sizeof(struct msg_msg) +
+ min(attr.mq_maxmsg, MQ_PRIO_MAX) *
+ sizeof(struct posix_msg_tree_node)+
+ /* For overhead */
+ attr.mq_maxmsg * attr.mq_msgsize;
+ /* For message data */
+
+ Linux 3.4 and earlier:
+ bytes = attr.mq_maxmsg * sizeof(struct msg_msg *) +
+ /* For overhead */
+ attr.mq_maxmsg * attr.mq_msgsize;
+ /* For message data */
.fi
where
is the
.I mq_attr
structure specified as the fourth argument to
-.BR mq_open (3).
+.BR mq_open (3),
+and the
+.I msg_msg
+and
+.I posix_msg_tree_node
+structures are kernel-internal structures.
-The first addend in the formula, which includes
-.I "sizeof(struct msg_msg\ *)"
-(4 bytes on Linux/i386), ensures that the user cannot
+The "overhead" addend in the formula accounts for overhead
+bytes required by the implementation
+and ensures that the user cannot
create an unlimited number of zero-length messages (such messages
nevertheless each consume some system memory for bookkeeping overhead).
.TP
.\" commit c022a0acad534fd5f5d5f17280f6d4d135e74e81
.\" Author: Jiri Slaby <jslaby@suse.cz>
.\" Date: Tue May 4 18:03:50 2010 +0200
+.\"
+.\" rlimits: implement prlimit64 syscall
+.\"
+.\" commit 6a1d5e2c85d06da35cdfd93f1a27675bfdc3ad8c
+.\" Author: Jiri Slaby <jslaby@suse.cz>
+.\" Date: Wed Mar 24 17:06:58 2010 +0100
+.\"
+.\" rlimits: add rlimit64 structure
+.\"
The Linux-specific
.BR prlimit ()
system call combines and extends the functionality of
.I and
the real, effective, and saved set group IDs of the target process
must match the real group ID of the caller.
-.\" FIXME this permission check is strange
+.\" FIXME . this permission check is strange
.\" Asked about this on LKML, 7 Nov 2010
.\" "Inconsistent credential checking in prlimit() syscall"
.SH RETURN VALUE
.BR vlimit ().
All new applications should be written using
.BR setrlimit ().
+.SS C library/ kernel ABI differences
+Since version 2.13, the glibc
+.BR getrlimit ()
+and
+.BR setrlimit ()
+wrapper functions no longer invoke the corresponding system calls,
+but instead employ
+.BR prlimit (),
+for the reasons described in BUGS.
.SH BUGS
-.\" FIXME prlimit() does not suffer
-.\" https://bugzilla.kernel.org/show_bug.cgi?id=5042
-.\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=12201
-.\" Since versions 2.13, glibc has library implementations of
-.\" getrlimit() and setrlimit() that use prlimit() to work around
-.\" this bug.
In older Linux kernels, the
.B SIGXCPU
and
soft limit in this manner,
and the Linux behavior is probably not standards conformant;
portable applications should avoid relying on this Linux-specific behavior.
-.\" FIXME https://bugzilla.kernel.org/show_bug.cgi?id=50951
+.\" FIXME . https://bugzilla.kernel.org/show_bug.cgi?id=50951
The Linux-specific
.BR RLIMIT_RTTIME
limit exhibits the same behavior when the soft limit is encountered.
.I rlim\->rlim_cur
was greater than
.IR rlim\->rlim_max .
+.\"
+.SS Representation of """large""" resource limit values on 32-bit platforms
+The glibc
+.BR getrlimit ()
+and
+.BR setrlimit ()
+wrapper functions use a 64-bit
+.IR rlim_t
+data type, even on 32-bit platforms.
+However, the
+.I rlim_t
+data type used in the
+.BR getrlimit ()
+and
+.BR setrlimit ()
+system calls is a (32-bit)
+.IR "unsigned long" .
+Furthermore, in Linux versions before 2.6.36,
+the kernel represents resource limits on 32-bit platforms as
+.IR "unsigned long" .
+However, a 32-bit data type is not wide enough.
+.\" https://bugzilla.kernel.org/show_bug.cgi?id=5042
+.\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=12201
+The most pertinent limit here is
+.BR RLIMIT_FSIZE ,
+which specifies the maximum size to which a file can grow:
+to be useful, this limit must be represented using a type
+that is as wide as the type used to
+represent file offsets\(emthat is, as wide as a 64-bit
+.BR off_t
+(assuming a program compiled with
+.IR _FILE_OFFSET_BITS=64 ).
+
+To work around this kernel limitation,
+if a program tried to set a resource limit to a value larger than
+can be represented in a 32-bit
+.IR "unsigned long" ,
+then the glibc
+.BR setrlimit ()
+wrapper function silently converted the limit value to
+.BR RLIM_INFINITY .
+In other words, the requested resource limit setting was silently ignored.
+
+This problem was addressed in Linux 2.6.36 with two principal changes:
+.IP * 3
+the addition of a new kernel representation of resource limits that
+uses 64 bits, even on 32-bit platforms;
+.IP *
+the addition of the
+.BR prlimit ()
+system call, which employs 64-bit values for its resource limit arguments.
+.PP
+Since version 2.13,
+.\" https://www.sourceware.org/bugzilla/show_bug.cgi?id=12201
+glibc works around the limitations of the
+.BR getrlimit ()
+and
+.BR setrlimit ()
+system calls by implementing
+.BR setrlimit ()
+and
+.BR getrlimit ()
+as wrapper functions that call
+.BR prlimit ().
.SH EXAMPLE
The program below demonstrates the use of
.BR prlimit ().
.BR capabilities (7),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wait4 (2),
.BR clock (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR setsid (2),
.BR credentials (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR socket (7),
.BR unix (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR udp (7),
.BR unix (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH NOTES
Glibc does not provide a wrapper for this system call; call it using
.BR syscall (2).
-.\" FIXME See http://sourceware.org/bugzilla/show_bug.cgi?id=6399
+.\" FIXME . See http://sourceware.org/bugzilla/show_bug.cgi?id=6399
.\" "gettid() should have a wrapper"
The thread ID returned by this call is not the same thing as a
.BR tgkill (2),
.BR timer_create (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
or
.I tz
is NULL, the corresponding structure is not set or returned.
-.\" FIXME The compilation warning looks to be going away in 2.17
+.\" FIXME . The compilation warning looks to be going away in 2.17
.\" see glibc commit 4b7634a5e03b0da6f8875de9d3f74c1cf6f2a6e8
(However, compilation warnings will result if
.I tv
argument should normally be specified as NULL.
(See NOTES below.)
-Under Linux there are some peculiar "warp clock" semantics associated
+Under Linux, there are some peculiar "warp clock" semantics associated
with the
.BR settimeofday ()
system call if on the very first call (after booting)
.BR capabilities (7),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR setuid (2),
.BR credentials (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH GETUNWIND 2 2013-02-13 Linux "Linux Programmer's Manual"
+.TH GETUNWIND 2 2014-09-21 Linux "Linux Programmer's Manual"
.SH NAME
getunwind \- copy the unwind data to caller's buffer
.SH SYNOPSIS
.SH RETURN VALUE
On success,
.BR getunwind ()
-returns the size of unwind table.
+returns the size of the unwind data.
On error, \-1 is returned and
.I errno
is set to indicate the error.
.SH SEE ALSO
.BR getauxval (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR attr (5),
.BR symlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
This function is Linux-specific, and should not be used in programs
intended to be portable.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR lsmod (8),
.BR modprobe (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2005-07-19 Robert Love <rlove@rlove.org> - initial version
.\" 2006-02-07 mtk, various changes
.\"
-.TH INOTIFY_ADD_WATCH 2 2014-03-28 "Linux" "Linux Programmer's Manual"
+.TH INOTIFY_ADD_WATCH 2 2014-07-08 "Linux" "Linux Programmer's Manual"
.SH NAME
inotify_add_watch \- add a watch to an initialized inotify instance
.SH SYNOPSIS
A successful call to
.BR inotify_add_watch ()
-returns the unique watch descriptor associated with
-.I pathname
-for this inotify instance.
-If
-.I pathname
+returns a unique watch descriptor for this inotify instance,
+for the filesystem object that corresponds to
+.IR pathname .
+If the filesystem object
was not previously being watched by this inotify instance,
then the watch descriptor is newly allocated.
-If
-.I pathname
-was already being watched, then the descriptor
+If the filesystem object was already being watched
+(perhaps via a different link to the same object), then the descriptor
for the existing watch is returned.
The watch descriptor is returned by later
.BR inotify_rm_watch (2),
.BR inotify (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR inotify_rm_watch (2),
.BR inotify (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR inotify_init (2),
.BR inotify (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR symlink (7),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" .SH AUTHOR
.\" Kent Yoder.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" .SH AUTHOR
.\" Kent Yoder.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" .SH AUTHOR
.\" Kent Yoder.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" .SH AUTHOR
.\" Kent Yoder.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" .SH AUTHOR
.\" Kent Yoder.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sd (4),
.BR tty (4)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR ioctl (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified, 27 May 2004, Michael Kerrisk <mtk.manpages@gmail.com>
.\" Added notes on capability requirements
.\"
-.TH IOPERM 2 2013-03-12 "Linux" "Linux Programmer's Manual"
+.TH IOPERM 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
ioperm \- set port input/output permissions
.SH SYNOPSIS
-.B #include <unistd.h>
-/* for libc5 */
-.br
.B #include <sys/io.h>
/* for glibc */
.sp
.I /proc/ioports
file shows the I/O ports that are currently allocated on the system.
-Libc5 treats it as a system call and has a prototype in
-.IR <unistd.h> .
-Glibc1 does not have a prototype.
-Glibc2 has a prototype both in
+Glibc has an
+.BR ioperm ()
+prototype both in
.I <sys/io.h>
and in
.IR <sys/perm.h> .
.BR outb (2),
.BR capabilities (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR outb (2),
.BR capabilities (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.I who
is a user ID identifying all of the processes that
have a matching real UID.
-.\" FIXME who==0 needs to be documented,
+.\" FIXME . Need to document the behavior when 'who" is specified as 0
.\" See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652443
.PP
If
.I Documentation/block/ioprio.txt
in the Linux kernel source tree
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR shmdt (2),
.BR shmget (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR clone (2),
.BR unshare (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH KEXEC_LOAD 2 2012-07-13 "Linux" "Linux Programmer's Manual"
+.TH KEXEC_LOAD 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
kexec_load \- load a new kernel for later execution
.SH SYNOPSIS
.PP
The
.I flags
-argument is a mask whose high-order bits control the operation of the call.
+argument is a bit mask that controls the operation of the call.
The following values can be specified in
.IR flags :
.TP
.BR KEXEC_ON_CRASH " (since Linux 2.6.13)"
Execute the new kernel automatically on a system crash.
-.\" FIXME figure out how this is really used
+.\" FIXME Explain in more detail how KEXEC_ON_CRASH is actually used
.TP
.BR KEXEC_PRESERVE_CONTEXT " (since Linux 2.6.27)"
Preserve the system hardware and
.I nr_segments
is greater than 0.
.PP
-The low-order bits of
+The high-order bits (corresponding to the mask 0xffff0000) of
.I flags
contain the architecture of the to-be-executed kernel.
Specify (OR) the constant
to use the current architecture,
or one of the following architecture constants
.BR KEXEC_ARCH_386 ,
+.BR KEXEC_ARCH_68K ,
.BR KEXEC_ARCH_X86_64 ,
.BR KEXEC_ARCH_PPC ,
.BR KEXEC_ARCH_PPC64 ,
.I nr_segments
argument is the number of segments pointed to by the
.I segments
-pointer.
+pointer;
+the kernel imposes an (arbitrary) limit of 16 on the number of segments.
The
.I segments
argument is an array of
.fi
.in
.PP
-.\" FIXME elaborate on the following:
+.\" FIXME Explain the details of how the kernel image defined by segments
+.\" is copied from the calling process into previously reserved memory.
The kernel image defined by
.I segments
is copied from the calling process into previously reserved memory.
The required constants are in the Linux kernel source file
.IR linux/kexec.h ,
which is not currently exported to glibc.
-.\" FIXME Andi submitted a patch for this.
+.\" FIXME . Andi submitted a patch for this.
.\" Check if it got accepted later.
Therefore, these constants must be defined manually.
.BR reboot (2),
.BR syscall (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
The kernel source file
.IR Documentation/security/keys.txt .
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR credentials (7),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR capabilities (7),
.BR credentials (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 2004-06-23 by Michael Kerrisk <mtk.manpages@gmail.com>
.\" Modified 2005-04-04, as per suggestion by Michael Hardt for rename.2
.\"
-.TH LINK 2 2014-05-10 "Linux" "Linux Programmer's Manual"
+.TH LINK 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
link, linkat \- make a new name for a file
.SH SYNOPSIS
For precise control over the treatment of symbolic links when
creating a link, use
.BR linkat (2).
+.SS Glibc notes
+On older kernels where
+.BR linkat ()
+is unavailable, the glibc wrapper function falls back to the use of
+.BR link (),
+unless the
+.B AT_SYMLINK_FOLLOW
+is specified.
+When
+.I oldpath
+and
+.I newpath
+are relative pathnames,
+glibc constructs pathnames based on the symbolic links in
+.IR /proc/self/fd
+that correspond to the
+.I olddirfd
+and
+.IR newdirfd
+arguments.
.SH BUGS
On NFS filesystems, the return code may be wrong in case the NFS server
performs the link creation and dies before it can say so.
.BR path_resolution (7),
.BR symlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR socket (2),
.BR socket (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR attr (5),
.BR symlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR lseek (2),
.BR lseek64 (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
The path returned may be suffixed by the string " (deleted)" if the directory
entry has been removed.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 2003-08-21 by Andries Brouwer <aeb@cwi.nl>
.\" 2011-09-18, mtk, Added SEEK_DATA + SEEK_HOLE
.\"
-.TH LSEEK 2 2014-01-22 "Linux" "Linux Programmer's Manual"
+.TH LSEEK 2 2014-06-13 "Linux" "Linux Programmer's Manual"
.SH NAME
lseek \- reposition read/write file offset
.SH SYNOPSIS
they are proposed for inclusion in the next POSIX revision (Issue 8).
.\" FIXME . Review http://austingroupbugs.net/view.php?id=415 in the future
.SH NOTES
+See
+.BR open (2)
+for a discussion of the relationship between file descriptors,
+open file descriptions, and files.
+
Some devices are incapable of seeking and POSIX does not specify which
devices must support
.BR lseek ().
.BR lseek64 (3),
.BR posix_fallocate (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR prctl (2),
.BR core (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR numa (7),
.BR numactl (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
No process matching
.I pid
could be found.
-.\" FIXME There are other errors
+.\" FIXME Document the other errors that can occur for migrate_pages()
.SH VERSIONS
The
.BR migrate_pages ()
.IR Documentation/vm/page_migration
in the Linux kernel source tree
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mlock (2),
.BR mmap (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Public License. It comes with NO WARRANTY.
.\" %%%LICENSE_END
.\"
-.TH MKDIR 2 2014-02-21 "Linux" "Linux Programmer's Manual"
+.TH MKDIR 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
mkdir, mkdirat \- create a directory
.SH SYNOPSIS
.BR mkdirat ():
POSIX.1-2008.
.SH NOTES
-Under Linux apart from the permission bits, only the
+Under Linux, apart from the permission bits, only the
.B S_ISVTX
mode bit is honored.
That is, under Linux the created directory actually gets mode
There are many infelicities in the protocol underlying NFS.
Some of these affect
.BR mkdir ().
+.SS Glibc notes
+On older kernels where
+.BR mkdirat ()
+is unavailable, the glibc wrapper function falls back to the use of
+.BR mkdir ().
+When
+.I pathname
+is a relative pathname,
+glibc constructs a pathname based on the symbolic link in
+.IR /proc/self/fd
+that corresponds to the
+.IR dirfd
+argument.
.SH SEE ALSO
.BR mkdir (1),
.BR chmod (2),
.BR unlink (2),
.BR path_resolution (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mkfifo (3),
.BR path_resolution (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR proc (5),
.BR capabilities (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2007-07-10, mtk, Added an example program.
.\" 2008-11-18, mtk, document MAP_STACK
.\"
-.TH MMAP 2 2014-04-06 "Linux" "Linux Programmer's Manual"
+.TH MMAP 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
mmap, munmap \- map or unmap files or devices into memory
.SH SYNOPSIS
.SH AVAILABILITY
On POSIX systems on which
.BR mmap (),
-.BR msync (2)
+.BR msync (2),
and
.BR munmap ()
are available,
.\" -1: unavailable, 0: ask using sysconf().
.\" glibc defines it to 1.
.SH NOTES
-This page describes the interface provided by the glibc
-.BR mmap ()
-wrapper function.
-Originally, this function invoked a system call of the same name.
-Since kernel 2.4, that system call has been superseded by
-.BR mmap2 (2),
-and nowadays
-.\" Since around glibc 2.1/2.2, depending on the platform.
-the glibc
-.BR mmap ()
-wrapper function invokes
-.BR mmap2 (2)
-with a suitably adjusted value for
-.IR offset .
-
On some hardware architectures (e.g., i386),
.B PROT_WRITE
implies
.BR MAP_POPULATE ,
and
.BR MAP_STACK .
+.\"
+.SS C library/kernel ABI differences
+This page describes the interface provided by the glibc
+.BR mmap ()
+wrapper function.
+Originally, this function invoked a system call of the same name.
+Since kernel 2.4, that system call has been superseded by
+.BR mmap2 (2),
+and nowadays
+.\" Since around glibc 2.1/2.2, depending on the platform.
+the glibc
+.BR mmap ()
+wrapper function invokes
+.BR mmap2 (2)
+with a suitably adjusted value for
+.IR offset .
.SH BUGS
On Linux there are no guarantees like those suggested above under
.BR MAP_NORESERVE .
.\" Repeat after me: private read-only mappings are 100% equivalent to
.\" shared read-only mappings. No ifs, buts, or maybes. -- Linus
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR msync (2),
.BR shm_open (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.I bytecount
must equal the size of this structure.
.\"
-.\" FIXME ? say something about func == 2 and func == 0x11?
+.\" FIXME Should this page say something about func == 2 and func == 0x11?
.\" In Linux 2.4, func == 2 returned "the default ldt"
.\" In Linux 2.6, func == 2 is a nop, returning a zeroed out structure.
.\" Linux 2.4 and 2.6 implement an operation for func == 0x11
.SH SEE ALSO
.BR vm86 (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2008-10-06, mtk: move umount*() material into separate umount.2 page.
.\" 2008-10-06, mtk: Add discussion of namespaces.
.\"
-.TH MOUNT 2 2014-03-17 "Linux" "Linux Programmer's Manual"
+.TH MOUNT 2 2014-09-21 "Linux" "Linux Programmer's Manual"
.SH NAME
mount \- mount filesystem
.SH SYNOPSIS
.\"
.\" These settings are visible in proc/mountinfo
.\"
-.\"
.\" These need to be documented on this page.
.\" See:
.\" Documentation/filesystems/sharedsubtree.txt
.\" Ram Pai (linuxram@us.ibm.com), Software Engineer, IBM
.\" Date: 17 Sep 2007
.\"
-.\" 2.6.25 Added MS_I_VERSION, which needs to be documented.
+.\" FIXME 2.6.25 Added MS_I_VERSION, which needs to be documented.
.\"
.TP
.BR MS_BIND " (Linux 2.4 onward)"
(Mandatory locking must still be enabled on a per-file basis,
as described in
.BR fcntl (2).)
-.\" FIXME Say more about MS_MOVE
+.\" FIXME Describe the MS_MOVE flag in more detail
.TP
.B MS_MOVE
Move a subtree.
and
.I filesystemtype
are ignored.
+The
+.I mountflags
+and
+.I data
+arguments should match the values used in the original
+.BR mount ()
+call, except for those parameters that are being deliberately changed.
The following
.I mountflags
and
.BR MS_STRICTATIME
were added to glibc headers in version 2.12.
-.\" FIXME: Definitions of the so-far-undocumented MS_UNBINDABLE, MS_PRIVATE,
-.\" MS_SHARED, and MS_SLAVE were (also) only added to glibc headers in 2.12.
+.\" FIXME . Definitions of the so-far-undocumented MS_UNBINDABLE, MS_PRIVATE,
+.\" MS_SHARED, and MS_SLAVE were (also) only added to glibc headers in 2.12.
.SH "CONFORMING TO"
This function is Linux-specific and should not be used in
programs intended to be portable.
.BR proc (5)
for details.
.SH "SEE ALSO"
-.BR lsblk (1),
.BR umount (2),
.BR namespaces (7),
.BR path_resolution (7),
+.BR lsblk (8),
.BR mount (8),
.BR umount (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" permission notice identical to this one.
.\" %%%LICENSE_END
.\"
-.\" FIXME Should programs normally be using this API directly, or should
+.\" FIXME Should programs normally be using move_pages() directly, or should
.\" they rather be using interfaces in the numactl package?
.\" (e.g., compare with recommendation in mbind(2)).
+.\" Does this page need to give advise on this topic?
.TH MOVE_PAGES 2 2010-06-11 "Linux" "Linux Programmer's Manual"
.SH NAME
move_pages \- move individual pages of a process to another node
.I pages
is an array of pointers to the pages that should be moved.
These are pointers that should be aligned to page boundaries.
-.\" FIXME what if they are not aligned?
+.\" FIXME Describe the result if pointers in the 'pages' array are
+.\" not aligned to page boundaries
Addresses are specified as seen by the process specified by
.IR pid .
On success
.BR move_pages ()
returns zero.
-.\" FIXME Is the following quite true: does the wrapper in numactl
+.\" FIXME . Is the following quite true: does the wrapper in numactl
.\" do the right thing?
On error, it returns \-1, and sets
.I errno
Too many pages to move.
.TP
.B EACCES
-.\" FIXME Clarify "current cpuset". Is that the cpuset of the caller
-.\" or the target?
+.\" FIXME Clarify "current cpuset" in the description of the EACCESS error.
+.\" Is that the cpuset of the caller or the target?
One of the target nodes is not allowed by the current cpuset.
.TP
.B EFAULT
.BR migratepages (8),
.BR numastat (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 2004-08-16 by Andi Kleen <ak@muc.de>
.\" 2007-06-02, mtk: Fairly substantial rewrites and additions, and
.\" a much improved example program.
+.\"
.\" FIXME The following protection flags need documenting:
.\" PROT_SEM
.\" PROT_GROWSDOWN
.TP
.B PROT_EXEC
The memory can be executed.
-.\" FIXME
-.\" Document PROT_GROWSUP and PROT_GROWSDOWN
.SH RETURN VALUE
On success,
.BR mprotect ()
.BR mmap (2),
.BR sysconf (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mq_getattr (3),
.BR mq_overview (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
\fIInside Linux\fP by Randolf Bentson,
\fIThe Design of the UNIX Operating System\fP by Maurice J. Bach)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mq_overview (7),
.BR svipc (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mq_overview (7),
.BR svipc (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified, 11 Nov 2004, Michael Kerrisk <mtk.manpages@gmail.com>
.\" Language and formatting clean-ups
.\" Added notes on /proc files
-.\" FIXME . Add example programs to this page.
.\"
-.TH MSGOP 2 2014-05-16 "Linux" "Linux Programmer's Manual"
+.\" FIXME Add example programs to this page.
+.\"
+.TH MSGOP 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
msgrcv, msgsnd \- System V message queue operations
.SH SYNOPSIS
The
.I msgp
-argument is declared as \fIstruct msgbuf\ *\fP with
-libc4, libc5, glibc 2.0, glibc 2.1.
+argument is declared as \fIstruct msgbuf\ *\fP in
+glibc 2.0 and 2.1.
It is declared as \fIvoid\ *\fP
-with glibc 2.2 and later, as required by SUSv2 and SUSv3.
+in glibc 2.2 and later, as required by SUSv2 and SUSv3.
The following limits on message queue resources affect the
.BR msgsnd ()
.I msgtyp
messages, then the call would block until the next message is written
to the queue.
-.\" FIXME http://marc.info/?l=linux-kernel&m=139048542803605&w=2
+.\" http://marc.info/?l=linux-kernel&m=139048542803605&w=2
At that point, the call would return a copy of the message,
.I regardless
of whether that message was at the ordinal position
is a logical error (since these flags impose different interpretations on
.IR msgtyp ).
In Linux 3.13 and earlier,
-.\" FIXME http://marc.info/?l=linux-kernel&m=139048542803605&w=2
+.\" http://marc.info/?l=linux-kernel&m=139048542803605&w=2
this error was not diagnosed by
.BR msgrcv ().
This bug is fixed
.BR mq_overview (7),
.BR svipc (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
B.O. Gallmeister, POSIX.4, O'Reilly, pp. 128-129 and 389-391.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR usleep (3),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" This text is in the public domain.
.\" %%%LICENSE_END
.\"
-.\" FIXME The description of nfsservctl() on this page
+.\" FIXME . The description of nfsservctl() on this page
.\" is woefully thin.
.\"
.TH NFSSERVCTL 2 2013-09-17 "Linux" "Linux Programmer's Manual"
.SH CONFORMING TO
This call is Linux-specific.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
supplying a negative
.I inc
but has insufficient privileges.
-Under Linux the
+Under Linux, the
.B CAP_SYS_NICE
capability is required.
(But see the discussion of the
.BR capabilities (7),
.BR sched (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" FIXME . Apr 08: The next POSIX revision has O_EXEC, O_SEARCH, and
.\" O_TTYINIT. Eventually these may need to be documented. --mtk
.\"
-.TH OPEN 2 2014-05-10 "Linux" "Linux Programmer's Manual"
+.TH OPEN 2 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
open, openat, creat \- open and possibly create a file
.SH SYNOPSIS
(i.e., the
.B FD_CLOEXEC
file descriptor flag described in
-.BR fcntl (2))
-is initially disabled; the
+.BR fcntl (2)
+is initially disabled); the
.B O_CLOEXEC
flag, described below, can be used to change this default.
The file offset is set to the beginning of the file (see
creates a new
.IR "open file description" ,
an entry in the system-wide table of open files.
-(This object is variously also called an "open file object",
-a "file handle", an "open file table entry",
-or\(emin kernel-developer parlance\(ema
-.IR "struct file" .
-The term "open file description" is used by POSIX.)
The open file description records the file offset and the file status flags
(see below).
A file descriptor is a reference to an open file description;
this reference is unaffected if
.I pathname
is subsequently removed or modified to refer to a different file.
-The new open file description is initially not shared
-with any other process,
-but sharing may arise via
-.BR fork (2).
+For further details on open file descriptions, see NOTES.
.PP
The argument
.I flags
is specified in
.IR flags ,
flag bits other than
-.BR O_DIRECTORY
+.BR O_CLOEXEC ,
+.BR O_DIRECTORY ,
and
.BR O_NOFOLLOW
are ignored.
synchronized I/O
.I file
integrity completion
-(by contrast with contrast with the
+(by contrast with the
synchronized I/O
.I data
integrity completion
on a 32-bit platform without
.I -D_FILE_OFFSET_BITS=64
tried to open a file whose size exceeds
-.I (2<<31)-1
-bits;
+.I (1<<31)-1
+bytes;
see also
.B O_LARGEFILE
above.
flag, its st_ctime and st_mtime fields are set to the current time.
.\"
.\"
+.SS Open file descriptions
+The term open file description is the one used by POSIX to refer to the
+entries in the system-wide table of open files.
+In other contexts, this object is
+variously also called an "open file object",
+a "file handle", an "open file table entry",
+or\(emin kernel-developer parlance\(ema
+.IR "struct file" .
+
+When a file descriptor is duplicated (using
+.BR dup (2)
+or similar),
+the duplicate refers to the same open file description
+as the original file descriptor,
+and the two file descriptors consequently share
+the file offset and file status flags.
+Such sharing can also occur between processes:
+a child process created via
+.BR fork (2)
+inherits duplicates of its parent's file descriptors,
+and those duplicates refer to the same open file descriptions.
+
+Each
+.BR open (2)
+of a file creates a new open file description;
+thus, there may be multiple open file descriptions
+corresponding to a file inode.
+.\"
+.\"
.SS Synchronized I/O
The POSIX.1-2008 "synchronized I/O" option
specifies different variants of synchronized I/O,
that are required for applications that don't need the guarantees
of file integrity completion.
-To understand the difference between the the two types of completion,
+To understand the difference between the two types of completion,
consider two pieces of file metadata:
the file last modification timestamp
.RI ( st_mtime )
.BR mmap (2)
of files with direct I/O to the same files.
.LP
-The behaviour of
+The behavior of
.B O_DIRECT
with NFS will differ from local filesystems.
Older kernels, or
.BR path_resolution (7),
.BR symlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH OPEN_BY_HANDLE_AT 2 2014-05-08 "Linux" "Linux Programmer's Manual"
+.TH OPEN_BY_HANDLE_AT 2 2014-06-13 "Linux" "Linux Programmer's Manual"
.SH NAME
name_to_handle_at, open_by_handle_at \- obtain handle
for a pathname and open file via a handle
.SH SYNOPSIS
.nf
-.B #define _GNU_SOURCE
+.BR "#define _GNU_SOURCE" " /* See feature_test_macros(7) */"
.B #include <sys/types.h>
.B #include <sys/stat.h>
.B #include <fcntl.h>
.IR dirfd ,
and a handle is returned for the file to which it refers.
(See
-.BR openat (3)
+.BR openat (2)
for an explanation of why "directory file descriptors" are useful.)
.IP *
If
.UR https://www.kernel.org/pub/linux/utils/util-linux/
.UE
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ioperm (2),
.BR iopl (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR signal (2),
.BR sigsuspend (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR capabilities (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" This document is based on the perf_event.h header file, the
.\" tools/perf/design.txt file, and a lot of bitter experience.
.\"
-.TH PERF_EVENT_OPEN 2 2014-04-17 "Linux" "Linux Programmer's Manual"
+.TH PERF_EVENT_OPEN 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
perf_event_open \- set up performance monitoring
.SH SYNOPSIS
.BR execve (2).
.TP
.BR PERF_FLAG_FD_NO_GROUP
-.\" FIXME The following sentence is unclear
+.\" FIXME . The following sentence is unclear
This flag allows creating an event as part of an event group but
having no group leader.
It is unclear why this is useful.
-.\" FIXME So, why is it useful?
+.\" FIXME . So, why is it useful?
.TP
.BR PERF_FLAG_FD_OUTPUT
This flag reroutes the output from an event to the group leader.
/* exclude kernel callchains */
exclude_callchain_user : 1,
/* exclude user callchains */
- __reserved_1 : 41;
+ mmap2 : 1, /* include mmap with inode data */
+ comm_exec : 1, /* flag comm events that are due to exec */
+ __reserved_1 : 39;
union {
__u32 wakeup_events; /* wakeup every n events */
.BR exec (2)
and
.BR prctl (PR_SET_NAME)
-system calls.
-Unfortunately for tools,
-there is no way to distinguish one system call versus the other.
+system calls as well as writing to
+.IR /proc/self/comm .
+If the
+.I comm_exec
+flag is also successfully set (possible since Linux 3.16),
+then the misc flag
+.B PERF_RECORD_MISC_COMM_EXEC
+can be used to differentiate the
+.BR exec (2)
+case from the others.
.TP
.IR "freq"
If this bit is set, then
.IR "exclude_callchain_user" " (since Linux 3.7)"
Do not include user callchains.
.TP
+.IR "mmap2" " (since Linux 3.16)"
+Generate an extended executable mmap record that contains enough
+additional information to uniquely identify shared mappings.
+The
+.I mmap
+flag must also be set for this to work.
+.TP
+.IR "comm_exec" " (since Linux 3.16)"
+This is purely a feature-detection flag, it does not change
+kernel behavior.
+If this flag can successfully be set, then, when
+.I comm
+is enabled, the
+.B PERF_RECORD_MISC_COMM_EXEC
+flag will be set in the
+.I misc
+field of a comm record header if the rename event being
+reported was caused by a call to
+.BR exec (2).
+This allows tools to distinguish between the various
+types of process renaming.
+.TP
.IR "wakeup_events" ", " "wakeup_watermark"
This union sets how many samples
.RI ( wakeup_events )
.B PERF_SAMPLE_BRANCH_IND_CALL
Indirect calls.
.TP
+.BR PERF_SAMPLE_BRANCH_COND " (since Linux 3.16)"
+Conditional branches.
+.TP
.BR PERF_SAMPLE_BRANCH_ABORT_TX " (since Linux 3.11)"
Transactional memory aborts.
.TP
This is set when the mapping is not executable;
otherwise the mapping is executable.
.TP
+.B PERF_RECORD_MISC_COMM_EXEC
+This is set for a
+.B PERF_RECORD_COMM
+record on kernels more recent than Linux 3.16
+if a process name change was caused by an
+.BR exec (2)
+system call.
+It is an alias for
+.B PERF_RECORD_MISC_MMAP_DATA
+since the two values would not be set in the same record.
+.TP
.B PERF_RECORD_MISC_EXACT_IP
This indicates that the content of
.B PERF_SAMPLE_IP
};
.fi
.in
+.RS
+.TP
+.I pid
+is the process ID.
+.TP
+.I tid
+is the thread ID.
+.TP
+.I addr
+is the address of the allocated memory.
+.I len
+is the length of the allocated memory.
+.I pgoff
+is the page offset of the allocated memory.
+.I filename
+is a string describing the backing of the allocated memory.
+.RE
.TP
.B PERF_RECORD_LOST
This record indicates when events are lost.
.nf
struct {
struct perf_event_header header;
- u32 pid, tid;
+ u32 pid;
+ u32 tid;
char comm[];
struct sample_id sample_id;
};
.fi
.in
+.RS
+.TP
+.I pid
+is the process ID.
+.TP
+.I tid
+is the thread ID.
+.TP
+.I comm
+is a string containing the new name of the process.
+.RE
.TP
.B PERF_RECORD_EXIT
This record indicates a process exit event.
.IR size ", " data[size] ", " dyn_size
If
.B PERF_SAMPLE_STACK_USER
-is enabled, then record the user stack to enable backtracing.
+is enabled, then the user stack is recorded.
+This can be used to generate stack backtraces.
.I size
is the size requested by the user in
-.I stack_user_size
+.I sample_stack_user
or else the maximum record size.
.I data
-is the stack data.
+is the stack data (a raw dump of the memory pointed to by the
+stack pointer at the time of sampling).
.I dyn_size
is the amount of data actually dumped (can be less than
.IR size ).
.PD
.TP
.I mem_lvl
-Memory hierarchy level hit or miss, a bitwise combination of:
+Memory hierarchy level hit or miss, a bitwise combination of
+the following, shifted left by
+.BR PERF_MEM_LVL_SHIFT :
.PD 0
.RS
.PD
.TP
.I mem_snoop
-Snoop mode, a bitwise combination of:
+Snoop mode, a bitwise combination of the following, shifted left by
+.BR PERF_MEM_SNOOP_SHIFT :
.PD 0
.RS
.PD
.TP
.I mem_lock
-Lock instruction, a bitwise combination of:
+Lock instruction, a bitwise combination of the following, shifted left by
+.BR PERF_MEM_LOCK_SHIFT :
.PD 0
.RS
.PD
.TP
.I mem_dtlb
-TLB access hit or miss, a bitwise combination of:
+TLB access hit or miss, a bitwise combination of the following, shifted
+left by
+.BR PERF_MEM_TLB_SHIFT :
.PD 0
.RS
and masking with
.BR PERF_TXN_ABORT_MASK .
.RE
+.TP
+.B PERF_RECORD_MMAP2
+This record includes extended information on
+.BR mmap (2)
+calls returning executable mappings.
+The format is similar to that of the
+.B PERF_RECORD_MMAP
+record, but includes extra values that allow uniquely identifying
+shared mappings.
+
+.in +4n
+.nf
+struct {
+ struct perf_event_header header;
+ u32 pid;
+ u32 tid;
+ u64 addr;
+ u64 len;
+ u64 pgoff;
+ u32 maj;
+ u32 min;
+ u64 ino;
+ u64 ino_generation;
+ u32 prot;
+ u32 flags;
+ char filename[];
+ struct sample_id sample_id;
+};
+.fi
+.RS
+.TP
+.I pid
+is the process ID.
+.TP
+.I tid
+is the thread ID.
+.TP
+.I addr
+is the address of the allocated memory.
+.TP
+.I len
+is the length of the allocated memory.
+.TP
+.I pgoff
+is the page offset of the allocated memory.
+.TP
+.I maj
+is the major ID of the underlying device.
+.TP
+.I min
+is the minor ID of the underlying device.
+.TP
+.I ino
+is the inode number.
+.TP
+.I ino_generation
+is the inode generation.
+.TP
+.I prot
+is the protection information.
+.TP
+.I flags
+is the flags information.
+.TP
+.I filename
+is a string describing the backing of the allocated memory.
+.RE
.RE
.SS Signal overflow
Events can be set to deliver a signal when a threshold is crossed.
+.\" FIXME .
+.\" The following sentence doesn't seem to make sense.
+.\" These system calls do not set up signal handlers.
The signal handler is set up using the
.BR poll (2),
.BR select (2),
and
the underlying event is disabled.
-Note: on newer kernels (definitely noticed with 3.2)
-.\" FIXME(Vince) : Find out when this was introduced
+Note: on newer kernels (since at least as early as Linux 3.2),
+.\" FIXME . Find out when this was introduced
a signal is provided for every overflow, even if
.I wakeup_events
is not set.
.BR prctl (2),
.BR read (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
The perfmon2 interface specification
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
is Linux-specific and should not be used in programs intended to
be portable.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" to EXAMPLE text.
.\" 2008-10-10, mtk: add description of pipe2()
.\"
-.TH PIPE 2 2014-02-11 "Linux" "Linux Programmer's Manual"
+.TH PIPE 2 2014-07-08 "Linux" "Linux Programmer's Manual"
.SH NAME
pipe, pipe2 \- create pipe
.SH SYNOPSIS
bytes (see
.BR pipe (7))
will be split into multiple packets.
+The constant
+.BR PIPE_BUF
+is defined in
+.IR <limits.h> .
.IP *
If a
.BR read (2)
.BR popen (3),
.BR pipe (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR initrd (4),
.BR pivot_root (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2006-07-01, mtk, Added POLLRDHUP + various other wording and
.\" formatting changes.
.\"
-.TH POLL 2 2014-05-10 "Linux" "Linux Programmer's Manual"
+.TH POLL 2 2014-09-06 "Linux" "Linux Programmer's Manual"
.SH NAME
poll, ppoll \- wait for some event on a file descriptor
.SH SYNOPSIS
.BR poll ()
call: simply negate the
.I fd
-field.)
+field.
+Note, however, that this technique can't be used to ignore file descriptor 0.)
The field
.I events
pseudoterminal master in packet mode has seen state change in slave).
.TP
.B POLLOUT
-Writing now will not block.
+Writing is now possible, though a write larger that the available space
+in a socket or pipe will still block (unless
+.B O_NONBLOCK
+is set).
.TP
.BR POLLRDHUP " (since Linux 2.6.17)"
Stream socket peer closed connection,
.BR poll ()
is closed in another thread, see
.BR select (2).
-.SS Linux notes
+.SS C library/kernel ABI differences
The Linux
.BR ppoll ()
system call modifies its
function does not modify its
.I timeout_ts
argument.
+
+The raw
+.BR ppoll ()
+system call has a fifth argument,
+.IR "size_t sigsetsize" ,
+which specifies the size in bytes of the
+.IR sigmask
+argument.
+The glibc
+.BR ppoll ()
+wrapper function specifies this argument as a fixed value
+(equal to
+.IR sizeof(sigset_t) ).
.SH BUGS
See the discussion of spurious readiness notifications under the
BUGS section of
.BR select_tut (2),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR posix_madvise (3)
.\" FIXME . Write a posix_fadvise(3) page.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR signal (2),
.BR core (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH BUGS
POSIX requires that opening a file with the
.BR O_APPEND
-flag should have no affect on the location at which
+flag should have no effect on the location at which
.BR pwrite ()
writes data.
However, on Linux, if a file is opened with
-.\" FIXME https://bugzilla.kernel.org/show_bug.cgi?id=43178
+.\" FIXME . https://bugzilla.kernel.org/show_bug.cgi?id=43178
.BR O_APPEND ,
.BR pwrite ()
appends data to the end of the file, regardless of the value of
.BR readv (2),
.BR write (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\" Commit fcf634098c00dd9cd247447368495f0b79be12d1
.\"
-.TH PROCESS_VM_READV 2 2014-05-05 "Linux" "Linux Programmer's Manual"
+.TH PROCESS_VM_READV 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
process_vm_readv, process_vm_writev \- transfer data between process address spaces
.SH SYNOPSIS
local[1].iov_base = buf2;
local[1].iov_len = 10;
remote[0].iov_base = (void *) 0x10000;
- remote[1].iov_len = 20;
+ remote[0].iov_len = 20;
nread = process_vm_readv(pid, local, 2, remote, 1, 0);
if (nread != 20)
.BR readv (2),
.BR writev (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" (Thanks to Blaisorblade, Daniel Jacobowitz and others who helped.)
.\" 2011-09, major update by Denys Vlasenko <vda.linux@googlemail.com>
.\"
-.TH PTRACE 2 2014-02-20 "Linux" "Linux Programmer's Manual"
+.TH PTRACE 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
ptrace \- process trace
.SH SYNOPSIS
As for
.BR PTRACE_POKEUSER ,
some general-purpose register modifications may be disallowed.
-.\" FIXME In the preceding sentence, which modifications are disallowed,
+.\" FIXME . In the preceding sentence, which modifications are disallowed,
.\" and when they are disallowed, how does user space discover that fact?
.RI ( addr
is ignored.)
/* r can still be 0 here! */
}
.fi
-.\" FIXME:
+.\" FIXME .
.\" waitid usage? WNOWAIT?
.\" describe how wait notifications queue (or not queue)
.LP
.SS PTRACE_SINGLESTEP, PTRACE_SYSEMU, PTRACE_SYSEMU_SINGLESTEP stops
[Details of these kinds of stops are yet to be documented.]
.\"
-.\" FIXME
+.\" FIXME .
.\" document stops occurring with PTRACE_SINGLESTEP, PTRACE_SYSEMU,
.\" PTRACE_SYSEMU_SINGLESTEP
.SS Informational and restarting ptrace commands
.B SIGSTOP
may be lost.
.\"
-.\" FIXME: Describe how to attach to a thread which is already
-.\" group-stopped.
+.\" FIXME . Describe how to attach to a thread which is already group-stopped.
.LP
Since attaching sends
.B SIGSTOP
the tracee is not already ptrace-stopped,
because no signal delivery happens while it is\(emnot even
.BR SIGSTOP .
-.\" FIXME: Describe how to detach from a group-stopped tracee so that it
+.\" FIXME . Describe how to detach from a group-stopped tracee so that it
.\" doesn't run, but continues to wait for SIGCONT.
.LP
If the tracer dies, all tracees are automatically detached and restarted,
set-user-ID/set-group-ID programs, for obvious reasons.
Alternatively, the process may already be being traced,
or (on kernels before 2.6.26) be
-.BR init (8)
+.BR init (1)
(PID 1).
.TP
.B ESRCH
or
.IR "(void\ *)\ 0".
.LP
-At the system call level, the
-.BR PTRACE_PEEKTEXT ,
-.BR PTRACE_PEEKDATA ,
-and
-.BR PTRACE_PEEKUSER
-requests have a different API: they store the result
-at the address specified by the
-.I data
-parameter, and the return value is the error flag.
-The glibc wrapper function provides the API given in DESCRIPTION above,
-with the result being returned via the function return value.
-.LP
In Linux kernels before 2.6.26,
.\" See commit 00cd5c37afd5f431ac186dd131705048c0a11fdb
-.BR init (8),
+.BR init (1),
the process with PID 1, may not be traced.
.LP
The layout of the contents of memory and the USER area are
In any case, use of
.BR ptrace ()
is highly specific to the operating system and architecture.
+.SS C library/kernel ABI differences
+At the system call level, the
+.BR PTRACE_PEEKTEXT ,
+.BR PTRACE_PEEKDATA ,
+and
+.BR PTRACE_PEEKUSER
+requests have a different API: they store the result
+at the address specified by the
+.I data
+parameter, and the return value is the error flag.
+The glibc wrapper function provides the API given in DESCRIPTION above,
+with the result being returned via the function return value.
.SH BUGS
On hosts with 2.6 kernel headers,
.B PTRACE_SETOPTIONS
.B PTRACE_DETACH
the thread group leader instead of restarting it in this case.
Last confirmed on 2.6.38.6.
-.\" FIXME: ^^^ need to test/verify this scenario
+.\" FIXME . need to test/verify this scenario
.LP
A
.B SIGKILL
.BR capabilities (7),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR lsmod (8),
.BR modinfo (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR quotacheck (8),
.BR quotaon (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR write (2),
.BR fread (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR posix_fadvise (2),
.BR read (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getdents (2),
.BR readdir (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2011-09-20, Guillem Jover <guillem@hadrons.org>:
.\" Added text on dynamically allocating buffer + example program
.\"
-.TH READLINK 2 2014-05-10 "Linux" "Linux Programmer's Manual"
+.TH READLINK 2 2014-10-15 "Linux" "Linux Programmer's Manual"
.SH NAME
readlink, readlinkat \- read value of a symbolic link
.SH SYNOPSIS
.\" commit 65cfc6722361570bfe255698d9cd4dccaf47570d
.I pathname
can be an empty string,
-in which case the call operates on the file referred to by
+in which case the call operates on the symbolic link referred to by
.IR dirfd
-(which may have been obtained using the
+(which should have have been obtained using
.BR open (2)
+with the
.B O_PATH
-flag).
-In this case,
-.I dirfd
-can refer to any type of file, not just a directory.
+and
+.B O_NOFOLLOW
+flags).
.PP
See
.BR openat (2)
for the buffer size,
as this constant is not guaranteed to be defined per POSIX
if the system does not have such limit.
+.SS Glibc notes
+On older kernels where
+.BR readlinkat ()
+is unavailable, the glibc wrapper function falls back to the use of
+.BR readlink ().
+When
+.I pathname
+is a relative pathname,
+glibc constructs a pathname based on the symbolic link in
+.IR /proc/self/fd
+that corresponds to the
+.IR dirfd
+argument.
.SH EXAMPLE
The following program allocates the buffer needed by
.BR readlink ()
printf("\(aq%s\(aq points to \(aq%s\(aq\\n", argv[1], linkname);
+ free(linkname);
+
exit(EXIT_SUCCESS);
}
.fi
.BR lstat (2),
.BR stat (2),
.BR symlink (2),
+.BR realpath (3),
.BR path_resolution (7),
.BR symlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" add more details.
.\" 2010-11-16, mtk, Added documentation of preadv() and pwritev()
.\"
-.TH READV 2 2010-11-17 "Linux" "Linux Programmer's Manual"
+.TH READV 2 2014-10-15 "Linux" "Linux Programmer's Manual"
.SH NAME
readv, writev, preadv, pwritev \- read or write data into multiple buffers
.SH SYNOPSIS
.BR readv (),
.BR writev ():
4.4BSD (these system calls first appeared in 4.2BSD), POSIX.1-2001.
-Linux libc5 used \fIsize_t\fP as the type of the \fIiovcnt\fP argument,
-and \fIint\fP as the return type.
+.\" Linux libc5 used \fIsize_t\fP as the type of the \fIiovcnt\fP argument,
+.\" and \fIint\fP as the return type.
.\" The readv/writev system calls were buggy before Linux 1.3.40.
.\" (Says release.libc.)
.BR pwritev ():
nonstandard, but present also on the modern BSDs.
.SH NOTES
-.SS Linux notes
+.SS C library/kernel ABI differences
POSIX.1-2001 allows an implementation to place a limit on
the number of items that can be passed in
.IR iov .
they detect that the underlying kernel system call failed because this
limit was exceeded.
In the case of
-.BR readv ().
+.BR readv (),
the wrapper function allocates a temporary buffer large enough
for all of the items specified by
.IR iov ,
.BR writev ()
performs the analogous task using a temporary buffer and a call to
.BR write (2).
+
+The raw
+.BR preadv ()
+and
+.BR pwritev ()
+system calls have call signatures that differ slightly from that of the
+corresponding GNU C library wrapper functions shown in the SYNOPSIS.
+The final argument,
+.IR offset ,
+is unpacked by the wrapper functions into two arguments in the system calls:
+
+.BI " unsigned long " pos_l ", unsigned long " pos
+
+These arguments contain, respectively, the low order and high order 32 bits of
+.IR offset .
.SH BUGS
It is not advisable to mix calls to
.BR readv ()
.BR read (2),
.BR write (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified, 27 May 2004, Michael Kerrisk <mtk.manpages@gmail.com>
.\" Added notes on capability requirements
.\"
-.TH REBOOT 2 2013-12-28 "Linux" "Linux Programmer's Manual"
+.TH REBOOT 2 2014-09-21 "Linux" "Linux Programmer's Manual"
.SH NAME
reboot \- reboot or enable/disable Ctrl-Alt-Del
.SH SYNOPSIS
and since 2.5.71 also
.B LINUX_REBOOT_MAGIC2C
(that is, 537993216)
-are permitted as value for
+are permitted as values for
.IR magic2 .
(The hexadecimal values of these constants are meaningful.)
The
anything at present (2.1.122), but the type of reboot can be
determined by kernel command-line arguments ("reboot=...") to be
either warm or cold, and either hard or through the BIOS.
+.SS Behavior inside PID namespaces
+.\" commit cf3f89214ef6a33fad60856bc5ffd7bb2fc4709b
+.\" see also commit 923c7538236564c46ee80c253a416705321f13e3
+Since Linux 3.4, when
+.BR reboot ()
+is called from a PID namespace (see
+.BR pid_namespaces (7))
+other than the initial PID namespace,
+the effect of the call is to send a signal to the namespace "init" process.
+.BR LINUX_REBOOT_CMD_RESTART
+and
+.BR LINUX_REBOOT_CMD_RESTART2
+cause a
+.BR SIGHUP
+signal to be sent.
+.BR LINUX_REBOOT_CMD_POWER_OFF
+and
+.BR LINUX_REBOOT_CMD_HALT
+cause a
+.B SIGINT
+signal to be sent.
.SH RETURN VALUE
For the values of
.I cmd
.BR halt (8),
.BR reboot (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 1998,1999 by Andi Kleen
.\" 2001-06-19 corrected SO_EE_OFFENDER, bug report by James Hawtin
.\"
-.TH RECV 2 2014-05-10 "Linux" "Linux Programmer's Manual"
+.TH RECV 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
recv, recvfrom, recvmsg \- receive a message from a socket
.SH SYNOPSIS
If the caller is not interested in the source address,
.I src_addr
-should be specified as NULL and
+and
.I addrlen
-should be specified as 0.
+should be specified as NULL.
.\"
.SS recv()
The
.B MSG_WAITALL
flags.
.SH NOTES
-The prototypes given above follow glibc2.
-The Single UNIX Specification agrees, except that it has return values
-of type \fIssize_t\fP (while 4.x BSD and libc4 and libc5 all have \fIint\fP).
-The
-.I flags
-argument is \fIint\fP in 4.x BSD, but \fIunsigned int\fP in libc4 and libc5.
The
-.I len
-argument is \fIint\fP in 4.x BSD, but \fIsize_t\fP in libc4 and libc5.
-The
-.I addrlen
-argument is \fIint\ *\fP in 4.x BSD, libc4 and libc5.
-The present \fIsocklen_t\ *\fP was invented by POSIX.
+.I socklen_t
+type was invented by POSIX.
See also
.BR accept (2).
.BR sockatmark (3),
.BR socket (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Author: Arnaldo Carvalho de Melo <acme@redhat.com>
.\" Date: Mon Oct 12 23:40:10 2009 -0700
.\"
-.TH RECVMMSG 2 2014-05-21 "Linux" "Linux Programmer's Manual"
+.TH RECVMMSG 2 2014-06-13 "Linux" "Linux Programmer's Manual"
.SH NAME
recvmmsg \- receive multiple messages on a socket
.SH SYNOPSIS
.nf
-.B "#define _GNU_SOURCE"
+.B "#define _GNU_SOURCE" " /* See feature_test_macros(7) */"
.BI "#include <sys/socket.h>"
.BI "int recvmmsg(int " sockfd ", struct mmsghdr *" msgvec \
The
.I timeout
argument does not work as intended.
-.\" FIXME https://bugzilla.kernel.org/show_bug.cgi?id=75371
+.\" FIXME . https://bugzilla.kernel.org/show_bug.cgi?id=75371
.\" http://thread.gmane.org/gmane.linux.man/5677
The timeout is checked only after the receipt of each datagram,
so that if up to
.BR socket (2),
.BR socket (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BI " size_t " pgoff ", int " flags );
.fi
.SH DESCRIPTION
+.BR Note :
+.\" commit 33041a0d76d3c3e0aff28ac95a2ffdedf1282dbc
+.\" http://lwn.net/Articles/597632/
+this system call is (since Linux 3.16) deprecated and will
+eventually be replaced by a slower in-kernel emulation.
+Those few applications that use this system call should
+consider migrating to alternatives.
+
The
.BR remap_file_pages ()
system call is used to create a nonlinear mapping, that is, a mapping
.BR mremap (2),
.BR msync (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR attr (5),
.BR symlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified Thu Mar 3 09:49:35 2005 by Michael Haardt <michael@moria.de>
.\" 2007-03-25, mtk, added various text to DESCRIPTION.
.\"
-.TH RENAME 2 2014-05-08 "Linux" "Linux Programmer's Manual"
+.TH RENAME 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
rename, renameat, renameat2 \- change the name or location of a file
.SH SYNOPSIS
.TP
Before glibc 2.10:
_ATFILE_SOURCE
-.\" FIXME need to define FTMs for renameat2(), once it hits glibc
+.\" FIXME . need to define FTMs for renameat2(), once it hits glibc
.RE
.ad
.PD
refers to a symbolic link, the link is renamed; if
.I newpath
refers to a symbolic link, the link will be overwritten.
-.SS renameat ()
+.SS renameat()
The
.BR renameat ()
system call operates in exactly the same way as
.BR renameat2 ()
was added to Linux in kernel 3.15.
-.\" FIXME glibc support is pending.
+.\" FIXME . glibc support is pending.
.SH CONFORMING TO
.BR rename ():
4.3BSD, C89, C99, POSIX.1-2001, POSIX.1-2008.
.BR renameat ():
POSIX.1-2008.
-.BR renameat2()
+.BR renameat2 ()
is Linux-specific.
+.SH NOTES
+.SS Glibc notes
+On older kernels where
+.BR renameat ()
+is unavailable, the glibc wrapper function falls back to the use of
+.BR rename ().
+When
+.I oldpath
+and
+.I newpath
+are relative pathnames,
+glibc constructs pathnames based on the symbolic links in
+.IR /proc/self/fd
+that correspond to the
+.I olddirfd
+and
+.IR newdirfd
+arguments.
.SH BUGS
On NFS filesystems, you can not assume that if the operation
failed, the file was not renamed.
.BR path_resolution (7),
.BR symlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR keyctl (2),
.BR request-key (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
it appears as though that system call executed and
returned in the usual fashion.
.\"
-.\" FIXME
+.\" FIXME .
.\" There is one oddness in the implementation though, with respect to
.\" nanosleep() (and probably also clock_nanosleep()). The scenario
.\" is as follows:
.BR sigaction (2),
.BR sigreturn (2),
.BR signal (7)
-.\" FIXME select(2) should probably get the restart_syscall() treatment:
+.\" FIXME . select(2) should probably get the restart_syscall() treatment:
.\" If a select() call is suspended by stop-sig+SIGCONT, the time
.\" spent suspended is *not* deducted when the select() is restarted.
-.\" FIXME: check whether recvmmsg() handles stop-sig+SIGCONT properly.
+.\" FIXME . check whether recvmmsg() handles stop-sig+SIGCONT properly.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR unlink (2),
.BR unlinkat (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sigqueue (3),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR syscall (2),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sched_setscheduler (2),
.BR sched (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR sched (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2008-11-12, mtk, removed CPU_*() macro descriptions to a
.\" separate CPU_SET(3) page.
.\"
-.TH SCHED_SETAFFINITY 2 2014-05-10 "Linux" "Linux Programmer's Manual"
+.TH SCHED_SETAFFINITY 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
sched_setaffinity, sched_getaffinity \- \
set and get a thread's CPU affinity mask
inherits its parent's CPU affinity mask.
The affinity mask is preserved across an
.BR execve (2).
-
+.SS C library/kernel ABI differences
This manual page describes the glibc interface for the CPU affinity calls.
The actual system call interface is slightly different, with the
.I mask
.BR cpuset (7),
.BR sched (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH SCHED_SETATTR 2 2014-05-13 "Linux" "Linux Programmer's Manual"
+.TH SCHED_SETATTR 2 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
sched_setattr, sched_getattr \-
set and get scheduling policy and attributes
.BI "int sched_getattr(pid_t " pid ", const struct sched_attr *" attr ,
.BI " unsigned int " size ", unsigned int " flags );
.fi
-.\" FIXME Add feature test macro requirements
+.\" FIXME . Add feature test macro requirements
.SH DESCRIPTION
.SS sched_setattr()
The
.BR sched_setaffinity (2)).
.SH VERSIONS
These system calls first appeared in Linux 3.14.
-.\" FIXME Add glibc version
+.\" FIXME . Add glibc version
.SH CONFORMING TO
These system calls are nonstandard Linux extensions.
.SH NOTES
.BR getpriority (2).
.SH BUGS
In Linux versions up to
-.\" FIXME patch sent to Peter Zijlstra
+.\" FIXME . patch sent to Peter Zijlstra
3.15,
.BR sched_settattr ()
failed with the error
.BR E2BIG
for the case described in ERRORS.
.\" In Linux versions up to up 3.15,
-.\" .\" FIXME patch from Peter Zijlstra pending
+.\" FIXME . patch from Peter Zijlstra pending
.\" .BR sched_setattr ()
.\" allowed a negative
.\" .I attr.sched_policy
.SH SEE ALSO
.ad l
.nh
+.BR chrt (1),
.BR nice (2),
.BR sched_get_priority_max (2),
.BR sched_get_priority_min (2),
.BR sched (7)
.ad
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR capabilities (7),
.BR sched (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" %%%LICENSE_END
.\"
.\"
-.TH SCHED_SETSCHEDULER 2 2014-05-21 "Linux" "Linux Programmer's Manual"
+.TH SCHED_SETSCHEDULER 2 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
sched_setscheduler, sched_getscheduler \-
set and get scheduling policy/parameters
.SH SEE ALSO
.ad l
.nh
+.BR chrt (1),
.BR nice (2),
.BR sched_get_priority_max (2),
.BR sched_get_priority_min (2),
.BR sched (7)
.ad
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR sched (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2005-03-11, mtk, modified pselect() text (it is now a system
.\" call in 2.6.16.
.\"
-.TH SELECT 2 2014-01-31 "Linux" "Linux Programmer's Manual"
+.TH SELECT 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
select, pselect, FD_CLR, FD_ISSET, FD_SET, FD_ZERO \-
synchronous I/O multiplexing
waiting until one or more of the file descriptors become "ready"
for some class of I/O operation (e.g., input possible).
A file descriptor is considered ready if it is possible to
-perform the corresponding I/O operation (e.g.,
-.BR read (2))
-without blocking.
+perform a corresponding I/O operation (e.g.,
+.BR read (2)
+without blocking, or a sufficiently small
+.BR write (2)).
.PP
The operation of
.BR select ()
block; in particular, a file descriptor is also ready on end-of-file),
those in
.I writefds
-will be watched to see if a write will not block, and
-those in
+will be watched to see if space is available for write (though a large
+write may still block), and those in
.I exceptfds
will be watched for exceptions.
On exit, the sets are modified in place
and
.BR pselect ().
-Libc4 and libc5 do not have a
+Under glibc 2.0,
.I <sys/select.h>
-header; under glibc 2.0 and later this header exists.
-Under glibc 2.0 it unconditionally gives the wrong prototype for
+gives the wrong prototype for
.BR pselect ().
-Under glibc 2.1 to 2.2.1 it gives
+Under glibc 2.1 to 2.2.1, it gives
.BR pselect ()
when
.B _GNU_SOURCE
is defined.
-Since glibc 2.2.2 the requirements are as shown in the SYNOPSIS.
+Since glibc 2.2.2, the requirements are as shown in the SYNOPSIS.
.SS Multithreaded applications
If a file descriptor being monitored by
.BR select ()
.BR select ().
In summary, any application that relies on a particular behavior
in this scenario must be considered buggy.
-.SS Linux notes
+.\"
+.SS C library/kernel ABI differences
The
.BR pselect ()
interface described in this page is implemented by glibc.
For a tutorial with discussion and examples, see
.BR select_tut (2).
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" .SH AUTHORS
.\" This man page was written by Paul Sheer.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sem_overview (7),
.BR svipc (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sem_overview (7),
.BR svipc (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2005-04-08, mtk, Noted kernel version numbers for semtimedop()
.\" 2007-07-09, mtk, Added an EXAMPLE code segment.
.\"
-.TH SEMOP 2 2014-05-10 "Linux" "Linux Programmer's Manual"
+.TH SEMOP 2 2014-09-21 "Linux" "Linux Programmer's Manual"
.SH NAME
semop, semtimedop \- System V semaphore operations
.SH SYNOPSIS
the corresponding
.I semadj
values in all processes are cleared.
-.PP
+The
+.BR clone ()
+.B CLONE_SYSVSEM
+flag allows more than one process to share a
+.I semadj
+list; see
+.BR clone (2)
+for details.
+
The \fIsemval\fP, \fIsempid\fP, \fIsemzcnt\fP, and \fIsemnct\fP values
for a semaphore can all be retrieved using appropriate
.BR semctl (2)
.BR svipc (7),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified Oct 2003 by aeb
.\" Modified 2004-07-01 by mtk
.\"
-.TH SEND 2 2014-05-10 "Linux" "Linux Programmer's Manual"
+.TH SEND 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
send, sendto, sendmsg \- send a message on a socket
.SH SYNOPSIS
.I flags
argument is the bitwise OR
of zero or more of the following flags.
-.\" FIXME ? document MSG_PROXY (which went away in 2.3.15)
+.\" FIXME . ? document MSG_PROXY (which went away in 2.3.15)
.TP
.BR MSG_CONFIRM " (since Linux 2.3.15)"
Tell the link layer that forward progress happened: you got a successful
field is used on an unconnected socket to specify the target
address for a datagram.
It points to a buffer containing the address; the
-.I msg_name
+.I msg_namelen
field should be set to the size of the address.
For a connected socket, these fields should be specified as NULL and 0,
respectively.
.B MSG_CONFIRM
flag is a Linux extension.
.SH NOTES
-The prototypes given above follow the Single UNIX Specification,
-as glibc2 also does; the
-.I flags
-argument was \fIint\fP in 4.x BSD, but \fIunsigned int\fP in libc4 and libc5;
-the
-.I len
-argument was \fIint\fP in 4.x BSD and libc4, but \fIsize_t\fP in libc5;
-the
-.I addrlen
-argument was \fIint\fP in 4.x BSD and libc4 and libc5.
-See also
-.BR accept (2).
-
According to POSIX.1-2001, the
.I msg_controllen
field of the
.BR tcp (7),
.BR udp (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR splice (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH SENDMMSG 2 2012-12-16 "Linux" "Linux Programmer's Manual"
+.TH SENDMMSG 2 2014-07-08 "Linux" "Linux Programmer's Manual"
.SH NAME
sendmmsg \- send multiple messages on a socket
.SH SYNOPSIS
.nf
-.B "#define _GNU_SOURCE"
+.B "#define _GNU_SOURCE" " /* See feature_test_macros(7) */"
.BI "#include <sys/socket.h>"
.BI "int sendmmsg(int " sockfd ", struct mmsghdr *" msgvec \
.\" must retry starting at the first failed one and if the problem is
.\" persistent the error will be returned.
.\"
-.\" This matches the behaviour of other syscalls like read/write - it
+.\" This matches the behavior of other syscalls like read/write - it
.\" is not an error if less than the requested number of elements are sent.
.SH VERSIONS
The
.BR socket (2),
.BR socket (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR numa (7),
.BR numactl (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR get_thread_area (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH SET_TID_ADDRESS 2 2012-07-19 "Linux" "Linux Programmer's Manual"
+.TH SET_TID_ADDRESS 2 2014-07-08 "Linux" "Linux Programmer's Manual"
.SH NAME
set_tid_address \- set pointer to thread ID
.SH SYNOPSIS
.BI "long set_tid_address(int *" tidptr );
.fi
.SH DESCRIPTION
-For each process, the kernel maintains two attributes (addresses) called
+For each thread, the kernel maintains two attributes (addresses) called
.I set_child_tid
and
.IR clear_child_tid .
These two attributes contain the value NULL by default.
.TP
.I set_child_tid
-If a process is started using
+If a thread is started using
.BR clone (2)
with the
.B CLONE_CHILD_SETTID
.IP
When
.I set_child_tid
-is set, the very first thing the new process does
-is writing its PID at this address.
+is set, the very first thing the new thread does
+is to write its thread ID at this address.
.TP
.I clear_child_tid
-If a process is started using
+If a thread is started using
.BR clone (2)
with the
.B CLONE_CHILD_CLEARTID
.BR set_tid_address ()
sets the
.I clear_child_tid
-value for the calling process to
+value for the calling thread to
.IR tidptr .
.LP
-When a process whose
+When a thread whose
.I clear_child_tid
is not NULL terminates, then,
-if the process is sharing memory with other processes or threads,
+if the thread is sharing memory with other threads,
then 0 is written at the address specified in
.I clear_child_tid
and the kernel performs the following operation:
futex(clear_child_tid, FUTEX_WAKE, 1, NULL, NULL, 0);
-The effect of this operation is to wake a single process that
+The effect of this operation is to wake a single thread that
is performing a futex wait on the memory location.
Errors from the futex wake operation are ignored.
.SH RETURN VALUE
.BR set_tid_address ()
-always returns the PID of the calling process.
+always returns the caller's thread ID.
.SH ERRORS
.BR set_tid_address ()
always succeeds.
This system call is Linux-specific.
.SH SEE ALSO
.BR clone (2),
-.BR futex (2)
+.BR futex (2),
+.BR gettid (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified, 27 May 2004, Michael Kerrisk <mtk.manpages@gmail.com>
.\" Added notes on capability requirements
.\"
-.TH SETEUID 2 2012-07-02 "Linux" "Linux Programmer's Manual"
+.TH SETEUID 2 2014-09-21 "Linux" "Linux Programmer's Manual"
.SH NAME
seteuid, setegid \- set effective user or group ID
.SH SYNOPSIS
On error, \-1 is returned, and
.I errno
is set appropriately.
+
+.IR Note :
+there are cases where
+.BR seteuid ()
+can fail even when the caller is UID 0;
+it is a grave security error to omit checking for a failure return from
+.BR seteuid ().
.SH ERRORS
-.\" .TP
-.\" .B EINVAL
+.TP
+.B EINVAL
+The target user or group ID is not valid in this user namespace.
.TP
.B EPERM
The calling process is not privileged (Linux: does not have the
On an arbitrary system one should check
.BR _POSIX_SAVED_IDS .
.LP
-Under libc4, libc5 and glibc 2.0
+Under glibc 2.0
.BI seteuid( euid )
is equivalent to
.BI setreuid(\-1, " euid" )
.RI ( egid )
to be the same value as the current effective user (group) ID,
and some implementations do not permit this.
+.SS C library/kernel ABI differences
+On Linux,
+.BR seteuid ()
+and
+.BR setegid ()
+are implemented as library functions that call, respectively,
+.BR setreuid (2)
+and
+.BR setresgid (2).
.SH SEE ALSO
.BR geteuid (2),
.BR setresuid (2),
.BR setreuid (2),
.BR setuid (2),
.BR capabilities (7),
-.BR credentials (7)
+.BR credentials (7),
+.BR user_namespaces (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR capabilities (7),
.BR credentials (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR capabilities (7),
.BR credentials (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 1997-01-31 by Eric S. Raymond <esr@thyrsus.com>
.\" Modified 2002-03-09 by aeb
.\"
-.TH SETGID 2 2010-11-22 "Linux" "Linux Programmer's Manual"
+.TH SETGID 2 2014-09-21 "Linux" "Linux Programmer's Manual"
.SH NAME
setgid \- set group identity
.SH SYNOPSIS
is set appropriately.
.SH ERRORS
.TP
+.B EINVAL
+The group ID specified in
+.I gid
+is not valid in this user namespace.
+.TP
.B EPERM
The calling process is not privileged (does not have the
\fBCAP_SETGID\fP capability), and
.BR setegid (2),
.BR setregid (2),
.BR capabilities (7),
-.BR credentials (7)
+.BR credentials (7),
+.BR user_namespaces (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Licensed under the GPLv2
.\" %%%LICENSE_END
.\"
-.TH SETNS 2 2013-01-01 "Linux" "Linux Programmer's Manual"
+.TH SETNS 2 2014-09-21 "Linux" "Linux Programmer's Manual"
.SH NAME
setns \- reassociate thread with a namespace
.SH SYNOPSIS
argument is a file descriptor referring to one of the namespace entries in a
.I /proc/[pid]/ns/
directory; see
-.BR proc (5)
+.BR namespaces (7)
for further information on
.IR /proc/[pid]/ns/ .
The calling thread will be reassociated with the corresponding namespace,
.BR 0
Allow any type of namespace to be joined.
.TP
-.BR CLONE_NEWIPC
+.BR CLONE_NEWIPC " (since Linux 3.0)"
.I fd
must refer to an IPC namespace.
.TP
-.BR CLONE_NEWNET
+.BR CLONE_NEWNET " (since Linux 3.0)"
.I fd
must refer to a network namespace.
.TP
-.BR CLONE_NEWUTS
+.BR CLONE_NEWNS " (since Linux 3.8)"
+.I fd
+must refer to a mount namespace.
+.TP
+.BR CLONE_NEWPID " (since Linux 3.8)"
+.I fd
+must refer to a PID namespace.
+.TP
+.BR CLONE_NEWUSER " (since Linux 3.8)"
+.I fd
+must refer to a user namespace.
+.TP
+.BR CLONE_NEWUTS " (since Linux 3.0)"
.I fd
must refer to a UTS namespace.
.PP
.IR fd
if the file descriptor was opened by another process and, for example,
passed to the caller via a UNIX domain socket.)
+
+.B CLONE_NEWPID
+behaves somewhat differently from the other
+.I nstype
+values:
+reassociating the calling thread with a PID namespace only changes
+the PID namespace that child processes of the caller will be created in;
+it does not change the PID namespace of the caller itself.
+Reassociating with a PID namespace is only allowed if the
+PID namespace specified by
+.IR fd
+is a descendant (child, grandchild, etc.)
+of the PID namespace of the caller.
+For further details on PID namespaces, see
+.BR pid_namespaces (7).
+
+A process reassociating itself with a user namespace must have the
+.B CAP_SYS_ADMIN
+.\" See kernel/user_namespace.c:userns_install() [3.8 source]
+capability in the target user namespace.
+Upon successfully joining a user namespace,
+a process is granted all capabilities in that namespace,
+regardless of its user and group IDs.
+A multithreaded process may not change user namespace with
+.BR setns ().
+It is not permitted to use
+.BR setns ()
+to reenter the caller's current user namespace.
+This prevents a caller that has dropped capabilities from regaining
+those capabilities via a call to
+.BR setns ().
+For security reasons,
+.\" commit e66eded8309ebf679d3d3c1f5820d1f2ca332c71
+.\" https://lwn.net/Articles/543273/
+a process can't join a new user namespace if it is sharing
+filesystem-related attributes
+(the attributes whose sharing is controlled by the
+.BR clone (2)
+.B CLONE_FS
+flag) with another process.
+For further details on user namespaces, see
+.BR user_namespaces (7).
+
+A process may not be reassociated with a new mount namespace if it is
+multithreaded.
+.\" Above check is in fs/namespace.c:mntns_install() [3.8 source]
+Changing the mount namespace requires that the caller possess both
+.B CAP_SYS_CHROOT
+and
+.BR CAP_SYS_ADMIN
+capabilities in its own user namespace and
+.BR CAP_SYS_ADMIN
+in the target mount namespace.
+See
+.BR user_namespaces (7)
+for details on the interaction of user namespaces and mount namespaces.
.SH RETURN VALUE
On success,
.IR setns ()
.B EINVAL
.I fd
refers to a namespace whose type does not match that specified in
-.IR nstype ,
-or there is problem with reassociating the
+.IR nstype .
+.TP
+.B EINVAL
+There is problem with reassociating
the thread with the specified namespace.
.TP
+.B EINVAL
+The caller attempted to join the user namespace
+in which it is already a member.
+.TP
+.B EINVAL
+.\" commit e66eded8309ebf679d3d3c1f5820d1f2ca332c71
+The caller shares filesystem
+.RB ( CLONE_FS )
+state (in particular, the root directory)
+with other processes and tried to join a new user namespace.
+.TP
+.B EINVAL
+.\" See kernel/user_namespace.c::userns_install() [kernel 3.15 sources]
+The caller is multithreaded and tried to join a new user namespace.
+.TP
.B ENOMEM
Cannot allocate sufficient memory to change the specified namespace.
.TP
.B EPERM
-The calling thread did not have the required privilege
-.RB ( CAP_SYS_ADMIN )
+The calling thread did not have the required capability
for this operation.
.SH VERSIONS
The
exit(EXIT_FAILURE);
}
- fd = open(argv[1], O_RDONLY); /* Get descriptor for namespace */
+ fd = open(argv[1], O_RDONLY); /* Get descriptor for namespace */
if (fd == \-1)
errExit("open");
- if (setns(fd, 0) == \-1) /* Join that namespace */
+ if (setns(fd, 0) == \-1) /* Join that namespace */
errExit("setns");
- execvp(argv[2], &argv[2]); /* Execute a command in namespace */
+ execvp(argv[2], &argv[2]); /* Execute a command in namespace */
errExit("execvp");
}
.fi
.SH SEE ALSO
.BR clone (2),
.BR fork (2),
+.BR unshare (2),
.BR vfork (2),
-.BR proc (5),
+.BR namespaces (7),
.BR unix (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR termios (3),
.BR credentials (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" %%%LICENSE_END
.\"
.\" Modified, 2003-05-26, Michael Kerrisk, <mtk.manpages@gmail.com>
-.TH SETRESUID 2 2010-11-22 "Linux" "Linux Programmer's Manual"
+.TH SETRESUID 2 2014-09-21 "Linux" "Linux Programmer's Manual"
.SH NAME
setresuid, setresgid \- set real, effective and saved user or group ID
.SH SYNOPSIS
On error, \-1 is returned, and
.I errno
is set appropriately.
+
+.IR Note :
+there are cases where
+.BR setresuid ()
+can fail even when the caller is UID 0;
+it is a grave security error to omit checking for a failure return from
+.BR setresuid ().
.SH ERRORS
.TP
.B EAGAIN
-.I uid
-does not match the current UID and this call would
-bring that user ID over its
+The call would change the caller's real UID (i.e.,
+.I ruid
+does not match the caller's real UID),
+but there was a temporary failure allocating the
+necessary kernel data structures.
+.TP
+.B EAGAIN
+.I ruid
+does not match the caller's real UID and this call would
+bring the number of processes belonging to the real user ID
+.I ruid
+over the caller's
.B RLIMIT_NPROC
resource limit.
+Since Linux 3.1, this error case no longer occurs
+(but robust applications should check for this error);
+see the description of
+.B EAGAIN
+in
+.BR execve (2).
+.TP
+.B EINVAL
+One or more of the target user or group IDs
+is not valid in this user namespace.
.TP
.B EPERM
The calling process is not privileged (did not have the \fBCAP_SETUID\fP
.SH NOTES
Under HP-UX and FreeBSD, the prototype is found in
.IR <unistd.h> .
-Under Linux the prototype is provided by glibc since version 2.3.2.
+Under Linux, the prototype is provided by glibc since version 2.3.2.
The original Linux
.BR setresuid ()
.BR setreuid (2),
.BR setuid (2),
.BR capabilities (7),
-.BR credentials (7)
+.BR credentials (7),
+.BR user_namespaces (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2004-07-04 by aeb
.\" 2004-05-27 by Michael Kerrisk
.\"
-.TH SETREUID 2 2013-12-12 "Linux" "Linux Programmer's Manual"
+.TH SETREUID 2 2014-09-21 "Linux" "Linux Programmer's Manual"
.SH NAME
setreuid, setregid \- set real and/or effective user or group ID
.SH SYNOPSIS
On error, \-1 is returned, and
.I errno
is set appropriately.
+
+.IR Note :
+there are cases where
+.BR setreuid ()
+can fail even when the caller is UID 0;
+it is a grave security error to omit checking for a failure return from
+.BR setreuid ().
.SH ERRORS
.TP
+.B EAGAIN
+The call would change the caller's real UID (i.e.,
+.I ruid
+does not match the caller's real UID),
+but there was a temporary failure allocating the
+necessary kernel data structures.
+.TP
+.B EAGAIN
+.I ruid
+does not match the caller's real UID and this call would
+bring the number of processes belonging to the real user ID
+.I ruid
+over the caller's
+.B RLIMIT_NPROC
+resource limit.
+Since Linux 3.1, this error case no longer occurs
+(but robust applications should check for this error);
+see the description of
+.B EAGAIN
+in
+.BR execve (2).
+.TP
+.B EINVAL
+One or more of the target user or group IDs
+is not valid in this user namespace.
+.TP
.B EPERM
The calling process is not privileged
(Linux: does not have the
.BR setgid (2),
.BR setresuid (2),
.BR setuid (2),
-.BR capabilities (7)
+.BR capabilities (7),
+.BR user_namespaces (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR tcgetsid (3),
.BR credentials (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" <richard@greenend.org.uk>, aeb 970616.
.\" Modified, 27 May 2004, Michael Kerrisk <mtk.manpages@gmail.com>
.\" Added notes on capability requirements
-.TH SETUID 2 2010-11-22 "Linux" "Linux Programmer's Manual"
+.TH SETUID 2 2014-09-21 "Linux" "Linux Programmer's Manual"
.SH NAME
setuid \- set user identity
.SH SYNOPSIS
On error, \-1 is returned, and
.I errno
is set appropriately.
+
+.IR Note :
+there are cases where
+.BR setuid ()
+can fail even when the caller is UID 0;
+it is a grave security error to omit checking for a failure return from
+.BR setuid ().
.SH ERRORS
.TP
.B EAGAIN
-The
+The call would change the caller's real UID (i.e.,
+.I uid
+does not match the caller's real UID),
+but there was a temporary failure allocating the
+necessary kernel data structures.
+.TP
+.B EAGAIN
.I uid
-does not match the current uid and
+does not match the real user ID of the caller and this call would
+bring the number of processes belonging to the real user ID
.I uid
-brings process over its
+over the caller's
.B RLIMIT_NPROC
resource limit.
+Since Linux 3.1, this error case no longer occurs
+(but robust applications should check for this error);
+see the description of
+.B EAGAIN
+in
+.BR execve (2).
+.TP
+.B EINVAL
+The user ID specified in
+.I uid
+is not valid in this user namespace.
.TP
.B EPERM
The user is not privileged (Linux: does not have the
.BR setfsuid (2),
.BR setreuid (2),
.BR capabilities (7),
-.BR credentials (7)
+.BR credentials (7),
+.BR user_namespaces (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
and at other times a single argument
.IR "int magic" .
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR attr (5),
.BR symlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sigprocmask (2),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR capabilities (7),
.BR svipc (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Language and formatting clean-ups
.\" Added notes on /proc files
.\"
-.TH SHMGET 2 2014-05-21 "Linux" "Linux Programmer's Manual"
+.TH SHMGET 2 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
shmget \- allocates a System V shared memory segment
.SH SYNOPSIS
call:
.TP
.B SHMALL
-System-wide limit on the number of shared memory pages.
-Since Linux 2.4, the default value for this limit is
+System-wide limit on the number of
+.I pages
+of shared memory.
+
+On Linux, this limit can be read and modified via
+.IR /proc/sys/kernel/shmall .
+Since Linux 3.16,
+.\" commit 060028bac94bf60a65415d1d55a359c3a17d5c31
+the default value for this limit is:
+
+ ULONG_MAX - 2^24
+
+The effect of this value
+(which is suitable for both 32-bit and 64-bit systems)
+is to impose no limitation on allocations.
+This value, rather than
+.BR ULONG_MAX ,
+was chosen as the default to prevent some cases where historical
+applications simply raised the existing limit without first checking
+its current value.
+Such applications would cause the value to overflow if the limit was set at
+.BR ULONG_MAX .
+
+From Linux 2.4 up to Linux 3.15,
+the default value for this limit was:
SHMMAX / PAGE_SIZE * (SHMMNI / 16)
.B SHMMAX
and
.B SHMMNI
-are not modified, this yields a limit for the
-total memory used by all shared memory segments of 8 GB:
-With a 4kB page size, this formula yields the value 2^21 (2,097,152),
-with 8kB page size, it yields 2^20 (1048576).
-
-On Linux, this limit can be read and modified via
-.IR /proc/sys/kernel/shmall .
+were not modified, then multiplying the result of this formula
+by the page size (to get a value in bytes) yielded a value of 8 GB
+as the limit on the total memory used by all shared memory segments.
.TP
.B SHMMAX
Maximum size in bytes for a shared memory segment.
-Since Linux 2.2, the default value of this limit is 0x2000000 (32MB).
On Linux, this limit can be read and modified via
.IR /proc/sys/kernel/shmmax .
+Since Linux 3.16,
+.\" commit 060028bac94bf60a65415d1d55a359c3a17d5c31
+the default value for this limit is:
+
+ ULONG_MAX - 2^24
+
+The effect of this value
+(which is suitable for both 32-bit and 64-bit systems)
+is to impose no limitation on allocations.
+See the description of
+.BR SHMALL
+for a discussion of why this default value (rather than
+.BR ULONG_MAX )
+is used.
+
+From Linux 2.2 up to Linux 3.15, the default value of
+this limit was 0x2000000 (32MB).
+
+Because it is not possible to map just part of a shared memory segment,
+the amount of virtual memory places another limit on the maximum size of a
+usable segment:
+for example, on i386 the largest segments that can be mapped have a
+size of around 2.8 GB, and on x86_64 the limit is around 127 TB.
.TP
.B SHMMIN
Minimum size in bytes for a shared memory segment: implementation
.BR shm_overview (7),
.BR svipc (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\" FIXME . Add an example program to this page.
.\"
-.TH SHMOP 2 2014-04-28 "Linux" "Linux Programmer's Manual"
+.TH SHMOP 2 2014-07-08 "Linux" "Linux Programmer's Manual"
.SH NAME
shmat, shmdt \- System V shared memory operations
.SH SYNOPSIS
.I "char\ *"
into
.IR "void\ *" .
-(Linux libc4 and libc5 have the
-.I "char\ *"
-prototypes; glibc2 has
-.IR "void\ *" .)
.SH NOTES
.PP
After a
The following system parameter affects
.BR shmat ():
.TP
-.\" FIXME A good explanation of the rationale for the existence
-.\" of SHMLBA would be useful here
.B SHMLBA
Segment low boundary address multiple.
-Must be page aligned.
-For the current implementation, the
+When explicitly specifying an attach address in a call to
+.BR shmat (),
+the caller should ensure that the address is a multiple of this value.
+This is necessary on some architectures,
+in order either to ensure good CPU cache performance or to ensure that
+different attaches of the same segment have consistent views
+within the CPU cache.
.B SHMLBA
-value is
-.BR PAGE_SIZE .
-.\" FIXME That last sentence isn't true for all Linux
-.\" architectures (i.e., SHMLBA != PAGE_SIZE for some architectures)
-.\" -- MTK, Nov 04
+is normally some multiple of the system page size
+(on many Linux architectures, it is the same as the system page size).
.PP
The implementation places no intrinsic per-process limit on the
number of shared memory segments
.BR shm_overview (7),
.BR svipc (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
checks for the validity of
.I how
are done in domain-specific code, and not all domains perform these checks.
-.\" FIXME
+.\" FIXME .
.\" https://bugzilla.kernel.org/show_bug.cgi?id=47111
Most notably, UNIX domain sockets simply ignore invalid values;
this may change in the future.
.BR socket (2),
.BR socket (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
hardware-generated signal
(unused on most architectures) */
.\" FIXME
-.\" si_trapno seems to be only used on SPARC and Alpha;
+.\" The siginfo_t 'si_trapno' filed seems to be used only on SPARC and Alpha;
.\" this page could use a little more detail on its purpose there.
pid_t si_pid; /* Sending process ID */
uid_t si_uid; /* Real user ID of sending process */
fill in
.I si_addr
with the address of the fault.
-.\" FIXME SIGTRAP also sets the following for ptrace_notify() ?
+.\" FIXME . SIGTRAP also sets the following for ptrace_notify() ?
.\" info.si_code = exit_code;
.\" info.si_pid = task_pid_vnr(current);
.\" info.si_uid = current_uid(); /* Real UID */
.BR core (5),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.B ENOMEM
The specified size of the new alternate signal stack
.I ss.ss_size
-as less than
+was less than
.BR MINSTKSZ .
.TP
.B EPERM
.BR sigsetjmp (3),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" various sections.
.\" 2008-07-11, mtk: rewrote and expanded portability discussion.
.\"
-.TH SIGNAL 2 2013-04-19 "Linux" "Linux Programmer's Manual"
+.TH SIGNAL 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
signal \- ANSI C signal handling
.SH SYNOPSIS
it is also implicitly defined if one defines
.BR _GNU_SOURCE ,
and can of course be explicitly defined.
-.sp
+.IP *
On glibc 2 and later, if the
.B _BSD_SOURCE
feature test macro is not defined, then
.\" System V semantics are also provided if one uses the separate
.\" .BR sysv_signal (3)
.\" function.
-.IP *
-The
-.BR signal ()
-function in Linux libc4 and libc5 provide System\ V semantics.
-If one on a libc5 system includes
-.I <bsd/signal.h>
-instead of
-.IR <signal.h> ,
-then
-.BR signal ()
-provides BSD semantics.
+.\" .IP *
+.\" The
+.\" .BR signal ()
+.\" function in Linux libc4 and libc5 provide System\ V semantics.
+.\" If one on a libc5 system includes
+.\" .I <bsd/signal.h>
+.\" instead of
+.\" .IR <signal.h> ,
+.\" then
+.\" .BR signal ()
+.\" provides BSD semantics.
.SH SEE ALSO
.BR kill (1),
.BR alarm (2),
.BR sysv_signal (3),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
-.TH SIGNALFD 2 2009-01-13 Linux "Linux Programmer's Manual"
+.TH SIGNALFD 2 2014-07-08 Linux "Linux Programmer's Manual"
.SH NAME
signalfd \- create a file descriptor for accepting signals
.SH SYNOPSIS
Starting with Linux 2.6.27, the following values may be bitwise ORed in
.IR flags
-to change the behaviour of
+to change the behavior of
.BR signalfd ():
.TP 14
.B SFD_NONBLOCK
uint64_t ssi_addr; /* Address that generated signal
(for hardware-generated signals) */
.\" FIXME Since Linux 2.6.37 there is 'uint16_t ssi_addr_lsb'
-.\" which is not yet documented
+.\" in the signalfd_siginfo structure. This needs to be documented.
uint8_t pad[\fIX\fP]; /* Pad size to 128 bytes (allow for
additional fields in the future) */
};
.BR signalfd4 ()
are Linux-specific.
.SH NOTES
-The underlying Linux system call requires an additional argument,
-.IR "size_t sizemask" ,
-which specifies the size of the
-.I mask
-argument.
-The glibc
-.BR signalfd ()
-wrapper function does not include this argument,
-since it provides the required value for the underlying system call.
-
A process can create multiple signalfd file descriptors.
This makes it possible to accept different signals
on different file descriptors.
.I mask
of more than one of the file descriptors, then occurrences
of that signal can be read (once) from any one of the descriptors.
-.SS Underlying Linux system calls
+.SS C library/kernel ABI differences
+The underlying Linux system call requires an additional argument,
+.IR "size_t sizemask" ,
+which specifies the size of the
+.I mask
+argument.
+The glibc
+.BR signalfd ()
+wrapper function does not include this argument,
+since it provides the required value for the underlying system call.
+
There are two underlying Linux system calls:
.BR signalfd ()
and the more recent
.BR epoll (7),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sigsetops (3),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sigsetops (3),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR signal (2),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sigwait (3),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH SIGWAITINFO 2 2013-09-04 "Linux" "Linux Programmer's Manual"
+.TH SIGWAITINFO 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
sigwaitinfo, sigtimedwait \- synchronously wait for queued signals
.SH SYNOPSIS
as a call to
.BR sigwaitinfo (),
and indeed this is what is done on Linux.
-
+.\"
+.SS C library/kernel ABI differences
On Linux,
.BR sigwaitinfo ()
is a library function implemented on top of
.BR sigtimedwait ().
+
+The raw
+.BR sigtimedwait ()
+system call has a fifth argument,
+.IR "size_t sigsetsize" ,
+which specifies the size in bytes of the
+.IR set
+argument.
+The glibc
+.BR sigtimedwait ()
+wrapper function specifies this argument as a fixed value
+(equal to
+.IR sizeof(sigset_t) ).
.SH SEE ALSO
.BR kill (2),
.BR sigaction (2),
.BR signal (7),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
reprinted in
.I UNIX Programmer's Supplementary Documents Volume 1.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR socket (2),
.BR socketpair (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR socket (7),
.BR unix (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH SPLICE 2 2012-05-04 "Linux" "Linux Programmer's Manual"
+.TH SPLICE 2 2014-07-08 "Linux" "Linux Programmer's Manual"
.SH NAME
splice \- splice data to/from a pipe
.SH SYNOPSIS
is set to indicate the error.
.SH ERRORS
.TP
+.B EAGAIN
+.B SPLICE_F_NONBLOCK
+was specified in
+.IR flags ,
+and the operation would block.
+.TP
.B EBADF
One or both file descriptors are not valid,
or do not have proper read-write mode.
.BR tee (2),
.BR vmsplice (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR capabilities (7),
.BR spufs (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR capabilities (7),
.BR spufs (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2007-06-08 mtk: Added example program
.\" 2007-07-05 mtk: Added details on underlying system call interfaces
.\"
-.TH STAT 2 2014-05-10 "Linux" "Linux Programmer's Manual"
+.TH STAT 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
stat, fstat, lstat, fstatat \- get file status
.SH SYNOPSIS
.BR execve (2),
.BR mknod (2),
.BR pipe (2),
-.BR utime (2)
+.BR utime (2),
and
.BR read (2)
(of more than zero bytes).
is changed by file modifications, for example, by
.BR mknod (2),
.BR truncate (2),
-.BR utime (2)
+.BR utime (2),
and
.BR write (2)
(of more than zero bytes).
.fi
.PP
The definitions of most of the above file type test macros
-are provided if any of the following feature test macros are defined:
+are provided if any of the following feature test macros is defined:
.BR _BSD_SOURCE
(in glibc 2.19 and earlier),
.BR _SVID_SOURCE
.BR capabilities (7),
.BR symlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 2003-08-17 by Walter Harms
.\" Modified 2004-06-23 by Michael Kerrisk <mtk.manpages@gmail.com>
.\"
-.TH STATFS 2 2010-11-21 "Linux" "Linux Programmer's Manual"
+.TH STATFS 2 2014-06-13 "Linux" "Linux Programmer's Manual"
.SH NAME
statfs, fstatfs \- get filesystem statistics
.SH SYNOPSIS
ADFS_SUPER_MAGIC 0xadf5
AFFS_SUPER_MAGIC 0xADFF
+ BDEVFS_MAGIC 0x62646576
BEFS_SUPER_MAGIC 0x42465331
BFS_MAGIC 0x1BADFACE
+ BINFMTFS_MAGIC 0x42494e4d
+ BTRFS_SUPER_MAGIC 0x9123683E
+ CGROUP_SUPER_MAGIC 0x27e0eb
CIFS_MAGIC_NUMBER 0xFF534D42
CODA_SUPER_MAGIC 0x73757245
COH_SUPER_MAGIC 0x012FF7B7
CRAMFS_MAGIC 0x28cd3d45
+ DEBUGFS_MAGIC 0x64626720
DEVFS_SUPER_MAGIC 0x1373
+ DEVPTS_SUPER_MAGIC 0x1cd1
+ EFIVARFS_MAGIC 0xde5e81e4
EFS_SUPER_MAGIC 0x00414A53
EXT_SUPER_MAGIC 0x137D
EXT2_OLD_SUPER_MAGIC 0xEF51
EXT2_SUPER_MAGIC 0xEF53
EXT3_SUPER_MAGIC 0xEF53
EXT4_SUPER_MAGIC 0xEF53
+ FUSE_SUPER_MAGIC 0x65735546
+ FUTEXFS_SUPER_MAGIC 0xBAD1DEA
HFS_SUPER_MAGIC 0x4244
+ HOSTFS_SUPER_MAGIC 0x00c0ffee
HPFS_SUPER_MAGIC 0xF995E849
HUGETLBFS_MAGIC 0x958458f6
ISOFS_SUPER_MAGIC 0x9660
MINIX_SUPER_MAGIC2 0x138F /* 30 char minix */
MINIX2_SUPER_MAGIC 0x2468 /* minix V2 */
MINIX2_SUPER_MAGIC2 0x2478 /* minix V2, 30 char names */
+ MINIX3_SUPER_MAGIC 0x4d5a /* minix V3 fs, 60 char names */
+ MQUEUE_MAGIC 0x19800202
MSDOS_SUPER_MAGIC 0x4d44
NCP_SUPER_MAGIC 0x564c
NFS_SUPER_MAGIC 0x6969
+ NILFS_SUPER_MAGIC 0x3434
NTFS_SB_MAGIC 0x5346544e
OPENPROM_SUPER_MAGIC 0x9fa1
+ PIPEFS_MAGIC 0x50495045
PROC_SUPER_MAGIC 0x9fa0
+ PSTOREFS_MAGIC 0x6165676C
QNX4_SUPER_MAGIC 0x002f
+ QNX6_SUPER_MAGIC 0x68191122
+ RAMFS_MAGIC 0x858458f6
REISERFS_SUPER_MAGIC 0x52654973
ROMFS_MAGIC 0x7275
+ SELINUX_MAGIC 0xf97cff8c
+ SMACK_MAGIC 0x43415d53
SMB_SUPER_MAGIC 0x517B
+ SOCKFS_MAGIC 0x534F434B
+ SQUASHFS_MAGIC 0x73717368
+ SYSFS_MAGIC 0x62656572
SYSV2_SUPER_MAGIC 0x012FF7B6
SYSV4_SUPER_MAGIC 0x012FF7B5
TMPFS_MAGIC 0x01021994
UDF_SUPER_MAGIC 0x15013346
UFS_MAGIC 0x00011954
USBDEVICE_SUPER_MAGIC 0x9fa2
+ V9FS_MAGIC 0x01021997
VXFS_SUPER_MAGIC 0xa501FCF5
+ XENFS_SUPER_MAGIC 0xabba1974
XENIX_SUPER_MAGIC 0x012FF7B4
XFS_SUPER_MAGIC 0x58465342
_XIAFS_SUPER_MAGIC 0x012FD16D
.fi
.in
.PP
+Most of these MAGIC constants are defined in
+.I /usr/include/linux/magic.h
+some are hardcoded in kernel sources.
+.PP
Nobody knows what
.I f_fsid
is supposed to contain (but see below).
contains some random stuff such that the pair
.RI ( f_fsid , ino )
uniquely determines a file.
-Some operating systems use (a variation on) the device number, or the device number
-combined with the filesystem type.
-Several OSes restrict giving out the
+Some operating systems use (a variation on) the device number,
+or the device number combined with the filesystem type.
+Several operating systems restrict giving out the
.I f_fsid
field to the superuser only (and zero it for unprivileged users),
because this field is used in the filehandle of the filesystem
when NFS-exported, and giving it out is a security concern.
.LP
-Under some operating systems the
+Under some operating systems, the
.I fsid
-can be used as second argument to the
+can be used as the second argument to the
.BR sysfs (2)
system call.
+.SH BUGS
+From Linux 2.6.38 up to and including Linux 3.1,
+.\" broken in commit ff0c7d15f9787b7e8c601533c015295cc68329f8
+.\" fixed in commit d70ef97baf048412c395bb5d65791d8fe133a52b
+.BR fstatfs ()
+failed with the error
+.B ENOSYS
+for file descriptors created by
+.BR pipe (2).
.SH SEE ALSO
.BR stat (2),
.BR statvfs (2),
.BR path_resolution (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.TP
.B EPERM
The calling process has insufficient privilege.
-Under Linux the
+Under Linux, the
.B CAP_SYS_TIME
privilege is required.
.SH CONFORMING TO
.BR settimeofday (2),
.BR capabilities (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.IR Documentation/vm/hugetlbpage.txt
in the Linux kernel source tree
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2007-06-22 Ivana Varekova <varekova@redhat.com>, mtk
.\" Update text describing limit on number of swap files.
.\"
+.\" FIXME Linux 3.11 added SWAP_FLAG_DISCARD_ONCE and SWAP_FLAG_DISCARD_PAGES
+.\" commit dcf6b7ddd7df8965727746f89c59229b23180e5a
+.\" Author: Rafael Aquini <aquini@redhat.com>
+.\" Date: Wed Jul 3 15:02:46 2013 -0700
+.\"
.TH SWAPON 2 2014-05-28 "Linux" "Linux Programmer's Manual"
.SH NAME
swapon, swapoff \- start/stop swapping to file/device
.BR swapoff (8),
.BR swapon (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 1997-01-31 by Eric S. Raymond <esr@thyrsus.com>
.\" Modified 2004-06-23 by Michael Kerrisk <mtk.manpages@gmail.com>
.\"
-.TH SYMLINK 2 2014-05-05 "Linux" "Linux Programmer's Manual"
+.TH SYMLINK 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
symlink, symlinkat \- make a new name for a file
.SH SYNOPSIS
file (unless it also has other hard links).
If this behavior is not desired, use
.BR link (2).
+.SS Glibc notes
+On older kernels where
+.BR symlinkat ()
+is unavailable, the glibc wrapper function falls back to the use of
+.BR symlink (2).
+When
+.I linkpath
+is a relative pathname,
+glibc constructs a pathname based on the symbolic link in
+.IR /proc/self/fd
+that corresponds to the
+.IR newdirfd
+argument.
.SH SEE ALSO
.BR ln (1),
.BR lchown (2),
.BR path_resolution (7),
.BR symlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 2001-10-10 by aeb, following Michael Kerrisk.
.\" 2011-09-07, mtk, Added syncfs() documentation,
.\"
-.TH SYNC 2 2014-04-06 "Linux" "Linux Programmer's Manual"
+.TH SYNC 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
sync, syncfs \- commit buffer cache to disk
.SH SYNOPSIS
.BR syncfs ()
is Linux-specific.
.SH NOTES
-Since glibc 2.2.2 the Linux prototype for
+Since glibc 2.2.2, the Linux prototype for
.BR sync ()
is as listed above,
following the various standards.
-In libc4, libc5, and glibc up to 2.2.1
+In glibc 2.2.1 and earlier,
it was "int sync(void)", and
.BR sync ()
always returned 0.
.BR bdflush (2),
.BR fdatasync (2),
.BR fsync (2),
-.BR sync (8)
+.BR sync (1)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Andrew Morton's comments in fs/sync.c
.\" 2010-10-09, mtk, Document sync_file_range2()
.\"
-.TH SYNC_FILE_RANGE 2 2013-04-01 "Linux" "Linux Programmer's Manual"
+.TH SYNC_FILE_RANGE 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
sync_file_range \- sync a file segment with disk
.SH SYNOPSIS
This system call is Linux-specific, and should be avoided
in portable programs.
.SH NOTES
+.SS sync_file_range2()
Some architectures (e.g., PowerPC, ARM)
need 64-bit arguments to be aligned in a suitable pair of registers.
.\" See kernel commit edd5cd4a9424f22b0fa08bef5e299d41befd5622
.BR msync (2),
.BR sync (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR syscalls (2),
.BR vdso (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH SYSCALLS 2 2014-05-08 "Linux" "Linux Programmer's Manual"
+.TH SYSCALLS 2 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
syscalls \- Linux system calls
.SH SYNOPSIS
\fBgetpid\fP(2) 1.0
\fBgetppid\fP(2) 1.0
\fBgetpriority\fP(2) 1.0
+\fBgetrandom\fP(2) 3.17
\fBgetresgid\fP(2) 2.2
\fBgetresgid32\fP(2) 2.4
\fBgetresuid\fP(2) 2.2
.\" Implements System V IPC calls
\fBkcmp\fP(2) 3.5
\fBkern_features\fP(2) 3.7 Sparc64
-.\" FIXME: document kern_features():
+.\" FIXME . document kern_features():
.\" commit 517ffce4e1a03aea979fe3a18a3dd1761a24fafb
+\fBkexec_file_load\fP(2) 3.17
\fBkexec_load\fP(2) 2.6.13
.\" The entry in the syscall table was reserved starting in 2.6.7
.\" Was named sys_kexec_load() from 2.6.7 to 2.6.16
\fBmadvise\fP(2) 2.4
\fBmbind\fP(2) 2.6.6
.\" \fBmemory_ordering\fP(2) ??? Sparc64
+\fBmemfd_create\fP(2) 3.17
\fBmigrate_pages\fP(2) 2.6.16
\fBmincore\fP(2) 2.4
\fBmkdir\fP(2) 1.0
T}
\fBpreadv\fP(2) 2.6.30
\fBprlimit\fP(2) 2.6.36
+\fBprlimit64\fP(2) 2.6.36
\fBprocess_vm_readv\fP(2) 3.2
\fBprocess_vm_writev\fP(2) 3.2
\fBpselect6\fP(2) 2.6.16
\fBrecvfrom\fP(2) 2.0 See notes on \fBsocketcall\fP(2)
\fBrecvmsg\fP(2) 2.0 See notes on \fBsocketcall\fP(2)
\fBrecvmmsg\fP(2) 2.6.33
-\fBremap_file_pages\fP(2) 2.6
+\fBremap_file_pages\fP(2) 2.6 Deprecated since 3.16
\fBremovexattr\fP(2) 2.6; 2.4.18
\fBrename\fP(2) 1.0
\fBrenameat\fP(2) 2.6.16
\fBsched_setparam\fP(2) 2.0
\fBsched_setscheduler\fP(2) 2.0
\fBsched_yield\fP(2) 2.0
+\fBseccomp\fP(2) 3.17
\fBselect\fP(2) 1.0
\fBsemctl\fP(2) 2.0 See notes on \fBipc\fP(2)
\fBsemget\fP(2) 2.0 See notes on \fBipc\fP(2)
\fButimensat\fP(2) 2.6.22
\fButimes\fP(2) 2.2
\fButrap_install\fP(2) 2.2 Sparc
-.\" FIXME: document utrap_install()
+.\" FIXME . document utrap_install()
.\" There's a man page for Solaris 5.11
\fBvfork\fP(2) 2.2
\fBvhangup\fP(2) 1.0
.BR unimplemented (2)).
However,
.BR ftime (3),
-.BR profil (3)
+.BR profil (3),
and
.BR ulimit (3)
exist as library routines.
.BR libc (7),
.BR vdso (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR proc (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
There is no libc or glibc support.
There is no way to guess how large \fIbuf\fP should be.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified Tue Oct 22 22:29:51 1996 by Eric S. Raymond <esr@thyrsus.com>
.\" Modified Mon Aug 25 16:06:11 1997 by Nicolás Lichtmaier <nick@debian.org>
.\"
-.TH SYSINFO 2 2012-05-05 "Linux" "Linux Programmer's Manual"
+.TH SYSINFO 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
sysinfo \- returns information on overall system statistics
.SH SYNOPSIS
.TP
.B EFAULT
pointer to \fIstruct\ sysinfo\fP is invalid
-.SH CONFORMING TO
-This function is Linux-specific, and should not be used in programs
-intended to be portable.
-.sp
+.SH VERSIONS
The Linux kernel has a
.BR sysinfo ()
system call since 0.98.pl6.
-Linux libc contains a
-.BR sysinfo ()
-routine since 5.3.5, and
-glibc has one since 1.90.
+.SH CONFORMING TO
+This function is Linux-specific, and should not be used in programs
+intended to be portable.
.SH SEE ALSO
.BR proc (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
+'\" t
.\" Copyright (C) 1995 Andries Brouwer (aeb@cwi.nl)
+.\" and Copyright (C) 2012, 2014 Michael Kerrisk <mtk.manpages@gmail.com>
.\"
.\" %%%LICENSE_START(VERBATIM)
.\" Permission is granted to make and distribute verbatim copies of this
.\" 2008-02-15, Michael Kerrisk <mtk.manpages@gmail.com>
.\" Update LOG_BUF_LEN details; update RETURN VALUE section.
.\"
-.TH SYSLOG 2 2012-11-29 "Linux" "Linux Programmer's Manual"
+.TH SYSLOG 2 2014-07-08 "Linux" "Linux Programmer's Manual"
.SH NAME
syslog, klogctl \- read and/or clear kernel message ring buffer;
set console_loglevel
.BI "int klogctl(int " type ", char *" bufp ", int " len );
.fi
.SH DESCRIPTION
-If you need the C library function
+.IR Note :
+Probably, you are looking for the C library function
+.BR syslog (),
+which talks to
+.BR syslogd (8);
+see
+.BR syslog (3)
+for details.
+
+This page describes the kernel
.BR syslog ()
-(which talks to
-.BR syslogd (8)),
-then look at
-.BR syslog (3).
-The system call of this name is about controlling the kernel
+system call, which is used to control the kernel
.IR printk ()
-buffer, and the glibc wrapper function is called
+buffer; the glibc wrapper function for the system call is called
.BR klogctl ().
.SS The kernel log buffer
The kernel has a cyclic buffer of length
.B LOG_BUF_LEN
in which messages given as arguments to the kernel function
.BR printk ()
-are stored (regardless of their loglevel).
+are stored (regardless of their log level).
In early kernels,
.B LOG_BUF_LEN
had the value 4096;
from kernel 1.3.54, it was 8192;
-from kernel 2.1.113 it was 16384;
-since 2.4.23/2.6 the value is a kernel configuration option
-.RB ( CONFIG_LOG_BUF_SHIFT ).
+from kernel 2.1.113, it was 16384;
+since kernel 2.4.23/2.6, the value is a kernel configuration option
+.RB ( CONFIG_LOG_BUF_SHIFT ,
+default value dependent on the architecture).
.\" Under "General setup" ==> "Kernel log buffer size"
.\" For 2.6, precisely the option seems to have appeared in 2.5.55.
-In recent kernels the size can be queried with command type 10 (see below).
+Since Linux 2.6.6, the size can be queried with command type 10 (see below).
.SS Commands
The \fItype\fP argument determines the action taken by this function.
The list below specifies the values for
.TP
.BR SYSLOG_ACTION_READ_ALL " (3)"
Read all messages remaining in the ring buffer,
-placing then in the buffer pointed to by
+placing them in the buffer pointed to by
.IR bufp .
The call reads the last \fIlen\fP
bytes from the log buffer (nondestructively),
.RB ( SYSLOG_ACTION_SIZE_UNREAD ).
.TP
.BR SYSLOG_ACTION_CONSOLE_OFF " (6)"
-Disable printk to console.
-The call sets the console log level to the minimum,
+The command saves the current value of
+.I console_loglevel
+and then sets
+.I console_loglevel
+to
+.IR minimum_console_loglevel ,
so that no messages are printed to the console.
+Before Linux 2.6.32,
+.\" commit 1aaad49e856ce41adc07d8ae0c8ef35fc4483245
+the command simply sets
+.I console_loglevel
+to
+.IR minimum_console_loglevel .
+See the discussion of
+.IR /proc/sys/kernel/printk ,
+below.
+
The
.I bufp
and
arguments are ignored.
.TP
.BR SYSLOG_ACTION_CONSOLE_ON " (7)"
-The call sets the console log level to the default,
-so that messages are printed to the console.
+If a previous
+.B SYSLOG_ACTION_CONSOLE_OFF
+command has been performed,
+this command restores
+.I console_loglevel
+to the value that was saved by that command.
+Before Linux 2.6.32,
+.\" commit 1aaad49e856ce41adc07d8ae0c8ef35fc4483245
+this command simply sets
+.I console_loglevel
+to
+.IR default_console_loglevel .
+See the discussion of
+.IR /proc/sys/kernel/printk ,
+below.
+
The
.I bufp
and
arguments are ignored.
.TP
.BR SYSLOG_ACTION_CONSOLE_LEVEL " (8)"
-The call sets the console log level to the value given in
+The call sets
+.I console_loglevel
+to the value given in
.IR len ,
which must be an integer between 1 and 8 (inclusive).
+The kernel silently enforces a minimum value of
+.IR minimum_console_loglevel
+for
+.IR len .
See the
-.B loglevel
+.IR "log level"
section for details.
The
.I bufp
capability (now deprecated for this purpose) or the (new)
.BR CAP_SYSLOG
capability.
-.SS The loglevel
-The kernel routine
-.BR printk ()
-will only print a message on the
-console, if it has a loglevel less than the value of the variable
-.IR console_loglevel .
-This variable initially has the value
+.\"
+.\"
+.SS /proc/sys/kernel/printk
+.I /proc/sys/kernel/printk
+is a writable file containing four integer values that influence kernel
+.I printk()
+behavior when printing or logging error messages.
+The four values are:
+.TP
+.I console_loglevel
+Only messages with a log level lower than this value will
+be printed to the console.
+The default value for this field is
.B DEFAULT_CONSOLE_LOGLEVEL
-(7), but is set to 10 if the
-kernel command line contains the word "debug", and to 15 in case
+(7), but it is set to
+4 if the kernel command line contains the word "quiet", \" since Linux 2.4
+10 if the kernel command line contains the word "debug",
+and to 15 in case
of a kernel fault (the 10 and 15 are just silly, and equivalent to 8).
-This variable is set (to a value in the range 1-8) by a
+The value of
+.IR console_loglevel
+can be set (to a value in the range 1-8) by a
.BR syslog ()
call with a
.I type
of 8.
-Calls to
-.BR syslog ()
-with
-.I type
-equal to 6 or 7 set the variable to 1 (kernel panics only)
-or 7 (all except debugging messages), respectively.
+.TP
+.I default_message_loglevel
+This value will be used as the log level for
+.IR printk()
+messages that do not have an explicit level.
+Up to and including Linux 2.6.38,
+the hard-coded default value for this field was 4
+.RB ( KERN_WARNING );
+since Linux 2.6.39,
+.\" commit 5af5bcb8d37f99ba415a1adc6da71051b84f93a5
+the default value is a defined by the kernel configuration option
+.BR CONFIG_DEFAULT_MESSAGE_LOGLEVEL ,
+which defaults to 4.
+.TP
+.I minimum_console_loglevel
+The value in this field is the minimum value to which
+.I console_loglevel
+can be set.
+.TP
+.I default_console_loglevel
+This is the default value for
+.IR console_loglevel .
+.\"
+.\"
+.SS The log level
+Every
+.IR printk ()
+message has its own log level.
+If the log level is not explicitly specified as part of the message,
+it defaults to
+.IR default_message_loglevel .
+The conventional meaning of the log level is as follows:
-Every text line in a message has its own loglevel.
-This level is
-.I "DEFAULT_MESSAGE_LOGLEVEL \- 1"
-(6) unless the line starts with <d>
-where \fId\fP is a digit in the range 1-7, in which case the level
-is \fId\fP.
-The conventional meaning of the loglevel is defined in
-.I <linux/kernel.h>
-as follows:
+.TS
+lB lB lB
+lB c l.
+Kernel constant Level value Meaning
+KERN_EMERG 0 System is unusable
+KERN_ALERT 1 Action must be taken immediately
+KERN_CRIT 2 Critical conditions
+KERN_ERR 3 Error conditions
+KERN_WARNING 4 Warning conditions
+KERN_NOTICE 5 Normal but significant condition
+KERN_INFO 6 Informational
+KERN_DEBUG 7 Debug-level messages
+.TE
-.nf
-#define KERN_EMERG "<0>" /* system is unusable */
-#define KERN_ALERT "<1>" /* action must be taken immediately */
-#define KERN_CRIT "<2>" /* critical conditions */
-#define KERN_ERR "<3>" /* error conditions */
-#define KERN_WARNING "<4>" /* warning conditions */
-#define KERN_NOTICE "<5>" /* normal but significant condition */
-#define KERN_INFO "<6>" /* informational */
-#define KERN_DEBUG "<7>" /* debug-level messages */
-.fi
+The kernel
+.IR printk()
+routine will print a message on the
+console only if it has a log level less than the value of
+.IR console_loglevel .
.SH RETURN VALUE
For \fItype\fP equal to 2, 3, or 4, a successful call to
.BR syslog ()
kernel-configuration option disabled.
.TP
.B EPERM
-An attempt was made to change console_loglevel or clear the kernel
+An attempt was made to change
+.I console_loglevel
+or clear the kernel
message ring buffer by a process without sufficient privilege
(more precisely: without the
.B CAP_SYS_ADMIN
This system call is Linux-specific and should not be used in programs
intended to be portable.
.SH NOTES
-From the very start people noted that it is unfortunate that
+From the very start, people noted that it is unfortunate that
a system call and a library routine of the same name are entirely
different animals.
.\" In libc4 and libc5 the number of this call was defined by
.BR syslog (3),
.BR capabilities (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH TEE 2 2012-05-04 "Linux" "Linux Programmer's Manual"
+.TH TEE 2 2014-07-08 "Linux" "Linux Programmer's Manual"
.SH NAME
tee \- duplicating pipe content
.SH SYNOPSIS
is set to indicate the error.
.SH ERRORS
.TP
+.B EAGAIN
+.B SPLICE_F_NONBLOCK
+was specified in
+.IR flags ,
+and the operation would block.
+.TP
.B EINVAL
.I fd_in
or
.BR splice (2),
.BR vmsplice (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ftime (3),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.\" FIXME: Linux 2.6.39 adds CLOCK_BOOTTIME
+.\" FIXME Linux 2.6.39 adds CLOCK_BOOTTIME, which needs be documented
.\" Does this also affect timerfd_create()?
-.\" FIXME: Linux 2.3.0 adds CLOCK_BOOTTIME_ALARM and CLOCK_REALTIME_ALARM
+.\"
+.\" FIXME Linux 3.0 adds CLOCK_BOOTTIME_ALARM and CLOCK_REALTIME_ALARM,
+.\" which need be documented
.\" Does this also affect timerfd_create()?
.\"
-.TH TIMER_CREATE 2 2014-01-20 Linux "Linux Programmer's Manual"
+.TH TIMER_CREATE 2 2014-08-19 Linux "Linux Programmer's Manual"
.SH NAME
timer_create \- create a POSIX per-process timer
.SH SYNOPSIS
.IP *
.BR timer_delete (2):
Disarm and delete a timer.
-.PP
+
+Since Linux 3.10, the
+.IR /proc/[pid]/timers
+file can be used to list the POSIX timers for the process with PID
+.IR pid .
+See
+.BR proc (5)
+for further information.
+.\"
+.SS C library/kernel ABI differences
Part of the implementation of the POSIX timers API is provided by glibc.
In particular:
.IP * 3
timers only) using POSIX threads,
and current glibc falls back to this implementation on systems
running pre-2.6 Linux kernels.
-
-Since Linux 3.10, the
-.IR /proc/[pid]/timers
-file can be used to list the POSIX timers for the process with PID
-.IR pid .
-See
-.BR proc (5)
-for further information.
.SH EXAMPLE
The program below takes two arguments: a sleep period in seconds,
and a timer frequency in nanoseconds.
.BR signal (7),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR timer_settime (2),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR signal (7),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BI "int timer_settime(timer_t " timerid ", int " flags ,
.BI " const struct itimerspec *" new_value ,
-.BI " struct itimerspec * " old_value );
+.BI " struct itimerspec *" old_value );
.BI "int timer_gettime(timer_t " timerid ", struct itimerspec *" curr_value );
.fi
.BR timer_getoverrun (2),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
-.\" FIXME: Linux 3.0: timerfd_settime() adds a TFD_TIMER_CANCEL_ON_SET flag.
+.\" FIXME Linux 3.0: timerfd_settime() adds a TFD_TIMER_CANCEL_ON_SET flag;
+.\" This flag needs to documented.
.\"
.TH TIMERFD_CREATE 2 2011-09-14 Linux "Linux Programmer's Manual"
.SH NAME
.BR epoll (7),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
(41 seconds) soon after boot when
.BR times ()
can return \-1, falsely indicating that an error occurred.
-The same problem can occur when the return value wraps passed
+The same problem can occur when the return value wraps past
the maximum value that can be stored in
.BR clock_t .
.\" The problem is that a syscall return of -4095 to -1
.BR sysconf (3),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
which may result in the wrong thread being signaled if a thread
terminates and its thread ID is recycled.
Avoid using this system call.
-.\" FIXME: Maybe say something about the following:
+.\" FIXME Maybe say something about the following:
.\" http://sourceware.org/bugzilla/show_bug.cgi?id=12889
.\" Rich Felker <bugdal@aerifal.cx>
.\" There is a race condition in pthread_kill: it is possible that,
.BR kill (2),
.BR rt_sigqueueinfo (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR path_resolution (7).)
.TP
.B EFAULT
-.I Path
+The argument
+.I path
points outside the process's allocated address space.
.TP
.B EFBIG
.BR stat (2),
.BR path_resolution (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR stat (2),
.BR acl (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mount (8),
.BR umount (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\" 2007-07-05 mtk: Added details on underlying system call interfaces
.\"
-.TH UNAME 2 2008-12-03 "Linux" "Linux Programmer's Manual"
+.TH UNAME 2 2014-09-21 "Linux" "Linux Programmer's Manual"
.SH NAME
uname \- get name and information about current kernel
.SH SYNOPSIS
.IR osrelease ,
.IR version ,
.IR domainname }.
-.SS Underlying kernel interface
+.SS C library/kernel ABI differences
.LP
Over time, increases in the size of the
.I utsname
.SH SEE ALSO
.BR uname (1),
.BR getdomainname (2),
-.BR gethostname (2)
+.BR gethostname (2),
+.BR namespaces (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH NOTES
Note that
.BR ftime (3),
-.BR profil (3)
+.BR profil (3),
and
.BR ulimit (3)
are implemented as library functions.
.SH SEE ALSO
.BR syscalls (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 2001-05-17 by aeb
.\" Modified 2004-06-23 by Michael Kerrisk <mtk.manpages@gmail.com>
.\"
-.TH UNLINK 2 2014-02-21 "Linux" "Linux Programmer's Manual"
+.TH UNLINK 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
unlink, unlinkat \- delete a name and possibly the file it refers to
.SH SYNOPSIS
.BR unlinkat ():
POSIX.1-2008.
+.SH NOTES
+.SS Glibc notes
+On older kernels where
+.BR unlinkat ()
+is unavailable, the glibc wrapper function falls back to the use of
+.BR unlink (2)
+or
+.BR rmdir (2).
+When
+.I pathname
+is a relative pathname,
+glibc constructs a pathname based on the symbolic link in
+.IR /proc/self/fd
+that corresponds to the
+.IR dirfd
+argument.
.SH BUGS
Infelicities in the protocol underlying NFS can cause the unexpected
disappearance of files which are still being used.
.BR path_resolution (7),
.BR symlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Copyright (C) 2006, Janak Desai <janak@us.ibm.com>
-.\" and Copyright (C) 2006, Michael Kerrisk <mtk.manpages@gmail.com>
+.\" and Copyright (C) 2006, 2012 Michael Kerrisk <mtk.manpages@gmail.com>
.\"
.\" %%%LICENSE_START(GPL_NOVERSION_ONELINE)
.\" Licensed under the GPL
.\" by clone, which would require porting and maintaining all commands
.\" such as login, and su, that establish a user session.
.\"
-.TH UNSHARE 2 2013-04-17 "Linux" "Linux Programmer's Manual"
+.TH UNSHARE 2 2014-09-21 "Linux" "Linux Programmer's Manual"
.SH NAME
unshare \- disassociate parts of the process execution context
.SH SYNOPSIS
.BR CAP_SYS_ADMIN
capability.
.TP
-.BR CLONE_NEWUTS " (since Linux 2.6.19)
+.BR CLONE_NEWPID " (since Linux 3.8)"
+This flag has the same effect as the
+.BR clone (2)
+.B CLONE_NEWPID
+flag.
+Unshare the PID namespace,
+so that the calling process has a new PID namespace for its children
+which is not shared with any previously existing process.
+The calling process is
+.I not
+moved into the new namespace.
+The first child created by the calling process will have
+the process ID 1 and will assume the role of
+.BR init (1)
+in the new namespace.
+.BR CLONE_NEWPID
+automatically implies
+.BR CLONE_THREAD
+as well.
+Use of
+.BR CLONE_NEWPID
+requires the
+.BR CAP_SYS_ADMIN
+capability.
+For further information, see
+.BR pid_namespaces (7).
+.TP
+.BR CLONE_NEWUSER " (since Linux 3.8)"
+This flag has the same effect as the
+.BR clone (2)
+.B CLONE_NEWUSER
+flag.
+Unshare the user namespace,
+so that the calling process is moved into a new user namespace
+which is not shared with any previously existing process.
+As with the child process created by
+.BR clone (2)
+with the
+.B CLONE_NEWUSER
+flag, the caller obtains a full set of capabilities in the new namespace.
+.IP
+.BR CLONE_NEWUSER
+requires that the calling process is not threaded; specifying
+.BR CLONE_NEWUSER
+automatically implies
+.BR CLONE_THREAD .
+Since Linux 3.9,
+.\" commit e66eded8309ebf679d3d3c1f5820d1f2ca332c71
+.\" https://lwn.net/Articles/543273/
+.BR CLONE_NEWUSER
+also automatically implies
+.BR CLONE_FS .
+.BR CLONE_NEWUSER
+requires that the user ID and group ID
+of the calling process are mapped to user IDs and group IDs in the
+user namespace of the calling process at the time of the call.
+
+For further information on user namespaces, see
+.BR user_namespaces (7).
+.TP
+.BR CLONE_NEWUTS " (since Linux 2.6.19)"
This flag has the same effect as the
.BR clone (2)
.B CLONE_NEWUTS
.BR clone (2)
.B CLONE_SYSVSEM
flag.
-Unshare System\ V semaphore undo values,
-so that the calling process has a private copy
-which is not shared with any other process.
-Use of
-.BR CLONE_SYSVSEM
-requires the
-.BR CAP_SYS_ADMIN
-capability.
-.\" As at 2.6.16, the following forced implications also apply,
+Unshare System\ V semaphore adjustment
+.RI ( semadj )
+values,
+so that the calling process has a new empty
+.I semadj
+list that is not shared with any other process.
+If this is the last process that has a reference to the process's current
+.I semadj
+list, then the adjustments in that list are applied
+to the corresponding semaphores, as described in
+.BR semop (2).
+.\" CLONE_NEWNS If CLONE_SIGHAND is set and signals are also being shared
+.\" (i.e., current->signal->count > 1), force CLONE_THREAD.
+.PP
+In addition,
+.BR CLONE_THREAD ,
+.BR CLONE_SIGHAND ,
+and
+.BR CLONE_VM
+can be specified in
+.I flags
+if the caller is single threaded (i.e., it is not sharing
+its address space with another process or thread).
+In this case, these flags have no effect.
+(Note also that specifying
+.BR CLONE_THREAD
+automatically implies
+.BR CLONE_VM ,
+and specifying
+.BR CLONE_VM
+automatically implies
+.BR CLONE_SIGHAND .)
+.\" As at 3.9, the following forced implications also apply,
.\" although the relevant flags are not yet implemented.
.\" If CLONE_THREAD is set force CLONE_VM.
.\" If CLONE_VM is set, force CLONE_SIGHAND.
-.\" CLONE_NEWNSIf CLONE_SIGHAND is set and signals are also being shared
-.\" (i.e., current->signal->count > 1), force CLONE_THREAD.
.\"
-.\" FIXME . CLONE_VM is not (yet, as at 2.6.16) implemented.
-.\" .TP
-.\" .B CLONE_VM
-.\" Reverse the effect of the
-.\" .BR clone (2)
-.\" .B CLONE_VM
-.\" flag.
-.\" .RB ( CLONE_VM
-.\" is also implicitly set by
-.\" .BR vfork (2),
-.\" and can be reversed using this
-.\" .BR unshare ()
-.\" flag.)
-.\" Unshare virtual memory, so that the calling process no
-.\" longer shares its virtual address space with any other process.
+If the process is multithreaded, then
+the use of these flags results in an error.
+.\" See kernel/fork.c::check_unshare_flags()
.PP
If
.I flags
An invalid bit was specified in
.IR flags .
.TP
+.B EINVAL
+.BR CLONE_THREAD ,
+.BR CLONE_SIGHAND ,
+or
+.BR CLONE_VM
+was specified in
+.IR flags ,
+and the caller is multithreaded.
+.TP
.B ENOMEM
Cannot allocate sufficient memory to copy parts of caller's
context that need to be unshared.
.TP
.B EPERM
The calling process did not have the required privileges for this operation.
+.TP
+.B EPERM
+.BR CLONE_NEWUSER
+was specified in
+.IR flags ,
+but either the effective user ID or the effective group ID of the caller
+does not have a mapping in the parent namespace (see
+.BR user_namespaces (7)).
+.TP
+.BR EPERM " (since Linux 3.9)"
+.\" commit 3151527ee007b73a0ebd296010f1c0454a919c7d
+.B CLONE_NEWUSER was specified in
+.I flags
+and the caller is in a chroot environment
+.\" FIXME What is the rationale for this restriction?
+(i.e., the caller's root directory does not match the root directory
+of the mount namespace in which it resides).
+.TP
+.BR EUSERS " (since Linux 3.11)"
+.B CLONE_NEWUSER
+was specified in
+.IR flags ,
+and the call would cause the limit on the number of
+nested user namespaces to be exceeded.
+See
+.BR user_namespaces (7).
.SH VERSIONS
The
.BR unshare ()
.\"be incrementally added to unshare without affecting legacy
.\"applications using unshare.
.\"
+.SH EXAMPLE
+The program below provides a simple implementation of the
+.BR unshare (1)
+command, which unshares one or more namespaces and executes the
+command supplied in its command-line arguments.
+Here's an example of the use of this program,
+running a shell in a new mount namespace,
+and verifying that the original shell and the
+new shell are in separate mount namespaces:
+.in +4n
+.nf
+
+$ \fBreadlink /proc/$$/ns/mnt\fP
+mnt:[4026531840]
+$ \fBsudo ./unshare -m /bin/bash\fP
+[sudo] password for cecilia:
+# \fBreadlink /proc/$$/ns/mnt\fP
+mnt:[4026532325]
+.fi
+.in
+
+The differing output of the two
+.BR readlink (1)
+commands shows that the two shells are in different mount namespaces.
+.SS Program source
+\&
+.nf
+/* unshare.c
+
+ A simple implementation of the unshare(1) command: unshare
+ namespaces and execute a command.
+*/
+#define _GNU_SOURCE
+#include <sched.h>
+#include <unistd.h>
+#include <stdlib.h>
+#include <stdio.h>
+
+/* A simple error\-handling function: print an error message based
+ on the value in \(aqerrno\(aq and terminate the calling process */
+
+#define errExit(msg) do { perror(msg); exit(EXIT_FAILURE); \\
+ } while (0)
+
+static void
+usage(char *pname)
+{
+ fprintf(stderr, "Usage: %s [options] program [arg...]\\n", pname);
+ fprintf(stderr, "Options can be:\\n");
+ fprintf(stderr, " \-i unshare IPC namespace\\n");
+ fprintf(stderr, " \-m unshare mount namespace\\n");
+ fprintf(stderr, " \-n unshare network namespace\\n");
+ fprintf(stderr, " \-p unshare PID namespace\\n");
+ fprintf(stderr, " \-u unshare UTS namespace\\n");
+ fprintf(stderr, " \-U unshare user namespace\\n");
+ exit(EXIT_FAILURE);
+}
+
+int
+main(int argc, char *argv[])
+{
+ int flags, opt;
+
+ flags = 0;
+
+ while ((opt = getopt(argc, argv, "imnpuU")) != \-1) {
+ switch (opt) {
+ case \(aqi\(aq: flags |= CLONE_NEWIPC; break;
+ case \(aqm\(aq: flags |= CLONE_NEWNS; break;
+ case \(aqn\(aq: flags |= CLONE_NEWNET; break;
+ case \(aqp\(aq: flags |= CLONE_NEWPID; break;
+ case \(aqu\(aq: flags |= CLONE_NEWUTS; break;
+ case \(aqU\(aq: flags |= CLONE_NEWUSER; break;
+ default: usage(argv[0]);
+ }
+ }
+
+ if (optind >= argc)
+ usage(argv[0]);
+
+ if (unshare(flags) == \-1)
+ errExit("unshare");
+
+ execvp(argv[optind], &argv[optind]);
+ errExit("execvp");
+}
+.fi
.SH SEE ALSO
+.BR unshare (1),
.BR clone (2),
.BR fork (2),
.BR kcmp (2),
.BR setns (2),
-.BR vfork (2)
+.BR vfork (2),
+.BR namespaces (7)
.I Documentation/unshare.txt
in the Linux kernel source tree
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR capabilities (7),
.BR ld.so (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR stat (2),
.BR statfs (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 2004-06-23 by Michael Kerrisk <mtk.manpages@gmail.com>
.\" Modified 2004-10-10 by Andries Brouwer <aeb@cwi.nl>
.\"
-.TH UTIME 2 2014-02-21 "Linux" "Linux Programmer's Manual"
+.TH UTIME 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
utime, utimes \- change file last access and modification times
.SH SYNOPSIS
Linux does not allow changing the timestamps on an immutable file,
or setting the timestamps to something other than the current time
on an append-only file.
-
-In libc4 and libc5,
-.BR utimes ()
-is just a wrapper for
-.BR utime ()
-and hence does not allow a subsecond resolution.
+.\"
+.\" In libc4 and libc5,
+.\" .BR utimes ()
+.\" is just a wrapper for
+.\" .BR utime ()
+.\" and hence does not allow a subsecond resolution.
.SH SEE ALSO
.BR chattr (1),
.BR futimesat (2),
.BR futimens (3),
.BR futimes (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR path_resolution (7),
.BR symlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR unshare (2),
.BR wait (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
intended to be portable.
.SH SEE ALSO
.BR capabilities (7),
-.BR init (8)
+.BR init (1)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
This call is specific to Linux on 32-bit Intel processors,
and should not be used in programs intended to be portable.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH VMSPLICE 2 2012-05-04 "Linux" "Linux Programmer's Manual"
+.TH VMSPLICE 2 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
vmsplice \- splice user pages into a pipe
.SH SYNOPSIS
.B SPLICE_F_GIFT
The user pages are a gift to the kernel.
The application may not modify this memory ever,
-.\" FIXME Explain the following line in a little more detail:
+.\" FIXME . Explain the following line in a little more detail:
or page cache and on-disk data may differ.
Gifting pages to the kernel means that a subsequent
.BR splice (2)
is set to indicate the error.
.SH ERRORS
.TP
+.B EAGAIN
+.B SPLICE_F_NONBLOCK
+was specified in
+.IR flags ,
+and the operation would block.
+.TP
.B EBADF
.I fd
either not valid, or doesn't refer to a pipe.
.TP
.B EINVAL
.I nr_segs
-is 0 or greater than
+is greater than
.BR IOV_MAX ;
or memory not aligned if
.B SPLICE_F_GIFT
.BR splice (2),
.BR tee (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2005-05-10, mtk, __W* flags can't be used with waitid()
.\" 2008-07-04, mtk, removed erroneous text about SA_NOCLDSTOP
.\"
-.TH WAIT 2 2013-09-04 "Linux" "Linux Programmer's Manual"
+.TH WAIT 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
wait, waitpid, waitid \- wait for process to change state
.SH SYNOPSIS
.I id
has yet changed state;
on error, \-1 is returned.
-.\" FIXME: As reported by Vegard Nossum, if infop is NULL, then waitid()
+.\" FIXME As reported by Vegard Nossum, if infop is NULL, then waitid()
.\" returns the PID of the child. Either this is a bug, or it is intended
.\" behavior that needs to be documented. See my Jan 2009 LKML mail
.\" "waitid() return value strangeness when infop is NULL".
+.PP
Each of these calls sets
.I errno
to an appropriate value in the case of an error.
this table fills, it will not be possible to create further processes.
If a parent process terminates, then its "zombie" children (if any)
are adopted by
-.BR init (8),
+.BR init (1),
which automatically performs a wait to remove the zombies.
POSIX.1-2001 specifies that if the disposition of
Do not wait for children of other threads in
the same thread group.
This was the default before Linux 2.4.
-.PP
+.SS C library/kernel ABI differences
The raw
.BR waitid ()
-system call takes a fith argument, of type
+system call takes a fifth argument, of type
.IR "struct rusage\ *" .
If this argument is non-NULL,
then it is used to return resource usage information about the child,
.BR credentials (7),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wait (2),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR writev (2),
.BR fwrite (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_setaffinity_np (3),
.BR cpuset (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR fpclassify (3),
.BR math_error (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wcstombs (3),
.BR wctomb (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR MB_CUR_MAX (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.br
.I <fpu_control.h>
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" .BR itoa (3),
.BR strtoul (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR longjmp (3),
.BR raise (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified Sat Jul 24 21:45:37 1993, Rik Faith (faith@cs.unc.edu)
.\" Modified Sat Dec 16 15:02:59 2000, Joseph S. Myers
.\"
-.TH ABS 3 2013-06-21 "GNU" "Linux Programmer's Manual"
+.TH ABS 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
abs, labs, llabs, imaxabs \- compute the absolute value of an integer
.SH SYNOPSIS
.PP
The
.BR llabs ()
-function is included in glibc since version 2.0, but
-is not in libc5 or libc4.
+function is included in glibc since version 2.0.
The
.BR imaxabs ()
function is included in
\fB_ISOC99_SOURCE\fP or \fB_ISOC9X_SOURCE\fP (depending on the
version of glibc) before including any standard headers.
.PP
+By default,
GCC handles
-.BR abs ()
-and
-.BR labs ()
-as built-in functions.
-GCC 3.0 also handles
+.BR abs (),
+.BR labs (),
+and (since GCC 3.0)
.BR llabs ()
and
.BR imaxabs ()
-as built-ins.
+as built-in functions.
.SH SEE ALSO
.BR cabs (3),
.BR ceil (3),
.BR floor (3),
.BR rint (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sin (3),
.BR tan (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sinh (3),
.BR tanh (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR fmtmsg (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.TP
.B EPERM
The caller does not have sufficient privilege to adjust the time.
-Under Linux the
+Under Linux, the
.B CAP_SYS_TIME
capability is required.
.SH ATTRIBUTES
.BR gettimeofday (2),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR lio_listio (3),
.BR aio (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR lio_listio (3),
.BR aio (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR aio (7),
.BR sigevent (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
that the caller expects to enqueue.
If a value less than 32 is specified for this field,
it is rounded up to 32.
-.\" FIXME But, if aio_num > 32, the behavior looks strange. See
+.\" FIXME . But, if aio_num > 32, the behavior looks strange. See
.\" http://sourceware.org/bugzilla/show_bug.cgi?id=12083
The default value is 64.
.TP
.SH SEE ALSO
.BR aio (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR lio_listio (3),
.BR aio (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR lio_listio (3),
.BR aio (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR aio (7),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR lio_listio (3),
.BR aio (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR longjmp (3),
.BR malloc (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR envz_add (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sin (3),
.BR tan (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sinh (3),
.BR tanh (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR malloc (3),
.BR printf (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR assert_perror (3),
.BR exit (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR exit (3),
.BR strerror (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sin (3),
.BR tan (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sin (3),
.BR tan (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sinh (3),
.BR tanh (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR exit (3),
.BR on_exit (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strtol (3),
.BR strtoul (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified Sat Jul 24 21:38:42 1993, Rik Faith (faith@cs.unc.edu)
.\" Modified Sun Dec 17 18:35:06 2000, Joseph S. Myers
.\"
-.TH ATOI 3 2014-01-22 "GNU" "Linux Programmer's Manual"
+.TH ATOI 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
-atoi, atol, atoll, atoq \- convert a string to an integer
+atoi, atol, atoll \- convert a string to an integer
.SH SYNOPSIS
.nf
.B #include <stdlib.h>
.BI "long atol(const char *" nptr );
.br
.BI "long long atoll(const char *" nptr );
-.br
-.BI "long long atoq(const char *" nptr );
.fi
.sp
.in -4n
.BR atoi (),
except that they convert the initial portion of the
string to their return type of \fIlong\fP or \fIlong long\fP.
-.BR atoq ()
-is an obsolete name for
-.BR atoll ().
.SH RETURN VALUE
The converted value.
.SH ATTRIBUTES
and
.BR atol ()
only.
-.BR atoq ()
-is a GNU extension.
.SH NOTES
-The nonstandard
+Linux libc provided
.BR atoq ()
-function is not present in libc 4.6.27
-or glibc 2, but is present in libc5 and libc 4.7 (though only as an
-inline function in \fI<stdlib.h>\fP until libc 5.4.44).
-The
-.BR atoll ()
-function is present in glibc 2 since version 2.0.2, but
-not in libc4 or libc5.
+as an obsolete name for
+.BR atoll ();
+.BR atoq ()
+is not provided by glibc.
+.\" The
+.\" .BR atoll ()
+.\" function is present in glibc 2 since version 2.0.2, but
+.\" not in libc4 or libc5.
.SH SEE ALSO
.BR atof (3),
.BR strtod (3),
.BR strtol (3),
.BR strtoul (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR dlopen (3),
.BR malloc (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\" Created, 14 Dec 2000 by Michael Kerrisk
.\"
-.TH BASENAME 3 2009-03-30 "GNU" "Linux Programmer's Manual"
+.TH BASENAME 3 2014-06-13 "GNU" "Linux Programmer's Manual"
.SH NAME
basename, dirname \- parse pathname components
.SH SYNOPSIS
return pointers to null-terminated strings.
(Do not pass these pointers to
.BR free (3).)
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR basename ()
+and
+.BR dirname ()
+functions are thread-safe.
.SH CONFORMING TO
POSIX.1-2001.
.SH NOTES
.BR basename (1),
.BR dirname (1)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strncasecmp (3),
.BR strncmp (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strcpy (3),
.BR strncpy (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" commit f6da27e53695ad1cc0e2a9490358decbbfdff5e5
the
.BR bindresvport ()
-function uses a lock to protect static variable, so it is thread-safe.
+function uses a lock to protect the static variable, so it is thread-safe.
.SH CONFORMING TO
Not in POSIX.1-2001.
Present on the BSDs, Solaris, and many other systems.
.BR bind (2),
.BR getsockname (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sysv_signal (3),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR qsort (3),
.BR tsearch (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR memmove (3),
.BR memset (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mbtowc (3),
.BR wctob (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.IR "The Art of Computer Programming Vol. 3: Sorting and Searching" ,
D.E. Knuth, 1968, pp 471-480.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR gethostbyname (3),
.BR getservent (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR memset (3),
.BR swab (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR hypot (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR clog (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR cimag (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR readlink (2),
.BR realpath (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR cabs (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR csin (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR csinh (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ctan (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ctanh (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" %%%LICENSE_END
.\"
.\" Updated, aeb, 980809
-.TH CATGETS 3 2013-06-21 "" "Linux Programmer's Manual"
+.TH CATGETS 3 2014-06-13 "" "Linux Programmer's Manual"
.SH NAME
catgets \- get message from a message catalog
.SH SYNOPSIS
.BR catgets ()
returns the value
.IR message .
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR catgets ()
+function is thread-safe.
.SH CONFORMING TO
POSIX.1-2001.
.SH NOTES
-These functions are available only in libc.so.4.4.4c and above.
+The
+.BR catgets ()
+function is available only in libc.so.4.4.4c and above.
The Jan 1987 X/Open Portability Guide specifies a more subtle
error return:
.I message
.BR catopen (3),
.BR setlocale (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified Thu Dec 13 22:51:19 2001 by Martin Schulze <joey@infodrom.org>
.\" Modified 2001-12-14 aeb
.\"
-.TH CATOPEN 3 2001-12-14 "GNU" "Linux Programmer's Manual"
+.TH CATOPEN 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
catopen, catclose \- open/close a message catalog
.SH SYNOPSIS
.\" In XPG 1987, Vol. 3 it says:
.\" .I "The flag argument of catopen is reserved for future use"
.\" .IR "and should be set to 0" .
-It is unclear what the source was for the constants
-.B MCLoadBySet
-and
-.B MCLoadAll
-(see below).
+.\"
+.\" It is unclear what the source was for the constants
+.\" .B MCLoadBySet
+.\" and
+.\" .B MCLoadAll
+.\" (see below).
.SH NOTES
The above is the POSIX.1-2001 description.
The glibc value for
.B NL_CAT_LOCALE
is 1.
-(Compare
-.B MCLoadAll
-below.)
+.\" (Compare
+.\" .B MCLoadAll
+.\" below.)
The default path varies, but usually looks at a number of places below
.IR /usr/share/locale .
-.SS Linux notes
-These functions are available for Linux since libc 4.4.4c.
-In the case of linux libc4 and libc5, the catalog descriptor
-.I nl_catd
-is a
-.BR mmap (2)'ed
-area of memory and not a file descriptor.
-The
-.I flag
-argument to
-.BR catopen ()
-should be either
-.B MCLoadBySet
-(=0) or
-.B MCLoadAll
-(=1).
-The former value indicates that a set from the catalog is to be
-loaded when needed, whereas the latter causes the initial call to
-.BR catopen ()
-to load the entire catalog into memory.
-The default search path varies, but usually looks at a number of places below
-.I /etc/locale
-and
-.IR /usr/lib/locale .
+.\" .SS Linux notes
+.\" These functions are available for Linux since libc 4.4.4c.
+.\" In the case of linux libc4 and libc5, the catalog descriptor
+.\" .I nl_catd
+.\" is a
+.\" .BR mmap (2)'ed
+.\" area of memory and not a file descriptor.
+.\" The
+.\" .I flag
+.\" argument to
+.\" .BR catopen ()
+.\" should be either
+.\" .B MCLoadBySet
+.\" (=0) or
+.\" .B MCLoadAll
+.\" (=1).
+.\" The former value indicates that a set from the catalog is to be
+.\" loaded when needed, whereas the latter causes the initial call to
+.\" .BR catopen ()
+.\" to load the entire catalog into memory.
+.\" The default search path varies, but usually looks at a number of places below
+.\" .I /etc/locale
+.\" and
+.\" .IR /usr/lib/locale .
.SH SEE ALSO
.BR catgets (3),
.BR setlocale (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pow (3),
.BR sqrt (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ctan (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ctanh (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR round (3),
.BR trunc (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Distributed under GPL
.\" %%%LICENSE_END
.\"
-.TH CERF 3 2010-09-12 "" "Linux Programmer's Manual"
+.TH CERF 3 2014-08-19 "" "Linux Programmer's Manual"
.SH NAME
cerf, cerff, cerfl, cerfc, cerfcf, cerfcl \- complex error function
.SH SYNOPSIS
.SH CONFORMING TO
The function names are reserved for future use in C99.
.SH AVAILABILITY
-Not yet in glibc, as at version 2.12.
+Not yet in glibc, as at version 2.19.
.\" But reserved in NAMESPACE.
.SH SEE ALSO
.BR erf (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR cpow (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Distributed under GPL
.\" %%%LICENSE_END
.\"
-.TH CEXP2 3 2013-02-27 "" "Linux Programmer's Manual"
+.TH CEXP2 3 2014-08-19 "" "Linux Programmer's Manual"
.SH NAME
cexp2, cexp2f, cexp2l \- base-2 exponent of a complex number
.SH SYNOPSIS
.SH CONFORMING TO
These function names are reserved for future use in C99.
.SH AVAILABILITY
-Not yet in glibc, as at version 2.17.
+Not yet in glibc, as at version 2.19.
.\" But reserved in NAMESPACE.
.SH SEE ALSO
.BR cabs (3),
.BR clog10 (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR malloc (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR creal (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" %%%LICENSE_END
.\"
.\" Additions, aeb, 2001-10-17.
-.TH CLEARENV 3 2010-10-04 "Linux" "Linux Programmer's Manual"
+.TH CLEARENV 3 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
clearenv \- clear the environment
.SH SYNOPSIS
.\" Most versions of UNIX return -1 on error, or do not even have errors.
.\" Glibc info and the Watcom C library document "a nonzero value".
.SH VERSIONS
-Not in libc4, libc5.
-In glibc since glibc 2.0.
+Available since glibc 2.0.
.SH CONFORMING TO
Various UNIX variants (DG/UX, HP-UX, QNX, ...).
POSIX.9 (bindings for FORTRAN77).
.BR unsetenv (3),
.BR environ (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 14 Jun 2002, Michael Kerrisk <mtk.manpages@gmail.com>
.\" Added notes on differences from other UNIX systems with respect to
.\" waited-for children.
-.TH CLOCK 3 2013-08-19 "GNU" "Linux Programmer's Manual"
+.TH CLOCK 3 2014-09-21 "GNU" "Linux Programmer's Manual"
.SH NAME
clock \- determine processor time
.SH SYNOPSIS
.BR clock ()
was implemented on top of
.BR times (2).
-For improved precision,
+For improved accuracy,
since glibc 2.18, it is implemented on top of
.BR clock_gettime (2)
(using the
.BR getrusage (2),
.BR times (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_getcpuclockid (3),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR clog2 (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR clog2 (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Distributed under GPL
.\" %%%LICENSE_END
.\"
-.TH CLOG2 3 2013-07-23 "" "Linux Programmer's Manual"
+.TH CLOG2 3 2014-08-19 "" "Linux Programmer's Manual"
.SH NAME
clog2, clog2f, clog2l \- base-2 logarithm of a complex number
.SH SYNOPSIS
.SH CONFORMING TO
These function names are reserved for future use in C99.
.SH AVAILABILITY
-Not yet in glibc, as at version 2.17.
+Not yet in glibc, as at version 2.19.
.\" But reserved in NAMESPACE.
.SH SEE ALSO
.BR cabs (3),
.BR clog10 (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR seekdir (3),
.BR telldir (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.IR msghdr .
.SH CONFORMING TO
This ancillary data model conforms to the POSIX.1g draft, 4.4BSD-Lite,
-the IPv6 advanced API described in RFC\ 2292 and the SUSv2.
+the IPv6 advanced API described in RFC\ 2292 and SUSv2.
.BR CMSG_ALIGN ()
is a Linux extension.
.SH NOTES
.PP
RFC\ 2292
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" See <bits/confname.h> for the rest.
.\" These should all be added to this page.
.\" See also the POSIX.1-2001 specification of confstr()
+.\"
.TH CONFSTR 3 2014-03-20 "GNU" "Linux Programmer's Manual"
.SH NAME
confstr \- get configuration dependent string variables
.BR pathconf (3)
.BR system (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR csqrt (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR signbit (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sincos (3),
.BR tan (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sinh (3),
.BR tanh (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pow (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR cabs (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR cimag (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getpass (3),
.BR passwd (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ctan (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ctanh (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR cexp (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR csin (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR csinh (3),
.BR complex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR ttyname (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 2001-12-13, joey, aeb
.\" Modified 2004-11-16, mtk
.\"
-.TH CTIME 3 2013-12-30 "" "Linux Programmer's Manual"
+.TH CTIME 3 2014-08-19 "" "Linux Programmer's Manual"
.SH NAME
asctime, ctime, gmtime, localtime, mktime, asctime_r, ctime_r, gmtime_r,
localtime_r \- transform date and time to broken-down time or ASCII
and
.BR localtime ()
return a pointer to static data and hence are not thread-safe.
-Thread-safe versions
+The thread-safe versions,
.BR asctime_r (),
.BR ctime_r (),
.BR gmtime_r ()
and
-.BR localtime_r ()
-are specified by SUSv2, and available since libc 5.2.5.
+.BR localtime_r (),
+are specified by SUSv2.
POSIX.1-2001 says:
"The
.BR tzset (3),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR fork (2),
.BR setsid (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
The formats and file-format-specific information are described in detail
in their respective manual pages
.BR btree (3),
-.BR hash (3)
+.BR hash (3),
and
.BR recno (3).
.PP
.IR "LIBTP: Portable, Modular Transactions for UNIX" ,
Margo Seltzer, Michael Olson, USENIX proceedings, Winter 1992.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" can be distributed under GPL.
.\" %%%LICENSE_END
.\"
-.TH DES_CRYPT 3 2013-09-18 "" "Linux Programmer's Manual"
+.TH DES_CRYPT 3 2014-08-19 "" "Linux Programmer's Manual"
.SH NAME
des_crypt, ecb_crypt, cbc_crypt, des_setparity, DES_FAILED \- fast
DES encryption
.\" So far the Sun page
.\" Some additions - aeb
.SH VERSIONS
-These routines are present in libc 4.6.27 and later, and in
+These functions are present in
glibc 2.1 and later.
.SH ATTRIBUTES
.SS Multithreading (see pthreads(7))
.BR crypt (3),
.BR xcrypt (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR gmtime (3),
.BR localtime (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR seekdir (3),
.BR telldir (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR abs (3),
.BR remainder (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.IR "Executable and Linking Format Specification" ,
available at various locations online.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified by Walter Harms: dladdr, dlvsym
.\" Modified by Petr Baudis <pasky@suse.cz>, 2008-12-04: dladdr caveat
.\"
-.TH DLOPEN 3 2014-01-08 "Linux" "Linux Programmer's Manual"
+.TH DLOPEN 3 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
dladdr, dlclose, dlerror, dlopen, dlsym, dlvsym \- programming interface to
dynamic linking loader
.SH SEE ALSO
.BR ld (1),
.BR ldd (1),
+.BR pldd (1),
.BR dl_iterate_phdr (3),
.BR rtld-audit (7),
.BR ld.so (8),
ld.so info pages, gcc info pages, ld info pages
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR printf (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Lewine's _POSIX Programmer's Guide_ (O'Reilly & Associates, 1991)
.\" 386BSD man pages
.\" Modified Sat Jul 24 19:46:03 1993 by Rik Faith (faith@cs.unc.edu)
-.TH DRAND48 3 2013-06-21 "" "Linux Programmer's Manual"
+.TH DRAND48 3 2014-09-21 "" "Linux Programmer's Manual"
.SH NAME
drand48, erand48, lrand48, nrand48, mrand48, jrand48, srand48, seed48,
lcong48 \- generate uniformly distributed pseudo-random numbers
so they are not thread-safe.
.SH CONFORMING TO
SVr4, POSIX.1-2001.
-.SH NOTES
-These functions are declared obsolete by SVID 3, which states that
-.BR rand (3)
-should be used instead.
.SH SEE ALSO
.BR rand (3),
.BR random (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR rand (3),
.BR random (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR locale (5),
.BR locale (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR strftime (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified Sat Jul 24 19:40:39 1993 by Rik Faith (faith@cs.unc.edu)
.\" Modified Fri Jun 25 12:10:47 1999 by Andries Brouwer (aeb@cwi.nl)
.\"
-.TH ECVT 3 2013-07-04 "" "Linux Programmer's Manual"
+.TH ECVT 3 2014-08-19 "" "Linux Programmer's Manual"
.SH NAME
ecvt, fcvt \- convert a floating-point number to a string
.SH SYNOPSIS
.BR snprintf (3)
may be preferable).
.SH NOTES
-Linux libc4 and libc5 specified the type of
-.I ndigits
-as
-.IR size_t .
+.\" Linux libc4 and libc5 specified the type of
+.\" .I ndigits
+.\" as
+.\" .IR size_t .
Not all locales use a point as the radix character ("decimal point").
.SH SEE ALSO
.BR ecvt_r (3),
.BR setlocale (3),
.BR sprintf (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
The functions
.BR ecvt_r (),
.BR fcvt_r (),
-.BR qecvt_r ()
+.BR qecvt_r (),
and
.BR qfcvt_r ()
are identical to
.BR ecvt (3),
.BR fcvt (3),
-.BR qecvt (3)
+.BR qecvt (3),
and
.BR qfcvt (3),
respectively, except that they do not return their result in a static
.BR qecvt (3),
.BR sprintf (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR setkey_r ()
are GNU extensions.
.SH NOTES
-In glibc 2.2 these functions use the DES algorithm.
+In glibc 2.2, these functions use the DES algorithm.
.SH EXAMPLE
You need to link with libcrypt to compile this example with glibc.
-To do useful work the
+To do useful work, the
.I key[]
and
.I txt[]
.BR ecb_crypt (3),
.\" .BR fcrypt (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sbrk (2),
.BR elf (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR byteorder (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR argz_add (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR erfc (3),
.BR exp (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR erf (3),
.BR exp (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR printf (3),
.BR strerror (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2006-02-09 Kurt Wall, mtk
.\" Added non-POSIX errors
.\"
-.TH ERRNO 3 2008-07-09 "" "Linux Programmer's Manual"
+.TH ERRNO 3 2014-09-06 "" "Linux Programmer's Manual"
.SH NAME
errno \- number of last error
.SH SYNOPSIS
.I <errno.h>
and the declaration is needed.
.SH SEE ALSO
+.BR errno (1), \" In the moreutils package
.BR err (3),
.BR error (3),
.BR perror (3),
.BR strerror (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR program_invocation_name (3),
.BR strerror (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\" Minor additions, aeb, 2013-06-21
.\"
-.TH ETHER_ATON 3 2013-07-04 "GNU" "Linux Programmer's Manual"
+.TH ETHER_ATON 3 2014-07-08 "GNU" "Linux Programmer's Manual"
.SH NAME
ether_aton, ether_ntoa, ether_ntohost, ether_hostton, ether_line,
ether_ntoa_r, ether_aton_r \- Ethernet address manipulation routines
.fi
.in
.SH ATTRIBUTES
-.SS Multithreading (see pthreads(7))
-The
-.BR ether_aton ()
-and
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.ad l
+.TS
+allbox;
+lbw33 lb lb
+l l l.
+Interface Attribute Value
+T{
+.BR ether_aton (),
.BR ether_ntoa ()
-functions are not thread-safe.
-.LP
-The
+T} Thread safety MT-Unsafe
+T{
.BR ether_ntohost (),
.BR ether_hostton (),
.BR ether_line (),
-.BR ether_ntoa_r ()
-and
+.BR ether_ntoa_r (),
.BR ether_aton_r ()
-functions are thread-safe.
+T} Thread safety MT-Safe
+.TE
+.ad
.SH CONFORMING TO
4.3BSD, SunOS.
.SH BUGS
-The glibc 2.2.5 implementation of
+In glibc 2.2.5 and earlier, the implementation of
.BR ether_line ()
+.\" The fix was presumably commit c0a0f9a32c8baa6ab93d00eb42d92c02e9e146d7
+.\" which was in glibc 2.3
is broken.
.SH SEE ALSO
.BR ethers (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
checks permissions and existence of the file identified by its argument
.IR pathname .
However, whereas
-.BR access (2),
+.BR access (2)
performs checks using the real user and group identifiers of the process,
.BR euidaccess ()
uses the effective identifiers.
.BR credentials (7),
.BR path_resolution (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR fexecve (3),
.BR environ (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.\" FIXME There are a lot of other process termination actions that
+.\" FIXME . There are a lot of other process termination actions that
.\" could be listed on this page. See, for example, the list in the
.\" POSIX exit(3p) page.
.\"
.BR on_exit (3),
.BR tmpfile (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR exp2 (3),
.BR sqrt (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR log10 (3),
.BR sqrt (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR exp10 (3),
.BR sqrt (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR log (3),
.BR log1p (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR labs (3),
.BR rint (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR fopen (3),
.BR setbuf (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR fopen (3),
.BR setbuf (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR fmax (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR math_error (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR stdio (3),
.BR unlocked_stdio (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR execve (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR setbuf (3),
.BR unlocked_stdio (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR memchr (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR unlocked_stdio (3),
.BR feature_test_macros (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Lewine's _POSIX Programmer's Guide_ (O'Reilly & Associates, 1991)
.\" 386BSD man pages
.\" Modified Sat Jul 24 19:38:44 1993 by Rik Faith (faith@cs.unc.edu)
-.TH FGETGRENT 3 2013-04-19 "GNU" "Linux Programmer's Manual"
+.TH FGETGRENT 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
fgetgrent \- get group file entry
.SH SYNOPSIS
char *gr_name; /* group name */
char *gr_passwd; /* group password */
gid_t gr_gid; /* group ID */
- char **gr_mem; /* group members */
+ char **gr_mem; /* NULL-terminated array of pointers
+ to names of group members */
};
.fi
.in
.BR setgrent (3),
.BR group (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR setpwent (3),
.BR passwd (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ungetwc (3),
.BR unlocked_stdio (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR fgetwc (3),
.BR unlocked_stdio (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR fpclassify (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH FLOCKFILE 3 2013-07-23 "" "Linux Programmer's Manual"
+.TH FLOCKFILE 3 2014-08-19 "" "Linux Programmer's Manual"
.SH NAME
flockfile, ftrylockfile, funlockfile \- lock FILE for stdio
.SH SYNOPSIS
These functions are available when
.B _POSIX_THREAD_SAFE_FUNCTIONS
is defined.
-They are in libc since libc 5.1.1 and in glibc
-since glibc 2.0.
.SH SEE ALSO
.BR unlocked_stdio (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR round (3),
.BR trunc (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR remainder (3),
.BR remquo (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR fmin (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR fmemopen ()
fails with the error
.BR EINVAL .
-.\" FIXME http://sourceware.org/bugzilla/show_bug.cgi?id=11216
+.\" FIXME . http://sourceware.org/bugzilla/show_bug.cgi?id=11216
It would be more consistent if this case successfully created
a stream that then returned end of file on the first attempt at reading.
Furthermore, POSIX.1-2008 does not specify a failure for this case.
Specifying append mode ("a" or "a+") for
.BR fmemopen ()
sets the initial file position to the first null byte, but
-.\" FIXME http://sourceware.org/bugzilla/show_bug.cgi?id=13152
+.\" FIXME . http://sourceware.org/bugzilla/show_bug.cgi?id=13152
(if the file offset is reset to a location other than
the end of the stream)
does not force subsequent writes to append at the end of the stream.
the initial file position should be set to
the next byte after the end of the buffer.
However, in this case the glibc
-.\" FIXME http://sourceware.org/bugzilla/show_bug.cgi?id=13151
+.\" FIXME . http://sourceware.org/bugzilla/show_bug.cgi?id=13151
.BR fmemopen ()
sets the file position to \-1.
.IR mode .
Thus, for example, "wb+" has the desired effect, but "w+b" does not.
This is inconsistent with the treatment of
-.\" FIXME http://sourceware.org/bugzilla/show_bug.cgi?id=12836
+.\" FIXME . http://sourceware.org/bugzilla/show_bug.cgi?id=12836
.IR mode
by
.BR fopen (3).
.BR fopen (3),
.BR fopencookie (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR fmax (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR remainder (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR addseverity (3),
.BR perror (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wordexp (3),
.BR glob (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.I errno
for any of the errors specified for the routines
.BR open (2),
-.BR fclose (3)
+.BR fclose (3),
and
.BR fflush (3).
.SH CONFORMING TO
.TP
.B x
.\" Since glibc 2.0?
-.\" FIXME C11 specifies this flag
+.\" FIXME . C11 specifies this flag
Open the file exclusively
(like the
.B O_EXCL
.IR mode
(i.e., the characters preceding the "ccs" specification),
the glibc implementation of
-.\" FIXME http://sourceware.org/bugzilla/show_bug.cgi?id=12685
+.\" FIXME . http://sourceware.org/bugzilla/show_bug.cgi?id=12685
.BR fopen ()
and
.BR freopen ()
.BR fmemopen (3),
.BR fopencookie (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR fopen (3),
.BR fseek (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR confstr (3),
.BR sysconf (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR isgreater (3),
.BR signbit (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR setbuf (3),
.BR stdio_ext (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR fputws (3),
.BR unlocked_stdio (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR fputwc (3),
.BR unlocked_stdio (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ferror (3),
.BR unlocked_stdio (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ldexp (3),
.BR modf (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR lseek (2),
.BR fseeko (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH FSEEKO 3 2014-03-20 "" "Linux Programmer's Manual"
+.TH FSEEKO 3 2014-10-02 "" "Linux Programmer's Manual"
.SH NAME
fseeko, ftello \- seek to or report file position
.SH SYNOPSIS
instead of
.IR long .
.LP
-On many architectures both
+On some architectures, both
.IR off_t
and
.I long
-are 32-bit types,
-but compilation with
-.RS
-.nf
-
-#define _FILE_OFFSET_BITS 64
-.fi
-.RE
-.PP
+are 32-bit types, but defining
+.BR _FILE_OFFSET_BITS
+with the value 64 (before including
+.I any
+header files)
will turn
.I off_t
into a 64-bit type.
.SH ERRORS
See the ERRORS in
.BR fseek (3).
+.SH VERSIONS
+These functions are available under glibc since version 2.1.
.SH CONFORMING TO
SUSv2, POSIX.1-2001.
.SH NOTES
These functions are found on System V-like systems.
-They are not present in libc4, libc5, glibc 2.0
-but are available since glibc 2.1.
.SH SEE ALSO
.BR fseek (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified Sun Oct 18 17:31:43 1998 by Andries Brouwer (aeb@cwi.nl)
.\" 2008-06-23, mtk, minor rewrites, added some details
.\"
-.TH FTIME 3 2013-09-26 "GNU" "Linux Programmer's Manual"
+.TH FTIME 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
ftime \- return date and time
.SH SYNOPSIS
gives nanoseconds but is not as widely available.
.SH BUGS
.LP
-Under libc4 and libc5 the \fImillitm\fP field is meaningful.
-But early glibc2 is buggy and returns 0 there;
+Early glibc2 is buggy and returns 0 in the
+.I millitm
+field;
glibc 2.1.1 is correct again.
.\" .SH HISTORY
.\" The
.BR gettimeofday (2),
.BR time (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Changed data type of proj_id; minor fixes
.\" aeb: further fixes; added notes.
.\"
-.TH FTOK 3 2013-10-07 "GNU" "Linux Programmer's Manual"
+.TH FTOK 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
ftok \- convert a pathname and a project identifier to a System V IPC key
.SH SYNOPSIS
.SH CONFORMING TO
POSIX.1-2001.
.SH NOTES
-Under libc4 and libc5 (and under SunOS 4.x) the prototype was:
+On some ancient systems, the prototype was:
.sp
.RS
.BI "key_t ftok(char *" pathname ", char " proj_id );
.RE
.PP
-Today
+Today,
.I proj_id
is an
.IR int ,
.I proj_id
is zero.
.LP
-Of course no guarantee can be given that the resulting
+Of course, no guarantee can be given that the resulting
.I key_t
is unique.
-Typically, a best effort attempt combines the given
+Typically, a best-effort attempt combines the given
.I proj_id
byte, the lower 16 bits of the inode number, and the
lower 8 bits of the device number into a 32-bit result.
.BR stat (2),
.BR svipc (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR chdir (2),
.BR malloc (3),
.BR opendir (3),
-.BR readdir (3)
+.BR readdir (3),
and
.BR stat (2).
.PP
In addition,
.BR fts_children (),
-.BR fts_open ()
+.BR fts_open (),
and
.BR fts_set ()
may fail and set
.BR ftw (3),
.BR qsort (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" reorganized and rewrote much of the page
.\" 2006-05-24, Michael Kerrisk <mtk.manpages@gmail.com>
.\" Added an example program.
-.TH FTW 3 2014-01-11 "Linux" "Linux Programmer's Manual"
+.TH FTW 3 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
ftw, nftw \- file tree walk
.SH SYNOPSIS
to terminate the tree walk is \fBFTW_STOP\fP,
and that value is returned as the result of
.BR nftw ().
+.SH VERSIONS
+.BR nftw ()
+is available under glibc since version 2.1.
.SH CONFORMING TO
POSIX.1-2001, SVr4, SUSv1.
POSIX.1-2008 marks
For predictable control, use
.BR nftw ().
.LP
-Under Linux, libc4 and libc5 and glibc 2.0.6 will
-use \fBFTW_F\fP for all objects (files, symbolic links, FIFOs, etc.)
+\fBFTW_F\fP is returned for all objects (files, symbolic links, FIFOs, etc.)
that can be stat'ed but are not a directory.
-The function
-.BR nftw ()
-is available since glibc 2.1.
-
\fBFTW_ACTIONRETVAL\fP is glibc-specific.
.SH EXAMPLE
The following program traverses the directory tree under the path named
.BR fts (3),
.BR readdir (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR utimensat (2),
.BR symlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR fprintf (3),
.BR fwprintf (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR signgam (3),
.BR tgamma (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR fcvt (3),
.BR sprintf (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.fi
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2008-06-18, mtk: many parts rewritten
.\" 2008-12-04, Petr Baudis <pasky@suse.cz>
.\" Describe results ordering and reference /etc/gai.conf.
+.\"
.\" FIXME . glibc's 2.9 NEWS file documents DCCP and UDP-lite support
.\" and is SCTP support now also there?
.\"
.BR hostname (7),
.BR ip (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ip (7),
.BR sigevent (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\" See also https://lwn.net/Articles/519085/
.\"
-.\" FIXME glibc 2.18 added AT_HWCAP2
+.\" FIXME glibc 2.18 added AT_HWCAP2, which needs to e documented
.\"
-.TH GETAUXVAL 3 2014-05-28 "GNU" "Linux Programmer's Manual"
+.TH GETAUXVAL 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
getauxval \- retrieve a value from the auxiliary vector
.SH SYNOPSIS
.I type
is not found, 0 is returned.
.SH ERRORS
-No errors are diagnosed.
+.TP
+.BR ENOENT " (since glibc 2.19)"
+.\" commit b9ab448f980e296eac21ac65f53783967cc6037b
+No entry corresponding to
+.IR type
+could be found in the auxiliary vector.
.SH VERSIONS
The
.BR getauxval ()
see
.BR proc (5)
for more information.
+.SH BUGS
+Before the addition of the
+.B ENOENT
+error in glibc 2.19,
+there was no way to unambiguously distinguish the case where
+.I type
+could not be found from the case where the value corresponding to
+.I type
+was zer0.
.SH SEE ALSO
.BR secure_getenv (3),
.BR vdso (7),
.BR ld-linux.so (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
and the four functions
.BR getcontext (),
.BR setcontext (),
-.BR makecontext (3)
+.BR makecontext (3),
and
.BR swapcontext (3)
that allow user-level context switching between multiple
.BR makecontext (3),
.BR sigsetjmp (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified Mon Dec 11 13:32:51 MET 2000 by aeb
.\" Modified Thu Apr 22 03:49:15 CEST 2002 by Roger Luethi <rl@hellgate.ch>
.\"
-.TH GETCWD 3 2010-09-20 "GNU" "Linux Programmer's Manual"
+.TH GETCWD 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
getcwd, getwd, get_current_dir_name \- get current working directory
.SH SYNOPSIS
an application should check for this error, and allocate a larger
buffer if necessary.
.PP
-As an extension to the POSIX.1-2001 standard, Linux (libc4, libc5, glibc)
+As an extension to the POSIX.1-2001 standard, glibc's
.BR getcwd ()
allocates the buffer dynamically using
.BR malloc (3)
.BR free (3),
.BR malloc (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified, 2001-12-26, aeb
.\" 2008-09-07, mtk, Various rewrites; added an example program.
.\"
-.TH GETDATE 3 2014-01-17 "" "Linux Programmer's Manual"
+.TH GETDATE 3 2014-06-13 "" "Linux Programmer's Manual"
.SH NAME
getdate, getdate_r \- convert a date-plus-time string to broken-down time
.SH SYNOPSIS
.SS Program source
\&
.nf
-#define _GNU_SOURCE 500
+#define _GNU_SOURCE
#include <time.h>
#include <stdio.h>
#include <stdlib.h>
.BR strftime (3),
.BR strptime (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH GETDIRENTRIES 3 2007-07-26 "GNU" "Linux Programmer's Manual"
+.TH GETDIRENTRIES 3 2014-06-13 "GNU" "Linux Programmer's Manual"
.SH NAME
getdirentries \- get directory entries in a filesystem-independent format
.SH SYNOPSIS
is set appropriately.
.SH ERRORS
See the Linux library source code for details.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR getdirentries ()
+function is thread-safe.
.SH CONFORMING TO
Not in POSIX.1-2001.
Present on the BSDs, and a few other systems.
.BR lseek (2),
.BR open (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\" Modified 2002-04-15 by Roger Luethi <rl@hellgate.ch> and aeb
.\"
-.TH GETDTABLESIZE 3 2013-02-05 "Linux" "Linux Programmer's Manual"
+.TH GETDTABLESIZE 3 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
getdtablesize \- get descriptor table size
.SH SYNOPSIS
can return any of the errors described for
.BR getrlimit (2);
see NOTES below.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR getdtablesize ()
+function is thread-safe.
.SH CONFORMING TO
SVr4, 4.4BSD (the
.BR getdtablesize ()
limit, or
.B OPEN_MAX
when that fails.
-The libc4 and libc5 versions return
-.B OPEN_MAX
-(set to 256 since Linux 0.98.4).
+.\" The libc4 and libc5 versions return
+.\" .B OPEN_MAX
+.\" (set to 256 since Linux 0.98.4).
.SH SEE ALSO
.BR close (2),
.BR dup (2),
.BR getrlimit (2),
.BR open (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR capabilities (7),
.BR environ (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getmntent (3),
.BR fstab (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Lewine's _POSIX Programmer's Guide_ (O'Reilly & Associates, 1991)
.\" 386BSD man pages
.\" Modified Sat Jul 24 19:29:54 1993 by Rik Faith (faith@cs.unc.edu)
-.TH GETGRENT 3 2013-06-21 "" "Linux Programmer's Manual"
+.TH GETGRENT 3 2014-10-02 "" "Linux Programmer's Manual"
.SH NAME
getgrent, setgrent, endgrent \- get group file entry
.SH SYNOPSIS
.in +4n
.nf
struct group {
- char *gr_name; /* group name */
- char *gr_passwd; /* group password */
- gid_t gr_gid; /* group ID */
- char **gr_mem; /* group members */
+ char *gr_name; /* group name */
+ char *gr_passwd; /* group password */
+ gid_t gr_gid; /* group ID */
+ char **gr_mem; /* NULL-terminated array of pointers
+ to names of group members */
};
.fi
.in
.BR free (3).)
.SH ERRORS
.TP
+.B EAGAIN
+The service was temporarily unavailable; try again later.
+For NSS backends in glibc this indicates a temporary error talking to the backend.
+The error may correct itself, retrying later is suggested.
+.TP
.B EINTR
A signal was caught.
.TP
.B ENFILE
Too many open files in the system.
.TP
+.\" not in POSIX
+.B ENOENT
+A necessary input file cannot be found.
+For NSS backends in glibc this indicates the backend is not correctly configured.
+.TP
.B ENOMEM
.\" not in POSIX
Insufficient memory to allocate
.BR putgrent (3),
.BR group (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
-.TH GETGRENT_R 3 2010-10-21 "GNU" "Linux Programmer's Manual"
+.TH GETGRENT_R 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
getgrent_r, fgetgrent_r \- get group file entry reentrantly
.SH SYNOPSIS
.in +4n
.nf
struct group {
- char *gr_name; /* group name */
- char *gr_passwd; /* group password */
- gid_t gr_gid; /* group ID */
- char **gr_mem; /* group members */
+ char *gr_name; /* group name */
+ char *gr_passwd; /* group password */
+ gid_t gr_gid; /* group ID */
+ char **gr_mem; /* NULL-terminated array of pointers
+ to names of group members */
};
.fi
.in
.BR putgrent (3),
.BR group (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 1993-07-24 by Rik Faith (faith@cs.unc.edu)
.\" Modified 2003-11-15 by aeb
.\"
-.TH GETGRNAM 3 2013-07-22 "" "Linux Programmer's Manual"
+.TH GETGRNAM 3 2014-08-19 "" "Linux Programmer's Manual"
.SH NAME
getgrnam, getgrnam_r, getgrgid, getgrgid_r \- get group file entry
.SH SYNOPSIS
.in +4n
.nf
struct group {
- char *gr_name; /* group name */
- char *gr_passwd; /* group password */
- gid_t gr_gid; /* group ID */
- char **gr_mem; /* group members */
+ char *gr_name; /* group name */
+ char *gr_passwd; /* group password */
+ gid_t gr_gid; /* group ID */
+ char **gr_mem; /* NULL-terminated array of pointers
+ to names of group members */
};
.fi
.in
.BR setgrent (3),
.BR group (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH GETGROUPLIST 3 2008-07-03 "GNU" "Linux Programmer's Manual"
+.TH GETGROUPLIST 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
getgrouplist \- get list of groups to which a user belongs
.SH SYNOPSIS
.BR getgroups (2),
.BR setgroups (2),
.BR getgrent (3),
+.BR group_member (3),
.BR group (5),
.BR passwd (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR named (8)
.\" .BR resolv+ (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR hostid (1),
.BR gethostbyname (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR packet (7),
.BR ifconfig (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR inet_ntop (3),
.BR inet_pton (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH GETLINE 3 2014-04-06 "GNU" "Linux Programmer's Manual"
+.TH GETLINE 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
getline, getdelim \- delimited string input
.SH SYNOPSIS
is NULL, or
.I stream
is not valid).
-.SH VERSIONS
-These functions are available since libc 4.6.27.
.SH CONFORMING TO
Both
.BR getline ()
}
free(line);
+ fclose(fp);
exit(EXIT_SUCCESS);
}
.fi
.BR fread (3),
.BR scanf (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR uptime (1),
.BR proc (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getuid (2),
.BR utmp (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR fstab (5),
.BR mount (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.UR http://www.usenix.org\:/publications\:/library\:/proceedings\:/usenix2000\:/freenix\:/metzprotocol.html
.UE .
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.br
RFC\ 1101
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getnetent (3),
.BR networks (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR getsubopt (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
-.TH GETPASS 3 2013-06-21 "Linux" "Linux Programmer's Manual"
+.TH GETPASS 3 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
getpass \- get a password
.SH SYNOPSIS
Present in SUSv2, but marked LEGACY.
Removed in POSIX.1-2001.
.SH NOTES
-For libc4 and libc5, the prompt is not written to
-.I /dev/tty
-but to
-.IR stderr .
-Moreover, if
-.I /dev/tty
-cannot be opened, the password is read from
-.IR stdin .
-The static buffer has length 128 so that only the first 127
-bytes of the password are returned.
-While reading the password, signal generation
-.RB ( SIGINT ,
-.BR SIGQUIT ,
-.BR SIGSTOP ,
-.BR SIGTSTP )
-is disabled and the corresponding characters
-(usually control-C, control-\e, control-Z and control-Y)
-are transmitted as part of the password.
-Since libc 5.4.19 also line editing is disabled, so that also
-backspace and the like will be seen as part of the password.
+.\" For libc4 and libc5, the prompt is not written to
+.\" .I /dev/tty
+.\" but to
+.\" .IR stderr .
+.\" Moreover, if
+.\" .I /dev/tty
+.\" cannot be opened, the password is read from
+.\" .IR stdin .
+.\" The static buffer has length 128 so that only the first 127
+.\" bytes of the password are returned.
+.\" While reading the password, signal generation
+.\" .RB ( SIGINT ,
+.\" .BR SIGQUIT ,
+.\" .BR SIGSTOP ,
+.\" .BR SIGTSTP )
+.\" is disabled and the corresponding characters
+.\" (usually control-C, control-\e, control-Z and control-Y)
+.\" are transmitted as part of the password.
+.\" Since libc 5.4.19 also line editing is disabled, so that also
+.\" backspace and the like will be seen as part of the password.
.PP
-For glibc2, if
+In the GNU C library implementation, if
.I /dev/tty
cannot be opened, the prompt is written to
.I stderr
There is no limit on the length of the password.
Line editing is not disabled.
.PP
-According to the SUSv2, the value of
+According to SUSv2, the value of
.B PASS_MAX
must be defined in
.I <limits.h>
.BR _SC_PASS_MAX ,
and the function
.BR getpass ().
-Libc4 and libc5 have never supported
-.B PASS_MAX
-or
-.BR _SC_PASS_MAX .
-Glibc2 accepts
+.\" Libc4 and libc5 have never supported
+.\" .B PASS_MAX
+.\" or
+.\" .BR _SC_PASS_MAX .
+The glibc version accepts
.B _SC_PASS_MAX
and returns
.B BUFSIZ
.SH SEE ALSO
.BR crypt (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getservent (3),
.BR protocols (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getprotoent (3),
.BR protocols (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ptmx (4),
.BR pty (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR setpwent (3),
.BR passwd (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR putpwent (3),
.BR passwd (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR putpwent (3),
.BR passwd (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.sp
.BI "int getpwnam_r(const char *" name ", struct passwd *" pwd ,
.br
-.BI " char *" buf ", size_t " buflen ", struct passwd **" result );
+.BI " char *" buf ", size_t " buflen ", struct passwd **" result );
.sp
.BI "int getpwuid_r(uid_t " uid ", struct passwd *" pwd ,
.br
-.BI " char *" buf ", size_t " buflen ", struct passwd **" result );
+.BI " char *" buf ", size_t " buflen ", struct passwd **" result );
.fi
.sp
.in -4n
.BR setpwent (3),
.BR passwd (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR rpcinfo (8),
.BR ypserv (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getrpcent (3),
.BR rpc (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
Not in POSIX.1-2001.
Present on the BSDs, Solaris, and many other systems.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR unlocked_stdio (3),
.BR feature_test_macros (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getservent_r (3),
.BR services (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getservent (3),
.BR services (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getpwnam (3)
and
.BR getpwent (3)).
-.\" FIXME I've commented out the following for the
+.\" FIXME . I've commented out the following for the
.\" moment. The relationship between PAM and nsswitch.conf needs
.\" to be clearly documented in one place, which is pointed to by
.\" the pages for the user, group, and shadow password functions.
.BR getpwnam_r (3),
.BR shadow (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR getopt (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
Not in POSIX.1-2001.
Present on the BSDs, and perhaps other systems.
.SH NOTES
-Under Linux the file
+Under Linux, the file
.IR /etc/ttys ,
and the functions described above, are not used.
.SH SEE ALSO
.BR ttyname (3),
.BR ttyslot (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR umask (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR shells (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified Thu Jul 25 14:43:46 MET DST 1996 by Michael Haardt
.\" <michael@cantor.informatik.rwth-aachen.de>
.\"
-.TH GETUTENT 3 2014-05-28 "" "Linux Programmer's Manual"
+.TH GETUTENT 3 2014-08-19 "" "Linux Programmer's Manual"
.SH NAME
getutent, getutid, getutline, pututline, setutent, endutent,
utmpname \- access utmp file entries
In XPG2 and SVID 2 the function
.BR pututline ()
is documented to return void, and that is what it does on many systems
-(AIX, HP-UX, Linux libc5).
+(AIX, HP-UX).
HP-UX introduces a new function
.BR _pututline ()
with the prototype given above for
-.BR pututline ()
-(also found in Linux libc5).
+.BR pututline ().
.LP
All these functions are obsolete now on non-Linux systems.
POSIX.1-2001, following SUSv1,
.BR getutmp (3),
.BR utmp (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getutent (3),
.BR utmp (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getc (3),
.BR putc (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR fgetwc (3),
.BR unlocked_stdio (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Expanded the description of various flags
.\" Various wording fixes.
.\"
-.TH GLOB 3 2007-10-10 "GNU" "Linux Programmer's Manual"
+.TH GLOB 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
glob, globfree \- find pathnames matching a pattern, free memory from glob()
.SH SYNOPSIS
in glibc 2.1, as they should be according to POSIX.2,
but are declared as
.I int
-in libc4, libc5 and glibc 2.0.
+in glibc 2.0.
.SH BUGS
The
.BR glob ()
.BR wordexp (3),
.BR glob (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR confstr (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pts (4),
.BR pty (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
--- /dev/null
+.\" Copyright (C) 2014, Michael Kerrisk <mtk.manpages@gmail.com>
+.\"
+.\" %%%LICENSE_START(VERBATIM)
+.\" Permission is granted to make and distribute verbatim copies of this
+.\" manual provided the copyright notice and this permission notice are
+.\" preserved on all copies.
+.\"
+.\" Permission is granted to copy and distribute modified versions of this
+.\" manual under the conditions for verbatim copying, provided that the
+.\" entire resulting derived work is distributed under the terms of a
+.\" permission notice identical to this one.
+.\"
+.\" Since the Linux kernel and libraries are constantly changing, this
+.\" manual page may be incorrect or out-of-date. The author(s) assume no
+.\" responsibility for errors or omissions, or for damages resulting from
+.\" the use of the information contained herein. The author(s) may not
+.\" have taken the same level of care in the production of this manual,
+.\" which is licensed free of charge, as they might when working
+.\" professionally.
+.\"
+.\" Formatted or processed versions of this manual, if unaccompanied by
+.\" the source, must acknowledge the copyright and authors of this work.
+.\" %%%LICENSE_END
+.\"
+.TH GROUP_MEMBER 3 2014-03-30 "GNU" "Linux Programmer's Manual"
+.SH NAME
+group_member \- test whether a process is in a group
+.SH SYNOPSIS
+.B #include <unistd.h>
+.sp
+.BI "int group_member(gid_t " gid );
+.sp
+.in -4n
+Feature Test Macro Requirements for glibc (see
+.BR feature_test_macros (7)):
+.in
+.sp
+.BR group_member ():
+_GNU_SOURCE
+.SH DESCRIPTION
+The
+.BR group_member ()
+function tests whether any of the caller's supplementary group IDs
+(as returned by
+.BR getgroups (2))
+matches
+.IR gid .
+.SH RETURN VALUE
+The
+.BR group_member ()
+function returns nonzero if any of the caller's
+supplementary group IDs matches
+.IR gid ,
+and zero otherwise.
+.SH CONFORMING TO
+This function is a nonstandard GNU extension.
+.SH SEE ALSO
+.BR getgid (2),
+.BR getgroups (2),
+.BR getgrouplist (3),
+.BR group (5)
+.SH COLOPHON
+This page is part of release 3.75 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.
.BR signal (2),
.BR raise (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.IR "A New Hash Package for UNIX" ,
Margo Seltzer, USENIX Proceedings, Winter 1991.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR malloc (3),
.BR tsearch (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR cabs (3),
.BR sqrt (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2000-06-30 correction by Yuichi SATO <sato@complex.eng.hokudai.ac.jp>
.\" 2000-11-15 aeb, fixed prototype
.\"
-.TH ICONV 3 2012-05-10 "GNU" "Linux Programmer's Manual"
+.TH ICONV 3 2014-06-13 "GNU" "Linux Programmer's Manual"
.SH NAME
iconv \- perform character set conversion
.SH SYNOPSIS
An incomplete multibyte sequence has been encountered in the input.
.SH VERSIONS
This function is available in glibc since version 2.1.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR iconv ()
+function is thread-safe.
.SH CONFORMING TO
POSIX.1-2001.
.SH NOTES
tight restrictions on alignment.
.SH SEE ALSO
.BR iconv_close (3),
-.BR iconv_open (3)
+.BR iconv_open (3),
+.BR iconvconfig (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR iconv (3),
.BR iconv_open (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR iconv (3),
.BR iconv_close (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR if_nametoindex (3),
.BR ifconfig (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR if_nameindex (3),
.BR ifconfig (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR logb (3),
.BR significand (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strstr (3),
.BR strtok (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR hosts (5),
.BR networks (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR inet (3),
.BR networks (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR inet (3),
.BR inet_pton (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR inet (3),
.BR inet_ntop (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
This obsolete function was provided in
libc4 and libc5, but is not available in glibc2.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR setgroups (2),
.BR credentials (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" mtk, 2010-09-09: Noted glibc 2.4 bug, added info on circular
.\" lists, added example program
.\"
-.TH INSQUE 3 2010-09-09 "" "Linux Programmer's Manual"
+.TH INSQUE 3 2014-08-19 "" "Linux Programmer's Manual"
.SH NAME
insque, remque \- insert/remove an item from a queue
.SH SYNOPSIS
.SH CONFORMING TO
POSIX.1-2001.
.SH NOTES
-Traditionally (e.g., SunOS, Linux libc 4 and libc 5),
+Traditionally (e.g., SunOS, Linux libc4 and libc5),
the arguments of these functions were of type \fIstruct qelem *\fP,
defined as:
versions of UNIX.
The above is the POSIX version.
Some systems place them in \fI<string.h>\fP.
-Linux libc4 and libc 5 placed them
-in \fI<stdlib.h>\fP.
+.\" Linux libc4 and libc 5 placed them
+.\" in \fI<stdlib.h>\fP.
.SH BUGS
In glibc 2.4 and earlier, it was not possible to specify
.I prev
}
.fi
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR signal (7),
.BR standards (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
and
.BR isxdigit ()
functions are thread-safe.
-.\" FIXME: need a thread-safety statement about the *_l functions
+.\" FIXME . need a thread-safety statement about the *_l functions
.SH VERSIONS
.BR isalnum_l (),
.BR isalpha_l (),
.BR ascii (7),
.BR locale (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
refers to a file other than a terminal.
POSIX.1-2001 specifies the error
.BR ENOTTY
-.\" FIXME File a bug for this?
+.\" FIXME . File a bug for this?
for this case.
.SH ATTRIBUTES
.SS Multithreading (see pthreads(7))
.BR fstat (2),
.BR ttyname (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
--- /dev/null
+'\" t
+.\" Copyright (C) 2014 Michael Kerrisk <mtk.manpages@gmail.com>
+.\"
+.\" %%%LICENSE_START(VERBATIM)
+.\" Permission is granted to make and distribute verbatim copies of this
+.\" manual provided the copyright notice and this permission notice are
+.\" preserved on all copies.
+.\"
+.\" Permission is granted to copy and distribute modified versions of this
+.\" manual under the conditions for verbatim copying, provided that the
+.\" entire resulting derived work is distributed under the terms of a
+.\" permission notice identical to this one.
+.\"
+.\" Since the Linux kernel and libraries are constantly changing, this
+.\" manual page may be incorrect or out-of-date. The author(s) assume no
+.\" responsibility for errors or omissions, or for damages resulting from
+.\" the use of the information contained herein. The author(s) may not
+.\" have taken the same level of care in the production of this manual,
+.\" which is licensed free of charge, as they might when working
+.\" professionally.
+.\"
+.\" Formatted or processed versions of this manual, if unaccompanied by
+.\" the source, must acknowledge the copyright and authors of this work.
+.\" %%%LICENSE_END
+.\"
+.TH ISFDTYPE 3 2014-03-13 "Linux" "Linux Programmer's Manual"
+.SH NAME
+isfdtype \- test file type of a file descriptor
+.SH SYNOPSIS
+.nf
+.B #include <sys/stat.h>
+.B #include <sys/socket.h>
+
+.BI "int isfdtype(int " fd ", int" fdtype );
+.fi
+.sp
+.in -4n
+Feature Test Macro Requirements for glibc (see
+.BR feature_test_macros (7)):
+.in
+.sp
+.BR isfdtype ():
+.ad l
+.RS 4
+.PD 0
+.TP 4
+Since glibc 2.20:
+_DEFAULT_SOURCE
+.TP 4
+Before glibc 2.20:
+_BSD_SOURCE || _SVID_SOURCE
+.PD
+.RE
+.ad b
+.SH DESCRIPTION
+The
+.BR isfdtype ()
+function tests whether the file descriptor
+.I fd
+refers to a file of type
+.IR fdtype .
+The
+.I fdtype
+argument specifies one of the
+.B S_IF*
+constants defined in
+.I <sys/stat.h>
+and documented in
+.BR stat (2)
+(e.g.,
+.BR S_IFREG ).
+.SH RETURN VALUE
+The
+.BR isfdtype ()
+function returns 1 if the file descriptor
+.I fd
+is of type
+.IR fdtype
+and 0 if it is not.
+On error, -1 is returned and
+.I errno
+is set to indicate the cause.
+.SH ERRORS
+The
+.BR isfdtype ()
+function can fail with any of the same errors as
+.BR fstat (3).
+.SH CONFORMING TO
+The
+.BR isfdtype ()
+function is not specified in any standard,
+but did appear in the draft POSIX.1g standard.
+It is present on OpenBSD and Tru64 UNIX
+(where the required header file in both cases is just
+.IR <sys/stat.h> ,
+as shown in the POSIX.1g draft),
+and possibly other systems.
+.SH NOTES
+Portable applications should use
+.BR fstat (3)
+instead.
+.SH SEE ALSO
+.BR fstat (3)
+.SH COLOPHON
+This page is part of release 3.75 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.
.BR fpclassify (3),
.BR isnan (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR isalnum (3),
.BR iswctype (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR isalpha (3),
.BR iswctype (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR isblank (3),
.BR iswctype (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR iscntrl (3),
.BR iswctype (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR iswxdigit (3),
.BR wctype (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR isdigit (3),
.BR iswctype (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR isgraph (3),
.BR iswctype (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR iswctype (3),
.BR towlower (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR isprint (3),
.BR iswctype (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ispunct (3),
.BR iswctype (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR isspace (3),
.BR iswctype (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR iswctype (3),
.BR towupper (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR iswctype (3),
.BR isxdigit (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR y0 (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR crypt (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR modf (3),
.BR scalbln (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR tgamma (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR aio_write (3),
.BR aio (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strftime (3),
.BR locale (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Added section stuff, aeb, 2002-04-22.
.\" Corrected include file, drepper, 2003-06-15.
.\"
-.TH LOCKF 3 2014-02-11 "GNU" "Linux Programmer's Manual"
+.TH LOCKF 3 2014-06-13 "GNU" "Linux Programmer's Manual"
.SH NAME
lockf \- apply, test or remove a POSIX lock on an open file
.SH SYNOPSIS
.TP
.B ENOLCK
Too many segment locks open, lock table is full.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR lockf ()
+function is thread-safe.
.SH CONFORMING TO
SVr4, POSIX.1-2001.
.SH SEE ALSO
is called
.IR mandatory.txt )
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR log2 (3),
.BR sqrt (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR log2 (3),
.BR sqrt (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR expm1 (3),
.BR log (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR log10 (3),
.BR sqrt (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ilogb (3),
.BR log (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getutent (3),
.BR utmp (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR setjmp (3),
.BR sigsetjmp (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR rint (3),
.BR round (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR rint (3),
.BR round (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR hsearch (3),
.BR tsearch (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH LSEEK64 3 2013-08-19 "Linux" "Linux Programmer's Manual"
+.TH LSEEK64 3 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
lseek64 \- reposition 64-bit read/write file offset
.SH SYNOPSIS
The library routine
.BR llseek ()
.\" in libc 5.0.9, not in 4.7.6
-is available in libc5 and glibc and works without special defines.
-Its prototype was given in
-.I <unistd.h>
-with libc5, but glibc does not provide a prototype.
-This is bad, since a prototype is needed.
+is available and glibc and works without special defines.
+However, the glibc headers do not provide a prototype.
Users should add
the above prototype, or something equivalent, to their own source.
When users complained about data loss caused by a miscompilation of
.BR llseek (2),
.BR lseek (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getcontext (3),
.BR sigsetjmp (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mknod (2),
.BR stat (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
A similar function exists on many System V derivatives,
and was specified in the SVID.
.SH BUGS
-.\" FIXME http://sourceware.org/bugzilla/show_bug.cgi?id=208
+.\" FIXME . http://sourceware.org/bugzilla/show_bug.cgi?id=208
.\" See the 24 Aug 2011 mail by Paul Pluzhnikov:
.\" "[patch] Fix mallinfo() to accumulate results for all arenas"
.\" on libc-alpha@sourceware.org
.BR malloc_trim (3),
.BR mallopt (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Documented MALLOC_CHECK_, Wolfram Gloger (wmglo@dent.med.uni-muenchen.de)
.\" 2007-09-15 mtk: added notes on malloc()'s use of sbrk() and mmap().
.\"
-.\" FIXME: Review http://austingroupbugs.net/view.php?id=374
-.\" to see what changes are req uired on this page.
+.\" FIXME . Review http://austingroupbugs.net/view.php?id=374
+.\" to see what changes are required on this page.
.\"
.TH MALLOC 3 2014-05-21 "GNU" "Linux Programmer's Manual"
.SH NAME
.IR ptr ,
which must have been returned by a previous call to
.BR malloc (),
-.BR calloc ()
+.BR calloc (),
or
.BR realloc ().
Otherwise, or if
.BR mtrace (3),
.BR posix_memalign (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH MALLOC_GET_STATE 3 2012-05-04 "GNU" "Linux Programmer's Manual"
+.TH MALLOC_GET_STATE 3 2014-06-13 "GNU" "Linux Programmer's Manual"
.SH NAME
malloc_get_state, malloc_set_state \- record and restore state of malloc implementation
.SH SYNOPSIS
.nf
-.B #include <stdlib.h>
+.B #include <malloc.h>
.sp
.BI "void* malloc_get_state(void);"
.BR malloc (3),
.BR mallopt (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mcheck (3),
.BR mtrace (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mallopt (3),
.BR open_memstream (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR malloc_info (3),
.BR mallopt (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR malloc (3),
.BR mallopt (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH MALLOC_USABLE_SIZE 3 2012-03-29 "GNU" "Linux Programmer's Manual"
+.TH MALLOC_USABLE_SIZE 3 2014-06-13 "GNU" "Linux Programmer's Manual"
.SH NAME
malloc_usable_size \- obtain size of block of memory allocated from heap
.SH SYNOPSIS
If
.I ptr
is NULL, 0 is returned.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR malloc_usable_size ()
+function is thread-safe.
.SH CONFORMING TO
This function is a GNU extension.
.SH NOTES
.SH SEE ALSO
.BR malloc (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH MALLOPT 3 2012-04-30 "Linux" "Linux Programmer's Manual"
+.TH MALLOPT 3 2014-07-08 "Linux" "Linux Programmer's Manual"
.SH NAME
mallopt \- set memory allocation parameters
.SH SYNOPSIS
A calculation error within the glibc implementation means that
a call of the form:
-.\" FIXME This looks buggy:
+.\" FIXME . This looks buggy:
.\" setting the M_MXFAST limit rounds up: (s + SIZE_SZ) & ~MALLOC_ALIGN_MASK)
.\" malloc requests are rounded up:
.\" (req) + SIZE_SZ + MALLOC_ALIGN_MASK) & ~MALLOC_ALIGN_MASK
is an integer.
.\" Bins are multiples of 2 * sizeof(size_t) + sizeof(size_t)
-The
-.BR MALLOC_MMAP_THRESHOLD_
-and
-.BR MALLOC_MMAP_MAX_
-variables are
-.I not
-ignored in set-group-ID programs.
-.\" FIXME MALLOC_MMAP_THRESHOLD_ and MALLOC_MMAP_MAX_
-.\" do have an effect for set-user-ID programs (but not
-.\" set-group-ID programs).
-.\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=12155
-
If
.BR mallopt ()
is used to set
However, there is an
.RI off-by- sizeof(size_t)
error in the implementation:
-.\" FIXME http://sources.redhat.com/bugzilla/show_bug.cgi?id=12140
+.\" FIXME . http://sources.redhat.com/bugzilla/show_bug.cgi?id=12140
instead of initializing precisely the block of memory
being freed by the call
.IR free(p) ,
.BR mtrace (3),
.BR posix_memalign (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH MATHERR 3 2010-09-10 "Linux" "Linux Programmer's Manual"
+.TH MATHERR 3 2014-06-13 "Linux" "Linux Programmer's Manual"
.SH NAME
matherr \- SVID math library exception handling
.SH SYNOPSIS
fmod(x,0) DOMAIN x y EDOM
remainder(x,0) DOMAIN NAN y EDOM \" retval is 0.0/0.0
.TE
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR matherr ()
+function is thread-safe.
.SH EXAMPLE
The example program demonstrates the use of
.BR matherr ()
.BR math_error (7),
.BR standards (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR mbrlen (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR mbrtowc (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mbsinit (3),
.BR mbsrtowcs (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mbsrtowcs (3),
.BR wcsrtombs (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mbsinit (3),
.BR mbsrtowcs (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mbsnrtowcs (3),
.BR mbstowcs (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wctomb (3),
.BR wcstombs (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wctomb (3),
.BR wcstombs (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mallopt (3),
.BR mtrace (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strcpy (3),
.BR strncpy (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strstr (3),
.BR wmemchr (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strncmp (3),
.BR wmemcmp (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strncpy (3),
.BR wmemcpy (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR strfry (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 386BSD man pages
.\" Modified Sat Jul 24 18:50:48 1993 by Rik Faith (faith@cs.unc.edu)
.\" Interchanged 'needle' and 'haystack'; added history, aeb, 980113.
-.TH MEMMEM 3 2014-03-17 "GNU" "Linux Programmer's Manual"
+.TH MEMMEM 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
memmem \- locate a substring
.SH SYNOPSIS
.SH CONFORMING TO
This function is a GNU extension.
.SH BUGS
-This function was broken in Linux libraries up to and including libc 5.0.9;
-there the
-.IR needle
-and
-.I haystack
-arguments were interchanged,
-and a pointer to the end of the first occurrence of
-.I needle
-was returned.
-
-Both old and new libc's have the bug that if
+.\" This function was broken in Linux libraries up to and including libc 5.0.9;
+.\" there the
+.\" .IR needle
+.\" and
+.\" .I haystack
+.\" arguments were interchanged,
+.\" and a pointer to the end of the first occurrence of
+.\" .I needle
+.\" was returned.
+.\"
+.\" Both old and new libc's have the bug that if
+.\" .I needle
+.\" is empty,
+.\" .I haystack\-1
+.\" (instead of
+.\" .IR haystack )
+.\" is returned.
+In glibc 2.0, if
.I needle
is empty,
-.I haystack\-1
-(instead of
-.IR haystack )
-is returned.
-And glibc 2.0 makes it worse, returning a pointer to the
-last byte of
+.BR memmem ()
+returns a pointer to the last byte of
.IR haystack .
This is fixed in glibc 2.1.
.SH SEE ALSO
.BR strstr (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strncpy (3),
.BR wmemmove (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR memmove (3),
.BR wmemcpy (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR swab (3),
.BR wmemset (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Formatted or processed versions of this manual, if unaccompanied by
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
-.TH MKDTEMP 3 2010-09-26 "GNU" "Linux Programmer's Manual"
+.TH MKDTEMP 3 2014-06-13 "GNU" "Linux Programmer's Manual"
.SH NAME
mkdtemp \- create a unique temporary directory
.SH SYNOPSIS
for other possible values for \fIerrno\fP.
.SH VERSIONS
Available since glibc 2.1.91.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR mkdtemp ()
+function is thread-safe.
.SH CONFORMING TO
POSIX.1-2008.
This function is present on the BSDs.
.BR tmpfile (3),
.BR tmpnam (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR write (2),
.BR fifo (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 990328, aeb
.\" 2008-06-19, mtk, Added mkostemp(); various other changes
.\"
-.TH MKSTEMP 3 2013-12-28 "GNU" "Linux Programmer's Manual"
+.TH MKSTEMP 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
mkstemp, mkostemp, mkstemps, mkostemps \- create a unique temporary file
.SH SYNOPSIS
and
.BR mkostemps ()
are available since glibc 2.11.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR mkstemp (),
+.BR mkostemp (),
+.BR mkstemps (),
+and
+.BR mkostemps ()
+functions are thread-safe.
.SH CONFORMING TO
.BR mkstemp ():
4.3BSD, POSIX.1-2001.
.BR mkstemp ()
(and
.BR mkostemp ()).
-
-The prototype for
-.BR mktemp ()
-is in
-.I <unistd.h>
-for libc4, libc5, glibc1; glibc2 follows POSIX.1 and has the prototype in
-.IR <stdlib.h> .
+.\"
+.\" The prototype for
+.\" .BR mktemp ()
+.\" is in
+.\" .I <unistd.h>
+.\" for libc4, libc5, glibc1; glibc2 follows POSIX.1 and has the prototype in
+.\" .IR <stdlib.h> .
.SH SEE ALSO
.BR mkdtemp (3),
.BR mktemp (3),
.BR tmpfile (3),
.BR tmpnam (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" (prompted by Scott Burkett <scottb@IntNet.net>)
.\" Modified Sun Mar 28 23:44:38 1999 by Andries Brouwer (aeb@cwi.nl)
.\"
-.TH MKTEMP 3 2014-02-27 "GNU" "Linux Programmer's Manual"
+.TH MKTEMP 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
mktemp \- make a unique temporary filename
.SH SYNOPSIS
4.3BSD, POSIX.1-2001.
POSIX.1-2008 removes the specification of
.BR mktemp ().
-.SH NOTES
-The prototype is in
-.I <unistd.h>
-for libc4, libc5, glibc1; glibc2 follows the Single UNIX Specification
-and has the prototype in
-.IR <stdlib.h> .
+.\" .SH NOTES
+.\" The prototype is in
+.\" .I <unistd.h>
+.\" for libc4, libc5, glibc1; glibc2 follows the Single UNIX Specification
+.\" and has the prototype in
+.\" .IR <stdlib.h> .
.SH BUGS
Never use
.BR mktemp ().
.BR tmpfile (3),
.BR tmpnam (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR frexp (3),
.BR ldexp (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR hash (3),
.BR recno (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH MQ_CLOSE 3 2010-08-29 "Linux" "Linux Programmer's Manual"
+.TH MQ_CLOSE 3 2014-06-13 "Linux" "Linux Programmer's Manual"
.SH NAME
mq_close \- close a message queue descriptor
.SH SYNOPSIS
The descriptor specified in
.I mqdes
is invalid.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR mq_close ()
+function is thread-safe.
.SH CONFORMING TO
POSIX.1-2001.
.SH NOTES
.BR mq_unlink (3),
.BR mq_overview (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH MQ_GETATTR 3 2014-05-28 "Linux" "Linux Programmer's Manual"
+.TH MQ_GETATTR 3 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
mq_getattr, mq_setattr \- get/set message queue attributes
.SH SYNOPSIS
Two
.I /proc
files that place ceilings on the values for these fields are described in
-.BR mq_open (3).
+.BR mq_overview (3).
The
.I mq_curmsgs
.I newattr\->mq_flags
contained set bits other than
.BR O_NONBLOCK .
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR mq_getattr ()
+and
+.BR mq_setattr ()
+functions are thread-safe.
.SH CONFORMING TO
POSIX.1-2001.
.SH NOTES
are library functions layered on top of the
.BR mq_getsetattr (2)
system call.
+.SH EXAMPLE
+The program below can be used to show the default
+.I mq_maxmsg
+and
+.I mq_msgsize
+values that are assigned to a message queue that is created with a call to
+.BR mq_open (3)
+in which the
+.I attr
+argument is NULL.
+Here is an example run of the program:
+
+.in +4n
+.nf
+$ \fB./a.out /testq\fP
+Maximum # of messages on queue: 10
+Maximum message size: 8192
+.fi
+.in
+
+Since Linux 3.5, the following
+.I /proc
+files (described in
+.BR mq_overview (7))
+can be used to control the defaults:
+
+.in +4n
+.nf
+$ \fBuname -sr\fP
+Linux 3.8.0
+$ \fBcat /proc/sys/fs/mqueue/msg_default\fP
+10
+$ \fBcat /proc/sys/fs/mqueue/msgsize_default\fP
+8192
+.fi
+.in
+.SS Program course
+\&
+.nf
+#include <mqueue.h>
+#include <sys/stat.h>
+#include <fcntl.h>
+#include <stdio.h>
+#include <stdlib.h>
+#include <unistd.h>
+
+#define errExit(msg) do { perror(msg); exit(EXIT_FAILURE); \\
+ } while (0)
+
+int
+main(int argc, char *argv[])
+{
+ mqd_t mqd;
+ struct mq_attr attr;
+
+ if (argc != 2) {
+ fprintf(stderr, "Usage: %s mq\-name\\n", argv[0]);
+ exit(EXIT_FAILURE);
+ }
+
+ mqd = mq_open(argv[1], O_CREAT | O_EXCL, S_IRUSR | S_IWUSR, NULL);
+ if (mqd == (mqd_t) \-1)
+ errExit("mq_open");
+
+ if (mq_getattr(mqd, &attr) == \-1)
+ errExit("mq_getattr");
+
+ printf("Maximum # of messages on queue: %ld\\n", attr.mq_maxmsg);
+ printf("Maximum message size: %ld\\n", attr.mq_msgsize);
+
+ if (mq_unlink(argv[1]) == \-1)
+ errExit("mq_unlink");
+
+ exit(EXIT_SUCCESS);
+}
+.fi
.SH SEE ALSO
.BR mq_close (3),
.BR mq_notify (3),
.BR mq_unlink (3),
.BR mq_overview (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mq_overview (7),
.BR sigevent (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH MQ_OPEN 3 2009-02-20 "Linux" "Linux Programmer's Manual"
+.TH MQ_OPEN 3 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
mq_open \- open a message queue
.SH SYNOPSIS
(Symbolic definitions for the permissions bits can be obtained by including
.IR <sys/stat.h> .)
The permissions settings are masked against the process umask.
+
The
.I attr
argument specifies attributes for the queue.
.I attr
is NULL, then the queue is created with implementation-defined
default attributes.
+Since Linux 3.5, two
+.I /proc
+files can be used to control these defaults; see
+.BR mq_overview (7)
+for details.
.SH RETURN VALUE
On success,
.BR mq_open ()
.I queues_max
limit was encountered; see
.BR mq_overview (7).
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR mq_open ()
+function is thread-safe.
.SH CONFORMING TO
POSIX.1-2001.
.SH BUGS
.BR mq_unlink (3),
.BR mq_overview (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH MQ_RECEIVE 3 2014-01-18 "Linux" "Linux Programmer's Manual"
+.TH MQ_RECEIVE 3 2014-06-03 "Linux" "Linux Programmer's Manual"
.SH NAME
mq_receive, mq_timedreceive \- receive a message from a message queue
.SH SYNOPSIS
.TP
.B ETIMEDOUT
The call timed out before a message could be transferred.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR mq_receive ()
+and
+.BR mq_timedreceive ()
+functions are thread-safe.
.SH CONFORMING TO
POSIX.1-2001.
.SH NOTES
.BR mq_overview (7),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH MQ_SEND 3 2014-01-18 "Linux" "Linux Programmer's Manual"
+.TH MQ_SEND 3 2014-06-03 "Linux" "Linux Programmer's Manual"
.SH NAME
mq_send, mq_timedsend \- send a message to a message queue
.SH SYNOPSIS
.TP
.B ETIMEDOUT
The call timed out before a message could be transferred.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR mq_send ()
+and
+.BR mq_timedsend ()
+functions are thread-safe.
.SH CONFORMING TO
POSIX.1-2001.
.SH NOTES
.BR mq_overview (7),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH MQ_UNLINK 3 2010-08-29 "Linux" "Linux Programmer's Manual"
+.TH MQ_UNLINK 3 2014-06-13 "Linux" "Linux Programmer's Manual"
.SH NAME
mq_unlink \- remove a message queue
.SH SYNOPSIS
.B ENOENT
There is no message queue with the given
.IR name .
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR mq_unlink ()
+function is thread-safe.
.SH CONFORMING TO
POSIX.1-2001.
.SH SEE ALSO
.BR mq_send (3),
.BR mq_overview (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR malloc_hook (3),
.BR mcheck (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strtod (3),
.BR math_error (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR libnetlink (3),
.BR netlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR locale (5),
.BR locale (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR nearbyint (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.br
The GNU C Library Reference Manual
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
}
.fi
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 386BSD man pages
.\" Modified 1993-04-02, David Metcalfe
.\" Modified 1993-07-25, Rik Faith (faith@cs.unc.edu)
-.TH ON_EXIT 3 2008-12-05 "GNU" "Linux Programmer's Manual"
+.TH ON_EXIT 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
on_exit \- register a function to be called at normal process termination
.SH SYNOPSIS
function returns the value 0 if successful; otherwise
it returns a nonzero value.
.SH CONFORMING TO
-This function comes from SunOS 4, but is also present in
-libc4, libc5 and glibc.
+This function comes from SunOS 4, but is also present in glibc.
It no longer occurs in Solaris (SunOS 5).
-Avoid this function, and use the standard
+Portable application should avoid this function, and use the standard
.BR atexit (3)
instead.
.SH SEE ALSO
.BR atexit (3),
.BR exit (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR seekdir (3),
.BR telldir (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\" Added -lutil remark, 030718
.\"
-.TH OPENPTY 3 2010-06-13 "GNU" "Linux Programmer's Manual"
+.TH OPENPTY 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
openpty, login_tty, forkpty \- terminal utility functions
.SH SYNOPSIS
.BR fork (2)
fails.
.SH CONFORMING TO
-These are BSD functions, present in libc5 and glibc2.
+These are BSD functions, present in glibc.
They are not standardized in POSIX.
.SH NOTES
The
.BR ttyname (3),
.BR pty (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR error (3),
.BR strerror (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR stdio (3),
.BR system (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH POSIX_FALLOCATE 3 2013-02-12 "GNU" "Linux Programmer's Manual"
+.TH POSIX_FALLOCATE 3 2014-06-03 "GNU" "Linux Programmer's Manual"
.SH NAME
posix_fallocate \- allocate file space
.SH SYNOPSIS
.SH VERSIONS
.BR posix_fallocate ()
is available since glibc 2.1.94.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR posix_fallocate ()
+function is thread-safe.
.SH CONFORMING TO
POSIX.1-2001.
.BR lseek (2),
.BR posix_fadvise (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR free (3),
.BR malloc (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH POSIX_OPENPT 3 2012-04-20 "" "Linux Programmer's Manual"
+.TH POSIX_OPENPT 3 2014-06-03 "" "Linux Programmer's Manual"
.SH NAME
posix_openpt \- open a pseudoterminal device
.SH SYNOPSIS
Glibc support for
.BR posix_openpt ()
has been provided since version 2.2.1.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR posix_openpt ()
+function is thread-safe.
.SH CONFORMING TO
.BR posix_openpt ()
is part of the UNIX 98 pseudoterminal support (see
.BR pts (4),
.BR pty (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR cpow (3),
.BR sqrt (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR exp10 (3),
.BR pow (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2000-07-26 jsm28@hermes.cam.ac.uk - three small fixes
.\" 2000-10-16 jsm28@hermes.cam.ac.uk - more fixes
.\"
-.TH PRINTF 3 2013-12-30 "GNU" "Linux Programmer's Manual"
+.TH PRINTF 3 2014-07-08 "GNU" "Linux Programmer's Manual"
.SH NAME
printf, fprintf, sprintf, snprintf, vprintf, vfprintf, vsprintf,
vsnprintf \- formatted output conversion
.B \-
The converted value is to be left adjusted on the field boundary.
(The default is right justification.)
-Except for
-.B n
-conversions, the converted value is padded on the right with blanks, rather
+The converted value is padded on the right with blanks, rather
than on the left with blanks or zeros.
A
.B \-
.B +
overrides a space if both are used.
.PP
-The five flag characters above are defined in the C standard.
-The SUSv2 specifies one further flag character.
+The five flag characters above are defined in the C99 standard.
+The Single UNIX Specification specifies one further flag character.
.TP
.B \(aq
For decimal conversion
Note that many versions of
.BR gcc (1)
cannot parse this option and will issue a warning.
-SUSv2 does not
-include \fI%\(aqF\fP.
+(SUSv2 did not
+include \fI%\(aqF\fP, but SUSv3 added it.)
.PP
glibc 2.2 adds one further flag character.
.TP
.I long double
argument.
(C99 allows %LF, but SUSv2 does not.)
-.TP
-.B q
-("quad". 4.4BSD and Linux libc5 only.
-Don't use.)
+.\" .TP
+.\" .B q
+.\" ("quad". 4.4BSD and Linux libc5 only.
+.\" Don't use.)
This is a synonym for
.BR ll .
.TP
.I intmax_t
or
.I uintmax_t
+argument, or a following
+.B n
+conversion corresponds to a pointer to an
+.I intmax_t
argument.
.TP
.B z
.I size_t
or
.I ssize_t
+argument, or a following
+.B n
+conversion corresponds to a pointer to a
+.I size_t
argument.
-(Linux libc5 has
-.B Z
-with this meaning.
-Don't use it.)
+.\" (Linux libc5 has
+.\" .B Z
+.\" with this meaning.
+.\" Don't use it.)
.TP
.B t
A following integer conversion corresponds to a
.I ptrdiff_t
+argument, or a following
+.B n
+conversion corresponds to a pointer to a
+.I ptrdiff_t
argument.
.PP
-The SUSv2 knows about only the length modifiers
+SUSv3 specifies all of the above.
+SUSv2 specified only the length modifiers
.B h
(in
.BR hd ,
6; if the precision is explicitly zero, no decimal-point character appears.
If a decimal point appears, at least one digit appears before it.
-(The SUSv2 does not know about
+(SUSv2 does not know about
.B F
and says that character string representations for infinity and NaN
may be made available.
+SUSv3 adds a specification for
+.BR F .
The C99 standard specifies "[\-]inf" or "[\-]infinity"
for infinity, and a string starting with "nan" for NaN, in the case of
.B f
followed by at least one digit.
.TP
.BR a ", " A
-(C99; not in SUSv2) For
+(C99; not in SUSv2, but added in SUSv3)
+For
.B a
conversion, the
.I double
exceeds it before the end of the array is reached.
.TP
.B C
-(Not in C99, but in SUSv2.)
+(Not in C99 or C11, but in SUSv2, SUSv3, and SUSv4.)
Synonym for
.BR lc .
Don't use.
.TP
.B S
-(Not in C99, but in SUSv2.)
+(Not in C99 or C11, but in SUSv2, SUSv3, and SUSv4.)
Synonym for
.BR ls .
Don't use.
.TP
.B n
The number of characters written so far is stored into the integer
-indicated by the
-.I "int\ *"
-(or variant) pointer argument.
+pointed to by the corresponding argument.
+That argument shall be an
+.I "int\ *",
+or variant whose size matches the (optionally)
+supplied integer length modifier.
No argument is converted.
+The behavior is undefined if the conversion specification includes
+any flags, a field width, or a precision.
.TP
.B m
(Glibc extension.)
to be NULL in this case, and gives the return value (as always)
as the number of characters that would have been written in case
the output string has been large enough.
-.PP
-Linux libc4 knows about the five C standard flags.
-It knows about the length modifiers \fBh\fP, \fBl\fP, \fBL\fP,
-and the conversions
-\fBc\fP, \fBd\fP, \fBe\fP, \fBE\fP, \fBf\fP, \fBF\fP,
-\fBg\fP, \fBG\fP, \fBi\fP, \fBn\fP, \fBo\fP, \fBp\fP,
-\fBs\fP, \fBu\fP, \fBx\fP, and \fBX\fP,
-where \fBF\fP is a synonym for \fBf\fP.
-Additionally, it accepts \fBD\fP, \fBO\fP, and \fBU\fP as synonyms
-for \fBld\fP, \fBlo\fP, and \fBlu\fP.
-(This is bad, and caused serious bugs later, when
-support for \fB%D\fP disappeared.)
-No locale-dependent radix character,
-no thousands' separator, no NaN or infinity, no "%m$" and "*m$".
-.PP
-Linux libc5 knows about the five C standard flags and the \(aq flag,
-locale, "%m$" and "*m$".
-It knows about the length modifiers \fBh\fP, \fBl\fP, \fBL\fP,
-\fBZ\fP, and \fBq\fP, but accepts \fBL\fP and \fBq\fP
-both for \fIlong double\fP and for \fIlong long int\fP (this is a bug).
-It no longer recognizes \fBF\fP, \fBD\fP, \fBO\fP, and \fBU\fP,
-but adds the conversion character
-.BR m ,
-which outputs
-.IR strerror(errno) .
-.PP
-glibc 2.0 adds conversion characters \fBC\fP and \fBS\fP.
+SUSv3 and later align their specification of
+.BR snprintf ()
+with C99.
+.\" .PP
+.\" Linux libc4 knows about the five C standard flags.
+.\" It knows about the length modifiers \fBh\fP, \fBl\fP, \fBL\fP,
+.\" and the conversions
+.\" \fBc\fP, \fBd\fP, \fBe\fP, \fBE\fP, \fBf\fP, \fBF\fP,
+.\" \fBg\fP, \fBG\fP, \fBi\fP, \fBn\fP, \fBo\fP, \fBp\fP,
+.\" \fBs\fP, \fBu\fP, \fBx\fP, and \fBX\fP,
+.\" where \fBF\fP is a synonym for \fBf\fP.
+.\" Additionally, it accepts \fBD\fP, \fBO\fP, and \fBU\fP as synonyms
+.\" for \fBld\fP, \fBlo\fP, and \fBlu\fP.
+.\" (This is bad, and caused serious bugs later, when
+.\" support for \fB%D\fP disappeared.)
+.\" No locale-dependent radix character,
+.\" no thousands' separator, no NaN or infinity, no "%m$" and "*m$".
+.\" .PP
+.\" Linux libc5 knows about the five C standard flags and the \(aq flag,
+.\" locale, "%m$" and "*m$".
+.\" It knows about the length modifiers \fBh\fP, \fBl\fP, \fBL\fP,
+.\" \fBZ\fP, and \fBq\fP, but accepts \fBL\fP and \fBq\fP
+.\" both for \fIlong double\fP and for \fIlong long int\fP (this is a bug).
+.\" It no longer recognizes \fBF\fP, \fBD\fP, \fBO\fP, and \fBU\fP,
+.\" but adds the conversion character
+.\" .BR m ,
+.\" which outputs
+.\" .IR strerror(errno) .
+.\" .PP
+.\" glibc 2.0 adds conversion characters \fBC\fP and \fBS\fP.
.PP
glibc 2.1 adds length modifiers \fBhh\fP, \fBj\fP, \fBt\fP, and \fBz\fP
and conversion characters \fBa\fP and \fBA\fP.
.BR vsnprintf ()
conforms to the C99 standard, that is, behaves as described above,
since glibc version 2.1.
-Until glibc 2.0.6 they would return \-1
+Until glibc 2.0.6, they would return \-1
when the output was truncated.
.\" .SH HISTORY
.\" UNIX V7 defines the three routines
.BR asprintf (3)
and
.BR vasprintf (3)).
-.PP
-Linux libc4.[45] does not have a
-.BR snprintf (),
-but provides a libbsd that contains an
-.BR snprintf ()
-equivalent to
-.BR sprintf (),
-that is, one that ignores the
-.I size
-argument.
-Thus, the use of
-.BR snprintf ()
-with early libc4 leads to serious security problems.
+.\" .PP
+.\" Linux libc4.[45] does not have a
+.\" .BR snprintf (),
+.\" but provides a libbsd that contains an
+.\" .BR snprintf ()
+.\" equivalent to
+.\" .BR sprintf (),
+.\" that is, one that ignores the
+.\" .I size
+.\" argument.
+.\" Thus, the use of
+.\" .BR snprintf ()
+.\" with early libc4 leads to serious security problems.
.PP
Code such as
.BI printf( foo );
.BR wprintf (3),
.BR locale (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified Fri Jun 23 01:35:19 1995 Andries Brouwer <aeb@cwi.nl>
.\" (prompted by Bas V. de Bakker <bas@phys.uva.nl>)
.\" Corrected (and moved to man3), 980612, aeb
-.TH PROFIL 3 2007-07-26 "Linux" "Linux Programmer's Manual"
+.TH PROFIL 3 2014-07-08 "Linux" "Linux Programmer's Manual"
.SH NAME
profil \- execution time profile
.SH SYNOPSIS
Libc 4.4 contained a kernel patch providing a system call profil.
.SH SEE ALSO
.BR gprof (1),
+.BR sprof (1),
.BR setitimer (2),
.BR sigaction (2),
.BR signal (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR proc (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
had the following bugs:
.IP * 3
In some circumstances, a trailing newline is not printed.
-.\" FIXME http://sourceware.org/bugzilla/show_bug.cgi?id=12107
+.\" FIXME . http://sourceware.org/bugzilla/show_bug.cgi?id=12107
.\" Reportedly now fixed; check glibc 2.13
.IP *
Additional details are not displayed for real-time signals.
-.\" FIXME http://sourceware.org/bugzilla/show_bug.cgi?id=12108
+.\" FIXME . http://sourceware.org/bugzilla/show_bug.cgi?id=12108
.\" Reportedly now fixed; check glibc 2.13
.SH SEE ALSO
.BR sigaction (2),
.BR strsignal (3),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_getattr_np (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR cpuset (7),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_join (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_create (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.I attr
take their scheduling attributes from the values specified
by the attributes object.
-.\" FIXME what are the defaults for scheduler settings?
+.\" FIXME Document the defaults for scheduler settings
.PP
The default setting of the inherit-scheduler attribute in
a newly initialized thread attributes object is
.BR pthread_create (3),
.BR pthread_setschedparam (3),
.BR pthread_setschedprio (3),
-.BR pthreads ,(7)
+.BR pthreads (7),
.BR sched (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_create (3),
.BR pthread_setschedparam (3),
.BR pthread_setschedprio (3),
-.BR pthreads (7).
+.BR pthreads (7),
.BR sched (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthreads (7),
.BR sched (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_create (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_create (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_create (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_create (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_testcancel (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_testcancel (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_testcancel (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR setrlimit (2)),
which limits the number of processes and threads for a real user ID,
was reached;
-the kernel's system-wide limit on the number of processes threads,
+the kernel's system-wide limit on the number of processes and threads,
.IR /proc/sys/kernel/threads-max ,
was reached (see
.BR proc (5));
.BR pthread_self (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_join (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_self (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_join (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_create (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.B #include <pthread.h>
.B #include <time.h>
-.BI "int pthread_getcpuclockid(pthread_t " thread ", clockid_t *" clock_id);
+.BI "int pthread_getcpuclockid(pthread_t " thread ", clockid_t *" clock_id );
.sp
Compile and link with \fI\-pthread\fP.
.fi
.BR pthreads (7),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_tryjoin_np (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthreads (7),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_setcanceltype (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
--- /dev/null
+.so man3/pthread_rwlockattr_setkind_np.3
--- /dev/null
+.\"Copyright (c) 2010 Novell Inc., written by Robert Schweikert
+.\"
+.\" %%%LICENSE_START(VERBATIM)
+.\" Permission is granted to make and distribute verbatim copies of this
+.\" manual provided the copyright notice and this permission notice are
+.\" preserved on all copies.
+.\"
+.\" Permission is granted to copy and distribute modified versions of this
+.\" manual under the conditions for verbat`im copying, provided that the
+.\" entire resulting derived work is distributed under the terms of a
+.\" permission notice identical to this one.
+.\"
+.\" Since the Linux kernel and libraries are constantly changing, this
+.\" manual page may be incorrect or out-of-date. The author(s) assume no
+.\" responsibility for errors or omissions, or for damages resulting from
+.\" the use of the information contained herein. The author(s) may not
+.\" have taken the same level of care in the production of this manual,
+.\" which is licensed free of charge, as they might when working
+.\" professionally.
+.\"
+.\" Formatted or processed versions of this manual, if unaccompanied by
+.\" the source, must acknowledge the copyright and authors of this work.
+.\" %%%LICENSE_END
+.\"
+.TH PTHREAD_RWLOCKATTR_SETKIND_NP 3 2014-10-15 "Linux Programmer's Manual"
+.SH NAME
+pthread_rwlockattr_setkind_np, pthread_rwlockattr_getkind_np \- set/get
+the read-write lock kind of the thread read-write lock attribute object
+.SH SYNOPSIS
+.nf
+.B #include <pthread.h>
+
+.BI "int pthread_rwlockattr_setkind_np(pthread_rwlockattr_t *" attr ,
+.BI " int " pref );
+.BI "int pthread_rwlockattr_getkind_np(const pthread_rwlockattr_t *" attr ,
+.BI " int *" pref );
+.sp
+Compile and link with \fI\-pthread\fP.
+.sp
+.fi
+.in -4n
+Feature Test Macro Requirements for glibc (see
+.BR feature_test_macros (7)):
+.in
+.sp
+.BR pthread_rwlockattr_setkind_np (),
+.BR pthread_rwlockattr_getkind_np ():
+.br
+.RS 4
+.ad l
+_XOPEN_SOURCE\ >=\ 500 || _POSIX_C_SOURCE >= 200809L
+.RE
+.ad
+.SH DESCRIPTION
+The
+.BR pthread_rwlockattr_setkind_np ()
+function sets the "lock kind" attribute of the
+read-write lock attribute object referred to by
+.I attr
+to the value specified in
+.IR pref .
+The argument
+.I pref
+may be set to one of the following:
+.TP
+.B PTHREAD_RWLOCK_PREFER_READER_NP
+This is the default.
+A thread may hold multiple read locks; that is, read locks are recursive.
+According to The Single Unix Specification, the behavior is unspecified when a
+reader tries to place a lock, and there is no write lock but writers are
+waiting.
+Giving preference to the reader, as is set by
+.BR PTHREAD_RWLOCK_PREFER_READER_NP ,
+implies that the reader will receive the requested lock, even if
+a writer is waiting.
+As long as there are readers, the writer will be
+starved.
+.TP
+.B PTHREAD_RWLOCK_PREFER_WRITER_NP
+This is intended as the write lock analog of
+.BR PTHREAD_RWLOCK_PREFER_READER_NP .
+But see BUGS.
+.TP
+.B PTHREAD_RWLOCK_PREFER_WRITER_NONRECURSIVE_NP
+Setting the lock kind to this
+avoids writer starvation as long as any read locking is not done in a
+recursive fashion.
+.PP
+The
+.BR pthread_rwlockattr_getkind_np ()
+function returns the value of the lock kind attribute of the
+read-write lock attribute object referred to by
+.IR attr
+in the pointer
+.IR pref .
+.SH RETURN VALUE
+On success, these functions return 0.
+Given valid pointer arguments,
+.BR pthread_rwlockattr_getkind_np ()
+always succeeds.
+On error,
+.BR pthread_rwlockattr_setkind_np ()
+returns a non-zero error number.
+.SH ERRORS
+.TP
+.BR EINVAL
+.I pref
+specifies an unsupported value.
+.SH BUGS
+Setting the value read-write lock kind to
+.BR PTHREAD_RWLOCK_PREFER_WRITER_NP
+results in the same behavior as setting the value to
+.BR PTHREAD_RWLOCK_PREFER_READER_NP .
+As long as a reader thread holds the lock, the thread holding a
+write lock will be starved.
+Setting the lock kind to
+.BR PTHREAD_RWLOCK_PREFER_WRITER_NONRECURSIVE_NP
+allows writers to run, but, as the name implies a writer
+may not lock recursively.
+.\" http://sourceware.org/bugzilla/show_bug.cgi?id=7057
+.SH VERSIONS
+The
+.BR pthread_rwlockattr_getkind_np ()
+and
+.BR pthread_rwlockattr_setkind_np ()
+functions first appeared in glibc 2.1.
+.SH CONFORMING TO
+These functions are non-standard GNU extensions;
+hence the suffix "_np" (non-portable) in the names.
+.SH SEE ALSO
+.BR pthreads (7)
+.SH COLOPHON
+This page is part of release 3.75 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.
.BR pthread_equal (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthreads (7),
.BR sched (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_testcancel (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_attr_setscope (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_create (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthreads (7),
.BR sched (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthreads (7),
.BR sched (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthreads (7),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthreads (7),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_setcancelstate (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_join (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthreads (7),
.BR sched (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pts (4),
.BR pty (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified Mon Oct 11 11:11:11 1999 by Andries Brouwer (aeb@cwi.nl)
.\" Modified Wed Nov 10 00:02:26 1999 by Andries Brouwer (aeb@cwi.nl)
.\" Modified Sun May 20 22:17:20 2001 by Andries Brouwer (aeb@cwi.nl)
-.TH PUTENV 3 2013-04-19 "GNU" "Linux Programmer's Manual"
+.TH PUTENV 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
putenv \- change or add an environment variable
.SH SYNOPSIS
The
.BR putenv ()
function is not required to be reentrant, and the
-one in libc4, libc5 and glibc 2.0 is not, but the glibc 2.1 version is.
+one in glibc 2.0 is not, but the glibc 2.1 version is.
+.\" .LP
+.\" Description for libc4, libc5, glibc:
+.\" If the argument \fIstring\fP is of the form \fIname\fP,
+.\" and does not contain an \(aq=\(aq character, then the variable \fIname\fP
+.\" is removed from the environment.
+.\" If
+.\" .BR putenv ()
+.\" has to allocate a new array \fIenviron\fP,
+.\" and the previous array was also allocated by
+.\" .BR putenv (),
+.\" then it will be freed.
+.\" In no case will the old storage associated
+.\" to the environment variable itself be freed.
.LP
-Description for libc4, libc5, glibc:
-If the argument \fIstring\fP is of the form \fIname\fP,
-and does not contain an \(aq=\(aq character, then the variable \fIname\fP
-is removed from the environment.
-If
-.BR putenv ()
-has to allocate a new array \fIenviron\fP,
-and the previous array was also allocated by
-.BR putenv (),
-then it will be freed.
-In no case will the old storage associated
-to the environment variable itself be freed.
-.LP
-The libc4 and libc5 and glibc 2.1.2 versions conform to SUSv2:
+Since version 2.1.2, the glibc implementation conforms to SUSv2:
the pointer \fIstring\fP given to
.BR putenv ()
is used.
with an automatic variable
as the argument, then return from the calling function while \fIstring\fP
is still part of the environment.)
-However, glibc 2.0-2.1.1 differs: a copy of the string is used.
+However, glibc versions 2.0 to 2.1.1 differ: a copy of the string is used.
On the one hand this causes a memory leak, and on the other hand
it violates SUSv2.
-This has been fixed in glibc 2.1.2.
.LP
The 4.4BSD version, like glibc 2.0, uses a copy.
.LP
.BR unsetenv (3),
.BR environ (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getgrent (3),
.BR group (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getpwuid (3),
.BR setpwent (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.I stream
more than once.
.PP
-.BI "putchar(" c );
+.BI "putchar(" c )
is equivalent to
.BI "putc(" c ", " stdout ).
.PP
.BR scanf (3),
.BR unlocked_stdio (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR fputwc (3),
.BR unlocked_stdio (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" This replaces an earlier man page written by Walter Harms
.\" <walter.harms@informatik.uni-oldenburg.de>.
.\"
-.TH QECVT 3 2014-03-11 "GNU" "Linux Programmer's Manual"
+.TH QECVT 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
qecvt, qfcvt, qgcvt \- convert a floating-point number to a string
.SH SYNOPSIS
.BR qgcvt ():
_SVID_SOURCE
.ad b
-.\" FIXME The full FTM picture looks to have be something like the
+.\" FIXME . The full FTM picture looks to have be something like the
.\" following mess:
.\" glibc 2.20 onward
.\" _DEFAULT_SOURCE
.SH DESCRIPTION
The functions
.BR qecvt (),
-.BR qfcvt ()
+.BR qfcvt (),
and
.BR qgcvt ()
are identical to
.BR ecvt (3),
-.BR fcvt (3)
+.BR fcvt (3),
and
.BR gcvt (3)
respectively, except that they use a
SVr4.
Not seen in most common UNIX implementations,
but occurs in SunOS.
-Not supported by libc4 and libc5.
+.\" Not supported by libc4 and libc5.
Supported by glibc.
.SH NOTES
These functions are obsolete.
.BR gcvt (3),
.BR sprintf (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strcmp (3),
.BR versionsort (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
for (np = head.lh_first; np != NULL; np = np\->entries.le_next)
np\-> ...
-.\" FIXME http://sourceware.org/bugzilla/show_bug.cgi?id=1506
+.\" FIXME . http://sourceware.org/bugzilla/show_bug.cgi?id=1506
while (head.lh_first != NULL) /* Delete. */
LIST_REMOVE(head.lh_first, entries);
.fi
queue functions first appeared in
4.4BSD.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pthread_kill (3),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR drand48 (3),
.BR random (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR random_r (3),
.BR srand (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR rand (3),
.BR random (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR rlogind (8),
.BR rshd (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR regex (7),
GNU regex manual
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR seekdir (3),
.BR telldir (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Rewritten old page, 990824, aeb@cwi.nl
.\" 2004-12-14, mtk, added discussion of resolved_path == NULL
.\"
-.TH REALPATH 3 2013-03-15 "" "Linux Programmer's Manual"
+.TH REALPATH 3 2014-10-02 "" "Linux Programmer's Manual"
.SH NAME
realpath \- return the canonicalized absolute pathname
.SH SYNOPSIS
.TP
.B ENOTDIR
A component of the path prefix is not a directory.
-.SH VERSIONS
-On Linux, this function appeared in libc 4.5.21.
.SH CONFORMING TO
4.4BSD, POSIX.1-2001.
.\" Solaris may return a relative pathname when the
.\" .I path
.\" argument is relative.
-The prototype of
-.BR realpath ()
-is given in \fI<unistd.h>\fP in libc4 and libc5,
-but in \fI<stdlib.h>\fP everywhere else.
+.\" The prototype of
+.\" .BR realpath ()
+.\" is given in \fI<unistd.h>\fP in libc4 and libc5,
+.\" but in \fI<stdlib.h>\fP everywhere else.
.SS GNU extensions
If the call fails with either
.BR EACCES
.I "resolved_path\ ==\ NULL"
feature, not standardized in POSIX.1-2001,
but standardized in POSIX.1-2008, allows this design problem to be avoided.
-.LP
-The libc4 and libc5 implementation contained a buffer overflow
-(fixed in libc-5.4.13).
-Thus, set-user-ID programs like
-.BR mount (8)
-needed a private version.
+.\" .LP
+.\" The libc4 and libc5 implementation contained a buffer overflow
+.\" (fixed in libc-5.4.13).
+.\" Thus, set-user-ID programs like
+.\" .BR mount (8)
+.\" needed a private version.
.SH SEE ALSO
+.BR realpath (1),
.BR readlink (2),
.BR canonicalize_file_name (3),
.BR getcwd (3),
.BR pathconf (3),
.BR sysconf (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
Michael Stonebraker, Heidi Stettner, Joseph Kalash, Antonin Guttman,
Nadene Lynn, Memorandum No. UCB/ERL M82/32, May 1982.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
The glibc manual section,
.I "Regular Expression Matching"
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR fmod (3),
.BR remquo (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH REMOVE 3 2014-03-10 "GNU" "Linux Programmer's Manual"
+.TH REMOVE 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
remove \- remove a file or directory
.SH SYNOPSIS
function is thread-safe.
.SH CONFORMING TO
C89, C99, 4.3BSD, POSIX.1-2001.
-.SH NOTES
-Under libc4 and libc5,
-.BR remove ()
-was an alias for
-.BR unlink (2)
-(and hence would not remove directories).
+.\" .SH NOTES
+.\" Under libc4 and libc5,
+.\" .BR remove ()
+.\" was an alias for
+.\" .BR unlink (2)
+.\" (and hence would not remove directories).
.SH BUGS
Infelicities in the protocol underlying NFS can cause the unexpected
disappearance of files which are still being used.
.BR mkfifo (3),
.BR symlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR logb (3),
.BR remainder (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR hostname (7),
.BR named (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR seekdir (3),
.BR telldir (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR rcmd (3),
.BR rexecd (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR round (3),
.BR trunc (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR rint (3),
.BR trunc (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
RFC\ 1050, Sun Microsystems, Inc.,
USC-ISI.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR regcomp (3),
.BR setlocale (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" .BR rdate (1),
.BR inetd (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\" $Id: rtnetlink.3,v 1.2 1999/05/18 10:35:10 freitag Exp $
.\"
-.TH RTNETLINK 3 2012-03-24 "GNU" "Linux Programmer's Manual"
+.TH RTNETLINK 3 2014-09-06 "GNU" "Linux Programmer's Manual"
.SH NAME
rtnetlink \- macros to manipulate rtnetlink messages
.SH SYNOPSIS
.SH BUGS
This manual page is incomplete.
.SH EXAMPLE
-.\" FIXME ? would be better to use libnetlink in the EXAMPLE code here
-
+.\" FIXME . ? would be better to use libnetlink in the EXAMPLE code here
Creating a rtnetlink message to set the MTU of a device:
.nf
#include <linux/rtnetlink.h>
req.n.nlmsg_len = NLMSG_ALIGN(req.nh.nlmsg_len) +
RTA_LENGTH(sizeof(mtu));
memcpy(RTA_DATA(rta), &mtu, sizeof(mtu));
- send(rtnetlink_sk, &req, req.nh.nlmsg_len);
+ send(rtnetlink_sk, &req, req.nh.nlmsg_len, 0);
.fi
.SH SEE ALSO
.BR netlink (3),
.BR netlink (7),
.BR rtnetlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ldexp (3),
.BR scalbln (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ldexp (3),
.BR scalb (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strverscmp (3),
.BR telldir (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strtol (3),
.BR strtoul (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getcpu (2),
.BR sched (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR scandir (3),
.BR telldir (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sem_wait (3),
.BR sem_overview (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sem_wait (3),
.BR sem_overview (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sem_wait (3),
.BR sem_overview (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sem_wait (3),
.BR sem_overview (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sem_wait (3),
.BR sem_overview (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sem_wait (3),
.BR sem_overview (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sem_wait (3),
.BR sem_overview (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sem_overview (7),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Yellow Pages
.\" newaliases, postalias
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Correction, 2000-03-03, Andreas Jaeger <aj@suse.de>
.\" Added return value for setvbuf, aeb,
.\"
-.TH SETBUF 3 2014-02-18 "Linux" "Linux Programmer's Manual"
+.TH SETBUF 3 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
setbuf, setbuffer, setlinebuf, setvbuf \- stream buffering operations
.SH SYNOPSIS
.BR setvbuf ()
functions conform to C89 and C99.
.SH BUGS
-The
-.BR setbuffer ()
-and
-.BR setlinebuf ()
-functions are not portable to versions of BSD before 4.2BSD, and
-are available under Linux since libc 4.5.21.
-On 4.2BSD and 4.3BSD systems,
-.BR setbuf ()
-always uses a suboptimal buffer size and should be avoided.
+.\" The
+.\" .BR setbuffer ()
+.\" and
+.\" .BR setlinebuf ()
+.\" functions are not portable to versions of BSD before 4.2BSD, and
+.\" are available under Linux since libc 4.5.21.
+.\" On 4.2BSD and 4.3BSD systems,
+.\" .BR setbuf ()
+.\" always uses a suboptimal buffer size and should be avoided.
.P
You must make sure that the space that
.I buf
.BR printf (3),
.BR puts (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR putenv (3),
.BR environ (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR longjmp (3),
.BR siglongjmp (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR charsets (7),
.BR locale (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR openlog (3),
.BR syslog (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR setprotoent (3),
.BR setservent (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR umask (2),
.BR shm_overview (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 386BSD man pages
.\" Modified Sun Jul 25 10:40:51 1993 by Rik Faith (faith@cs.unc.edu)
.\" Modified Sun Apr 14 16:20:34 1996 by Andries Brouwer (aeb@cwi.nl)
-.TH SIGINTERRUPT 3 2013-04-19 "" "Linux Programmer's Manual"
+.TH SIGINTERRUPT 3 2014-06-13 "" "Linux Programmer's Manual"
.SH NAME
siginterrupt \- allow signals to interrupt system calls
.SH SYNOPSIS
.TP
.B EINVAL
The specified signal number is invalid.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR siginterrupt ()
+function uses a global variable that is not protected,
+so it is not thread-safe.
.SH CONFORMING TO
4.3BSD, POSIX.1-2001.
POSIX.1-2008 marks
.SH SEE ALSO
.BR signal (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR copysign (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ilogb (3),
.BR scalb (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH SIGPAUSE 3 2014-01-07 "Linux" "Linux Programmer's Manual"
+.TH SIGPAUSE 3 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
sigpause \- atomically release blocked signals and wait for interrupt
.SH SYNOPSIS
On Linux, this routine is a system call only on the Sparc (sparc64)
architecture.
-Libc4 and libc5 know only about the BSD version.
-
+.\" Libc4 and libc5 know only about the BSD version.
+.\"
Glibc uses the BSD version if the
.B _BSD_SOURCE
feature test macro is defined and none of
.BR sigvec (3),
.BR feature_test_macros (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sigwait (3),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sigvec (3),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sigprocmask (2),
.BR sigsuspend (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sigset (3),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sigsetops (3),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sincos (3),
.BR tan (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sin (3),
.BR tan (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR csinh (3),
.BR tanh (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR signal (2),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR send (2),
.BR tcp (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR csqrt (3),
.BR hypot (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR statfs (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
}
.fi
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR fopen (3),
.BR stdio (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR stdout (3),
.BR unlocked_stdio (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR flockfile (3),
.BR fpurge (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR string (3),
.BR wcpcpy (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strncpy (3),
.BR wcpncpy (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wcscasecmp (3),
.BR wcsncasecmp (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.IR "size\-strlen(dest)\-1"
from
.IR src ,
-and adds a null terminator to the result,
+and adds a terminating null byte to the result,
.I unless
.IR size
is less than
.BR wcscat (3),
.BR wcsncat (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wcschr (3),
.BR wcsrchr (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wcscmp (3),
.BR wcsncmp (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR string (3),
.BR strxfrm (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wcscpy (3),
.BR wcsncpy (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR string (3),
.BR wcsdup (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
The
.BR strerror_r ()
function is thread-safe.
-.\" FIXME Need a thread-safety statement about strerror_l()
+.\" FIXME . Need a thread-safety statement about strerror_l()
.SH VERSIONS
The
.BR strerror_l ()
.BR strsignal (3),
.BR locale (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sprintf (3),
.BR locale (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR memfrob (3),
.BR string (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2005-11-22 mtk, added Glibc Notes covering optional 'flag' and
.\" 'width' components of conversion specifications.
.\"
-.TH STRFTIME 3 2014-03-18 "GNU" "Linux Programmer's Manual"
+.TH STRFTIME 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
strftime \- format date and time
.SH SYNOPSIS
.I s
of size
.IR max .
-.\" FIXME POSIX says: Local timezone information is used as though
+.\" FIXME . POSIX says: Local timezone information is used as though
.\" strftime() called tzset(). But this doesn't appear to be the case
.PP
The format specification is a null-terminated string and may contain
bytes, then
.BR strftime ()
returns 0, and the contents of the array are undefined.
-(This behavior applies since at least libc 4.4.4;
-very old versions of libc, such as libc 4.4.1,
-would return
-.I max
-if the array was too small.)
+.\" (This behavior applies since at least libc 4.4.4;
+.\" very old versions of libc, such as libc 4.4.1,
+.\" would return
+.\" .I max
+.\" if the array was too small.)
.LP
Note that the return value 0 does not necessarily indicate an error.
For example, in many locales
.BR sprintf (3),
.BR strptime (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strtok (3),
.BR strxfrm (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wcslen (3),
.BR wcsnlen (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR strlen (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strtok (3),
.BR wcspbrk (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified, aeb, 2001-08-31
.\" Modified, wharms 2001-11-12, remark on white space and example
.\"
-.TH STRPTIME 3 2014-01-17 "GNU" "Linux Programmer's Manual"
+.TH STRPTIME 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
strptime \- convert a string representation of time to a time tm structure
.SH SYNOPSIS
and
.I tm_yday
field if any of the year, month, or day elements changed.
-.PP
-This function is available since libc 4.6.8.
-Linux libc4 and libc5 includes define the prototype unconditionally;
-glibc2 includes provide a prototype only when
-.B _XOPEN_SOURCE
-or
-.B _GNU_SOURCE
-are defined.
-.PP
-Before libc 5.4.13 whitespace
-(and the \(aqn\(aq and \(aqt\(aq specifications) was not handled,
-no \(aqE\(aq and \(aqO\(aq locale modifier characters were accepted,
-and the \(aqC\(aq specification was a synonym for the \(aqc\(aq specification.
+.\" .PP
+.\" This function is available since libc 4.6.8.
+.\" Linux libc4 and libc5 includes define the prototype unconditionally;
+.\" glibc2 includes provide a prototype only when
+.\" .B _XOPEN_SOURCE
+.\" or
+.\" .B _GNU_SOURCE
+.\" are defined.
+.\" .PP
+.\" Before libc 5.4.13 whitespace
+.\" (and the \(aqn\(aq and \(aqt\(aq specifications) was not handled,
+.\" no \(aqE\(aq and \(aqO\(aq locale modifier characters were accepted,
+.\" and the \(aqC\(aq specification was a synonym for the \(aqc\(aq specification.
.PP
The \(aqy\(aq (year in century) specification is taken to specify a year
-in the 20th century by libc4 and libc5.
-It is taken to be a year
+.\" in the 20th century by libc4 and libc5.
+.\" It is taken to be a year
in the range 1950-2049 by glibc 2.0.
It is taken to be a year in
1969-2068 since glibc 2.1.
.BR setlocale (3),
.BR strftime (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strstr (3),
.BR strtok (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR psignal (3),
.BR strerror (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wcscspn (3),
.BR wcsspn (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Added history, aeb, 980113.
.\" 2005-05-05 mtk: added strcasestr()
.\"
-.TH STRSTR 3 2014-01-22 "GNU" "Linux Programmer's Manual"
+.TH STRSTR 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
strstr, strcasestr \- locate a substring
.SH SYNOPSIS
The
.BR strcasestr ()
function is a nonstandard extension.
-.SH BUGS
-Early versions of Linux libc (like 4.5.26) would not allow
-an empty
-.I needle
-argument for
-.BR strstr ().
-Later versions (like 4.6.27) work correctly,
-and return
-.IR haystack
-when
-.I needle
-is empty.
+.\" .SH BUGS
+.\" Early versions of Linux libc (like 4.5.26) would not allow
+.\" an empty
+.\" .I needle
+.\" argument for
+.\" .BR strstr ().
+.\" Later versions (like 4.6.27) work correctly,
+.\" and return
+.\" .IR haystack
+.\" when
+.\" .I needle
+.\" is empty.
.SH SEE ALSO
.BR index (3),
.BR memchr (3),
.BR strtok (3),
.BR wcsstr (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" (michael@cantor.informatik.rwth-aachen.de)
.\" Added strof, strtold, aeb, 2001-06-07
.\"
-.TH STRTOD 3 2014-01-22 "Linux" "Linux Programmer's Manual"
+.TH STRTOD 3 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
strtod, strtof, strtold \- convert ASCII string to floating-point number
.SH SYNOPSIS
or
.I cc\ -std=c99
.RE
-.ad l
+.ad
.SH DESCRIPTION
The
.BR strtod (),
.LP
A
.I NAN
-is "NAN" (disregarding case) optionally followed by \(aq(\(aq,
-a sequence of characters, followed by \(aq)\(aq.
-The character string specifies in an implementation-dependent
-way the type of NAN.
-.\" From glibc 2.8's stdlib/strtod_l.c:
-.\" We expect it to be a number which is put in the
-.\" mantissa of the number.
+is "NAN" (disregarding case) optionally followed by a string,
+.IR (n-char-sequence) ,
+where
+.IR n-char-sequence
+specifies in an implementation-dependent
+way the type of NAN (see NOTES).
.SH RETURN VALUE
These functions return the converted value, if any.
and then determine if an error occurred by checking whether
.I errno
has a nonzero value after the call.
+
+In the glibc implementation, the
+.IR n-char-sequence
+that optionally follows "NAN"
+is interpreted as an integer number
+(with an optional '0' or '0x' prefix to select base 8 or 16)
+that is to be placed in the
+mantissa component of the returned value.
+.\" From glibc 2.8's stdlib/strtod_l.c:
+.\" We expect it to be a number which is put in the
+.\" mantissa of the number.
+.\" It looks as though at least FreeBSD (according to the manual) does
+.\" something similar.
+.\" C11 says: "An implementation may use the n-char sequence to determine
+.\" extra information to be represented in the NaN's significant."
.SH EXAMPLE
See the example on the
.BR strtol (3)
.BR atof (3),
.BR atoi (3),
.BR atol (3),
+.BR nan (3),
+.BR nanf (3),
+.BR nanl (3),
.BR strtol (3),
.BR strtoul (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strtoul (3),
.BR wcstoimax (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strstr (3),
.BR wcstok (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strtod (3),
.BR strtoul (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strtod (3),
.BR strtol (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strcmp (3),
.BR strcoll (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strcoll (3),
.BR string (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR bstring (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pathconf (3),
.BR posixoptions (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR syslog.conf (5),
.BR syslogd (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 14 May 2001, 23 Sep 2001 by aeb
.\" 2004-12-20, mtk
.\"
-.TH SYSTEM 3 2014-05-10 "" "Linux Programmer's Manual"
+.TH SYSTEM 3 2014-06-13 "" "Linux Programmer's Manual"
.SH NAME
system \- execute a shell command
.SH SYNOPSIS
.BR execl (3)
as follows:
- execl("/bin/sh", "sh". "-c", command, (char *) 0);
+ execl("/bin/sh", "sh", "-c", command, (char *) 0);
.BR system ()
returns after the command has been completed.
.PP
.BR system ()
does not affect the wait status of any other children.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR system ()
+function is thread-safe.
.SH CONFORMING TO
C89, C99, POSIX.1-2001.
.SH NOTES
.BR exec (3),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR bsd_signal (3),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ctan (3),
.BR sin (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ctanh (3),
.BR sinh (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR setsid (2),
.BR credentials (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR getsid (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR scandir (3),
.BR seekdir (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR tmpfile (3),
.BR tmpnam (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR tty_ioctl (4),
.BR setserial (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR gamma (3),
.BR lgamma (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mktime (3),
.BR tzset (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR gettimeofday (2),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR tempnam (3),
.BR tmpnam (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR tempnam (3),
.BR tmpfile (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR tolower (3),
.BR toupper (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
as long as
.BR setlocale (3)
is not called to change the locale during their execution.
-.\" FIXME Add toupper_l() and tolower_l()
+.\" FIXME . Add toupper_l() and tolower_l()
.SH CONFORMING TO
.BR toupper (),
.BR tolower ():
.PP
In some non-English locales, there are lowercase letters with no
corresponding uppercase equivalent;
-.\" FIXME: One day the statement about "sharp s" needs to be reworked,
+.\" FIXME One day the statement about "sharp s" needs to be reworked,
.\" since there is nowadays a capital "sharp s" that has a codepoint
.\" in Unicode 5.0; see https://en.wikipedia.org/wiki/Capital_%E1%BA%9E
the German sharp s is one example.
.BR towupper (3),
.BR locale (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR towupper (3),
.BR wctrans (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
It can be safely used in multithreaded applications, as long as
.BR setlocale (3)
is not called to change the locale during its execution.
-.\" FIXME need a thread-safety statement about towlower_l()
+.\" FIXME . need a thread-safety statement about towlower_l()
.SH VERSIONS
The
.BR towlower_l ()
.BR towupper (3),
.BR locale (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
-.\" Copyright (c) Bruno Haible <haible@clisp.cons.org>
+
.\" and Copyright (C) 2014 Michael Kerrisk <mtk.manpages@gmail.com>
.\"
.\" %%%LICENSE_START(GPLv2+_DOC_ONEPARA)
It can be safely used in multithreaded applications, as long as
.BR setlocale (3)
is not called to change the locale during its execution.
-.\" FIXME need a thread-safety statement about towupper_l()
+.\" FIXME . need a thread-safety statement about towupper_l()
.SH VERSIONS
The
.BR towupper_l ()
.BR towlower (3),
.BR locale (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR rint (3),
.BR round (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR lsearch (3),
.BR qsort (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ctermid (3),
.BR isatty (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
There used to be a file
.I /etc/ttys
in UNIX\ V6, that was read by the
-.BR init (8)
+.BR init (1)
program to find out what to do with each terminal line.
Each line consisted of three characters.
The first character was either \(aq0\(aq or \(aq1\(aq,
.BR ttyname (3),
.BR utmp (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 2001-11-13, aeb
.\" Modified 2004-12-01 mtk and Martin Schulze <joey@infodrom.org>
.\"
-.TH TZSET 3 2012-03-25 "" "Linux Programmer's Manual"
+.TH TZSET 3 2014-08-19 "" "Linux Programmer's Manual"
.SH NAME
tzset, tzname, timezone, daylight \- initialize time conversion information
.SH SYNOPSIS
TZ=":Pacific/Auckland"
.fi
.SH FILES
-The system timezone directory used depends on the (g)libc version.
-Libc4 and libc5 use
-.IR /usr/lib/zoneinfo ,
-and, since libc-5.4.6,
-when this doesn't work, will try
-.IR /usr/share/zoneinfo .
-Glibc2 will use the environment variable
-.BR TZDIR ,
-when that exists.
-Its default depends on how it was installed, but normally is
+Under glibc,
+the system timezone directory is determined using the
+.BR TZDIR
+the environment variable.
+If
+.BR TZDIR
+the default depends on the system setup, but is normally
.IR /usr/share/zoneinfo .
.LP
This timezone directory contains the files
+
.nf
-localtime local timezone file
-posixrules rules for POSIX-style TZ's
+ localtime local timezone file
+ posixrules rules for POSIX-style TZ's
.fi
.LP
-Often
+Often,
.I /etc/localtime
-is a symlink to the file
+is a symbolic link to the file
.I localtime
or to the correct timezone file in the system timezone directory.
.SH CONFORMING TO
.BR getenv (3),
.BR tzfile (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR usleep (3),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR setrlimit (2),
.BR sysconf (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR yp_unbind (3),
.BR yp_update (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR fgetwc (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR flockfile (3),
.BR stdio (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR pts (4),
.BR pty (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Added -lutil remark, 030718
.\" 2008-07-02, mtk, document updwtmpx()
.\"
-.TH UPDWTMP 3 2008-07-02 "GNU" "Linux Programmer's Manual"
+.TH UPDWTMP 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME
updwtmp, logwtmp \- append an entry to the wtmp file
.SH SYNOPSIS
.BI "void logwtmp(const char *" line ", const char *" name \
", const char *" host );
.fi
+
+For
+.BR logwtmp (),
+link with \fI\-lutil\fP.
.SH DESCRIPTION
.BR updwtmp ()
appends the utmp structure
.SH CONFORMING TO
Not in POSIX.1-2001.
Present on Solaris, NetBSD, and perhaps other systems.
-.SH AVAILABILITY
-Both functions are available under glibc2, but not under libc5.
-However,
-.BR logwtmp ()
-used to occur in the old libbsd.
-These days, the
-.BR logwtmp ()
-function is included in libutil.
-(Hence you'll need to add \fI\-lutil\fP
-to your compiler command line to get it.)
.SH NOTES
For consistency with the other "utmpx" functions (see
.BR getutxent (3)),
.BR getutxent (3),
.BR wtmp (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR locale (5),
.BR locale (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ualarm (3),
.BR time (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strcpy (3),
.BR wcscpy (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR stpncpy (3),
.BR wcsncpy (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mbsinit (3),
.BR wcsrtombs (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strcasecmp (3),
.BR wcscmp (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wcscpy (3),
.BR wcsncat (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wcsstr (3),
.BR wmemchr (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wcscasecmp (3),
.BR wmemcmp (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wcsdup (3),
.BR wmemcpy (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wcspbrk (3),
.BR wcsspn (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strdup (3),
.BR wcscpy (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR strlen (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strncasecmp (3),
.BR wcsncmp (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strncat (3),
.BR wcscat (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strncmp (3),
.BR wcsncasecmp (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR strncpy (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strnlen (3),
.BR wcslen (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mbsinit (3),
.BR wcsrtombs (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wcschr (3),
.BR wcscspn (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strrchr (3),
.BR wcschr (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wcsnrtombs (3),
.BR wcstombs (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strspn (3),
.BR wcscspn (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strstr (3),
.BR wcschr (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wcstol (3),
.BR wcstoul (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR strtok (3),
.BR wcschr (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wcsrtombs (3)
.BR wctom (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR iswprint (3),
.BR wcwidth (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wcrtomb (3),
.BR wctomb (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wcrtomb (3),
.BR wcstombs (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR towctrans (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR iswctype (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR iswprint (3),
.BR wcswidth (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR memchr (3),
.BR wcschr (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR memcmp (3),
.BR wcscmp (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR wmemmove (3),
.BR wmempcpy (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR memmove (3),
.BR wmemcpy (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR memset (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR fnmatch (3),
.BR glob (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR snprintf (3)
.\" .BR wscanf (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 3. xencrypt() a hexstring
.\" to bad to be true :(
.\"
-.TH XCRYPT 3 2003-04-04 "" "Linux Programmer's Manual"
+.TH XCRYPT 3 2014-08-19 "" "Linux Programmer's Manual"
.SH NAME
xencrypt, xdecrypt, passwd2des \- RFS password encryption
.SH SYNOPSIS
.BR xdecrypt ()
return 1 on success and 0 on error.
.SH VERSIONS
-These routines are present in libc 4.6.27 and later, and in
-glibc 2.1 and later.
+These functions are available in glibc since version 2.1.
.SH BUGS
The prototypes are missing from the abovementioned include file.
.SH SEE ALSO
.BR cbc_crypt (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
USC-ISI.
.RE
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR j0 (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.B cciss
driver is a block
driver as well as a SCSI driver and only the tape drives and medium
-changers are presented to the SCSI midlayer
+changers are presented to the SCSI midlayer.
Furthermore, unlike more
straightforward SCSI drivers, disk I/O continues through the block
-side during the SCSI error-recovery process
+side during the SCSI error-recovery process.
Therefore, the
.B cciss
driver implements only the first two of these actions,
.\" Charles White, Francis Wiran
.\" and probably some other people.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.LP
Common ways to start a process on a console are:
(a) tell
-.BR init (8)
+.BR init (1)
(in
.BR inittab (5))
to start a
.SH SEE ALSO
.BR chvt (1),
.BR deallocvt (1),
+.BR init (1),
.BR loadkeys (1),
.BR mknod (1),
.BR openvt (1),
.BR ttyS (4),
.BR charsets (7),
.BR agetty (8),
-.BR init (8),
.BR mapscrn (8),
.BR mingetty (8),
.BR resizecons (8),
.BR setfont (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR console_ioctl (4),
.BR charsets (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.TS
l l l.
LED_CAP 0x04 caps lock led
-LEC_NUM 0x02 num lock led
+LED_NUM 0x02 num lock led
LED_SCR 0x01 scroll lock led
.TE
.TP
.IR /usr/include/linux/kd.h ,
.I /usr/include/linux/vt.h
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
Intel Corporation, Intel Processor Identification and
the CPUID Instruction, Application note 485.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.UE ,
DSP56000/DSP56001 Digital Signal Processor User's Manual
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mount (8),
.BR setfdprm (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR null (4),
.BR zero (4)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sd (4),
.BR mount (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Don Brace, Steve Cameron, Tom Lawler, Mike Miller, Scott Teel
.\" and probably some other people.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
and
.BR pivot_root (8)
for information on the modern method of changing the root filesystem.
-.\" FIXME the manual page should describe the pivot_root mechanism.
+.\" FIXME . Should this manual page describe the pivot_root mechanism?
.\"
.\"
.\"
in the Linux kernel source tree, the LILO documentation,
the LOADLIN documentation, the SYSLINUX documentation
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR standards (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR lpcntl (8),
.BR tunelp (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mknod (1),
.BR ioperm (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ttyS (4),
.BR gpm (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
Software Developer's Manual Volume 3B Appendix B,
for an overview of the Intel CPU MSRs.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mknod (1),
.BR full (4)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR unlockpt (3),
.BR pty (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mknod (1),
.BR mount (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.br
RFC\ 1750, "Randomness Recommendations for Security"
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.I Documentation/rtc.txt
in the Linux kernel source tree
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\".SH "SEE ALSO"
.\".BR scsi (4)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR insmod (8),
.BR modprobe (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
the most recent information about the driver and its configuration
possibilities
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR agetty (8),
.BR mingetty (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mingetty (8),
.BR setserial (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" TIOCSERSETMULTI const struct serial_multiport_struct *
.\" TIOCGSERIAL, TIOCSSERIAL (see above)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ttyS (4),
.BR gpm (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR iwpriv (8),
.BR iwspy (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR accton (8),
.BR sa (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
-.\" This file is part of locale(1) which displays the settings of the
-.\" current locale.
.\" Copyright (C) 1994 Jochen Hein (Hein@Student.TU-Clausthal.de)
.\"
.\" %%%LICENSE_START(GPLv2+_SW_3_PARA)
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
-.TH CHARMAP 5 1994-11-28 "" "Linux User Manual"
+.TH CHARMAP 5 2014-07-08 "GNU" "Linux Programmer's Manual"
.SH NAME
-charmap \- character symbols to define character encodings
+charmap \- character set description file
.SH DESCRIPTION
-A character set description (charmap) defines a character set of
-available characters and their encodings.
-All supported character
-sets should have the
-.B portable character set
-as a proper subset.
-.\" Not true anymore:
-.\" The portable character set is defined in the file
-.\" .I /usr/lib/nls/charmap/POSIX
-.\" .I /usr/share/i18n/charmap/POSIX
-.\" for reference purposes.
+A character set description (charmap) defines all available characters
+and their encodings in a character set.
+.BR localedef (1)
+can use charmaps to create locale variants for different character sets.
.SS Syntax
-The charmap file starts with a header, that may consist of the
+The charmap file starts with a header that may consist of the
following keywords:
.TP
-.I <codeset>
-is followed by the name of the codeset.
+.I <code_set_name>
+is followed by the name of the character map.
+.TP
+.I <comment_char>
+is followed by a character that will be used as the comment character
+for the rest of the file.
+It defaults to the number sign (#).
+.TP
+.I <escape_char>
+is followed by a character that should be used as the escape character
+for the rest of the file to mark characters that should be interpreted
+in a special way.
+It defaults to the backslash (\\).
.TP
.I <mb_cur_max>
-is followed by the max number of bytes for a multibyte-character.
-Multibyte characters are currently not supported.
-The default value
-is 1.
+is followed by the maximum number of bytes for a character.
+The default value is 1.
.TP
.I <mb_cur_min>
-is followed by the min number of bytes for a character.
-This
-value must be less than or equal than
-.BR mb_cur_max .
+is followed by the minimum number of bytes for a character.
+This value must be less than or equal than
+.IR mb_cur_max .
If not specified, it defaults to
-.BR mb_cur_max .
-.TP
-.I <escape_char>
-is followed by a character that should be used as the
-escape-character for the rest of the file to mark characters that
-should be interpreted in a special way.
-It defaults to
-the backslash (
-.B \\\\
-).
-.TP
-.I <comment_char>
-is followed by a character that will be used as the
-comment-character for the rest of the file.
-It defaults to the
-number sign (
-.B #
-).
+.IR mb_cur_max .
.PP
-The charmap-definition itself starts with the keyword
+The character set definition section starts with the keyword
.B CHARMAP
-in column 1.
+in the first column.
The following lines may have one of the two following forms to
-define the character-encodings:
+define the character set:
.TP
-.I <symbolic-name> <encoding> <comments>
-This form defines exactly one character and its encoding.
+.I <character> <byte-sequence> <comment>
+This form defines exactly one character and its byte sequence,
+.I <comment>
+being optional.
.TP
-.I <symbolic-name>...<symbolic-name> <encoding> <comments>
-This form defines a couple of characters.
-This is useful only for
-multibyte-characters, which are currently not implemented.
+.I <character>..<character> <byte-sequence> <comment>
+This form defines a character range and its byte sequence,
+.I <comment>
+being optional.
+.PP
+The character set definition section ends with the string
+.IR "END CHARMAP" .
+.PP
+The character set definition section may optionally be followed by a
+section to define widths of characters.
.PP
-The last line in a charmap-definition file must contain
-.B END CHARMAP.
-.SS Symbolic names
-A
-.B symbolic name
-for a character contains only characters of the
-.B portable character set.
-The name itself is enclosed between angle brackets.
-Characters following an
-.B <escape_char>
-are interpreted as itself; for example, the sequence
-.B "<\\\\\\\\\\\\>>"
-represents the symbolic name
-.B "\\\\>"
-enclosed in angle brackets.
-.SS Character encoding
The
-encoding may be in each of the following three forms:
-.TP
-.I <escape_char>d<number>
-with a decimal number
+.B WIDTH_DEFAULT
+keyword can be used to define the default width for all characters
+not explicitly listed.
+The default character width is 1.
+.PP
+The width section for individual characters starts with the keyword
+.B WIDTH
+in the first column.
+
+The following lines may have one of the two following forms to
+define the widths of the characters:
.TP
-.I <escape_char>x<number>
-with a hexadecimal number
+.I <character> <width>
+This form defines the width of exactly one character.
.TP
-.I <escape_char><number>
-with an octal number.
-.\" FIXME comments
-.\" FIXME char ... char
+.I <character>...<character> <width>
+This form defines the width for all the characters in the range.
+.PP
+The width definition section ends with the string
+.IR "END WIDTH" .
.SH FILES
-.I /usr/share/i18n/charmaps/*
-.\" .SH AUTHOR
-.\" Jochen Hein (jochen.hein@delphi.central.de)
+.TP
+.I /usr/share/i18n/charmaps
+Usual default character map path.
.SH CONFORMING TO
POSIX.2.
+.SH EXAMPLE
+The Euro sign is defined as follows in the
+.I UTF\-8
+charmap:
+.PP
+.nf
+<U20AC> /xe2/x82/xac
+.fi
.SH SEE ALSO
+.BR iconv (1),
.BR locale (1),
.BR localedef (1),
-.BR localeconv (3),
-.BR setlocale (3),
-.BR locale (5)
+.BR locale (5),
+.BR charsets (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH CORE 5 2014-05-28 "Linux" "Linux Programmer's Manual"
+.TH CORE 5 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
core \- core dump file
.SH DESCRIPTION
tot += nread;
fprintf(fp, "Total bytes in core dump: %d\\n", tot);
+ fclose(fp);
exit(EXIT_SUCCESS);
}
.fi
.BR pthreads (7),
.BR signal (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR stty (1),
.BR xterm (1)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.IR "System V Application Binary Interface AMD64 Architecture Processor Supplement" .
.PP
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mkfs (8),
.BR mount (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR proftpd (8),
.BR wuftpd (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getaddrinfo (3),
RFC\ 3484
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getgrnam (3),
.BR passwd (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR named (8),
.BR resolv+ (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" This manual page was written by Manoj Srivastava <srivasta@debian.org>,
.\" for the Debian GNU/Linux system.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR rlogind (8),
.BR rshd (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR standards (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR agetty (8),
.BR mingetty (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2008-06-17 Petr Baudis <pasky@suse.cz>
.\" LC_TIME: Describe first_weekday and first_workday
.\"
-.TH LOCALE 5 2014-05-23 "Linux" "Linux User Manual"
+.TH LOCALE 5 2014-06-13 "Linux" "Linux User Manual"
.SH NAME
locale \- describes a locale definition file
.SH DESCRIPTION
in the first column.
The following keywords are allowed:
-.\" FIXME translit_start + translit_end are not documented
-.\" FIXME 'charclass' is not documented
-.\" FIXME 'charconv' is not documented
-.\" FIXME 'outdigit' is not documented
-.\" FIXME 'include' is not documented
-.\" FIXME 'map' (to_inpunct, to_outpunct) is not documented
+.\" FIXME The following LC_CTYPE keywords are not documented:
+.\" translit_start + translit_end
+.\" charclass
+.\" charconv
+.\" outdigit
+.\" include
+.\" map (to_inpunct, to_outpunct)
.TP
.I upper
followed by a list of uppercase letters.
definition ends with the string
.IR "END LC_CTYPE" .
.SS LC_COLLATE
-.\" FIXME: the description of LC_COLLATE lacks a lot of details
+.\" FIXME The description of LC_COLLATE lacks a lot of details
The
.B LC_COLLATE
category defines the rules for collating characters.
in the first column.
The following keywords are allowed:
-.\" FIXME 'script' is not documented
-.\" FIXME 'symbol-equivalence' is not documented
+.\" FIXME The following LC_COLLATE keywords are not documented:
+.\" script
+.\" symbol-equivalence
.TP
.I collating-element
followed by the definition of a collating-element symbol
The order definition consists of lines that describe the order
and is terminated with the keyword
.IR order_end .
-.\" FIXME 'reorder-after' is not documented
-.\" FIXME 'reorder-end' is not documented
-.\" FIXME 'reorder-sections-after' is not documented
-.\" FIXME 'reorder-sections-end' is not documented
+.\" FIXME The following LC_COLLATE keywords are not documented:
+.\" reorder-after
+.\" reorder-end
+.\" reorder-sections-after
+.\" reorder-sections-end
.PP
The
.B LC_COLLATE
in the first column.
The following keywords are allowed:
-.\" FIXME 'era', 'era_d_fmt', 'era_d_t_fmt', 'era_t_fmt', are not documented
-.\" FIXME 'timezone' is not documented
+.\" FIXME The following LC_TIME keywords are not documented:
+.\" era
+.\" era_d_fmt
+.\" era_d_t_fmt
+.\" era_t_fmt
+.\" timezone
.TP
.I abday
followed by a list of abbreviated names of the days of the week.
as specified by
.I week
(Sunday by default).
+See NOTES.
.TP
.I day
followed by a list of names of the days of the week.
as specified by
.I week
(Sunday by default).
+See NOTES.
.TP
.I abmon
followed by a list of abbreviated month names.
and
.B pm
strings.
-This should be defined only for locales using AM/PM convention.
+This should be left empty for locales not using AM/PM convention.
.TP
.I d_t_fmt
followed by the appropriate date and time format.
.TP
.I t_fmt_ampm
followed by the appropriate time format when using 12h clock format.
-This should be defined only for locales using the AM/PM convention.
+This should be left empty for locales not using AM/PM convention.
.TP
.I week
followed by a list of three values:
shall be used for Sunday and
.B 19971201
shall be used for Monday.
-Thus, countries using
-.B 19971130
-should have local Sunday name as the first day in the
-.I day
-list,
-while countries using
-.B 19971201
-should have Monday translation as the first item in the
-.I day
-list.
+See NOTES.
.TP
.IR first_weekday " (since glibc 2.2)"
followed by the number of the first day from the
on the value of the second
.I week
list item.
+See NOTES.
.TP
.IR first_workday " (since glibc 2.2)"
followed by the number of the first working day from the
list.
The default value is
.BR 2 .
+See NOTES.
.TP
.I cal_direction
.\" from localedata/locales/uk_UA
Usual default path for locale definition files.
.SH CONFORMING TO
POSIX.2, ISO/IEC TR 14652.
+.SH NOTES
+The collective GNU C library community wisdom regarding
+.IR abday ,
+.IR day ,
+.IR week ,
+.IR first_weekday ,
+and
+.I first_workday
+states at
+https://sourceware.org/glibc/wiki/Locales
+the following:
+.IP * 3
+The value of the second
+.I week
+list item specifies the base of the
+.I abday
+and
+.I day
+lists.
+.IP *
+.I first_weekday
+specifies the offset of the first day-of-week in the
+.I abday
+and
+.I day
+lists.
+.IP *
+For compatibility reasons, all glibc locales should set the value of the
+second
+.I week
+list item to
+.B 19971130
+(Sunday) and base the
+.I abday
+and
+.I day
+lists appropriately, and set
+.I first_weekday
+to
+.B 1
+or
+.BR 2 ,
+depending on whether the week actually starts on Sunday or Monday
+for the locale.
.SH BUGS
This manual page isn't complete.
.\" .SH AUTHOR
.BR setlocale (3),
.BR uselocale (3),
.BR charmap (5),
-.BR locale (7)
+.BR charsets (7),
+.BR locale (7),
+.BR unicode (7),
+.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR login (1),
.BR issue (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR netstat (8),
.BR route (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR login (1),
.BR shutdown (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" .B nscd
.\" was written by Thorsten Kukuk and Ulrich Drepper.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
\fInsswitch.conf\fR
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR getent (1),
.BR nss (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR group (5),
.BR shadow (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2008-06-19, mtk, Documented /proc/[pid]/status.
.\" 2008-07-15, mtk, added /proc/config.gz
.\"
-.\" FIXME 2.6.13 seems to have /proc/vmcore implemented
-.\" in the source code, but there is no option available under
-.\" 'make xconfig'; eventually this should be fixed, and then info
-.\" from the patch-2.6.13 and change log could be used to write an
-.\" entry in this man page.
-.\" Needs CONFIG_VMCORE
-.\"
-.\" FIXME cross check against Documentation/filesystems/proc.txt
+.\" FIXME . cross check against Documentation/filesystems/proc.txt
.\" to see what information could be imported from that file
.\" into this file.
.\"
-.TH PROC 5 2014-05-28 "Linux" "Linux Programmer's Manual"
+.TH PROC 5 2014-09-21 "Linux" "Linux Programmer's Manual"
.SH NAME
proc \- process information pseudo-filesystem
.SH DESCRIPTION
Each such subdirectory contains the following
pseudo-files and directories.
.\" FIXME Describe /proc/[pid]/attr and
-.\" /proc/[pid]/task/[tid]/attr
-.\" This is a directory
-.\" Added in ???
-.\" CONFIG_SECURITY
+.\" /proc/[pid]/task/[tid]/attr
+.\" This is a directory
+.\" Added in 2.6.0
+.\" CONFIG_SECURITY
+.\" https://lwn.net/Articles/28222/
+.\" http://www.nsa.gov/research/_files/selinux/papers/module/x362.shtml
+.\"
+.\" fscreate, current, prev, and exec present in Linux 2.6.0
+.\" keycreate added in Linux 2.6.18
+.\" commit 4eb582cf1fbd7b9e5f466e3718a59c957e75254e
+.\" /Documentation/keys.txt
+.\" sockcreate added in Linux 2.6.18
+.\" commit 42c3e03ef6b298813557cdb997bd6db619cd65a2
+.\"
+.\" FIXME Describe /proc/[pid]/autogroup
+.\" 2.6.38
+.\" commit 5091faa449ee0b7d73bc296a93bca9540fc51d0a
+.\" CONFIG_SCHED_AUTOGROUP
.\"
.TP
.IR /proc/[pid]/auxv " (since 2.6.0-test7)"
The format is one \fIunsigned long\fP ID
plus one \fIunsigned long\fP value for each entry.
The last entry contains two zeros.
+See also
+.BR getauxval (3).
.TP
.IR /proc/[pid]/cgroup " (since Linux 2.6.24)"
.\" Info in Documentation/cgroups/cgroups.txt
kernel configuration option is enabled.
.TP
.I /proc/[pid]/cmdline
-This holds the complete command line for the process,
+This read-only file holds the complete command line for the process,
unless the process is a zombie.
.\" In 2.3.26, this also used to be true if the process was swapped out.
In the latter case, there is nothing in this file:
strings separated by null bytes (\(aq\\0\(aq),
with a further null byte after the last string.
.TP
-.IR /proc/[pid]/coredump_filter " (since kernel 2.6.23)"
+.IR /proc/[pid]/comm " (since Linux 2.6.33)"
+.\" commit 4614a696bd1c3a9af3a08f0e5874830a85b889d4
+This file exposes the process's
+.I comm
+value\(emthat is, the command name associated with the process.
+Different threads in the same process may have different
+.I comm
+values, accessible via
+.IR /proc/[pid]/task/[tid]/comm .
+A thread may modify its
+.I comm
+value, or that of any of other thread in the same thread group (see
+the discussion of
+.B CLONE_THREAD
+in
+.BR clone (2)),
+by writing to the file
+.IR /proc/self/task/[tid]/comm .
+Strings longer than
+.B TASK_COMM_LEN
+(16) characters are silently truncated.
+
+This file provides a superset of the
+.BR prctl (2)
+.B PR_SET_NAME
+and
+.B PR_GET_NAME
+operations, and is employed by
+.BR pthread_setname_np (3)
+when used to rename threads other than the caller.
+.TP
+.IR /proc/[pid]/coredump_filter " (since Linux 2.6.23)"
See
.BR core (5).
.TP
-.IR /proc/[pid]/cpuset " (since kernel 2.6.12)"
+.IR /proc/[pid]/cpuset " (since Linux 2.6.12)"
.\" and/proc/[pid]/task/[tid]/cpuset
See
.BR cpuset (7).
(typically by calling
.BR pthread_exit (3)).
-Under Linux 2.0 and earlier
+Under Linux 2.0 and earlier,
.I /proc/[pid]/exe
is a pointer to the binary which was executed,
and appears as a symbolic link.
.\" Added in 2.6.11; updating requires CAP_AUDIT_CONTROL
.\" CONFIG_AUDITSYSCALL
.TP
-.IR /proc/[pid]/fdinfo/ " (since kernel 2.6.22)"
+.IR /proc/[pid]/fdinfo/ " (since Linux 2.6.22)"
This is a subdirectory containing one entry for each file which the
process has open, named by its file descriptor.
The contents of each file can be read to obtain information
while process B is updating one of these 64-bit counters,
process A could see an intermediate result.
.TP
-.IR /proc/[pid]/limits " (since kernel 2.6.24)"
+.IR /proc/[pid]/gid_map " (since Linux 3.5)"
+See the description of
+.IR /proc/[pid]/uid_map .
+
+.TP
+.IR /proc/[pid]/limits " (since Linux 2.6.24)"
This file displays the soft limit, hard limit, and units of measurement
for each of the process's resource limits (see
.BR getrlimit (2)).
.BR strace (1),
or similar.
-Under Linux 2.0 there is no field giving pathname.
+Under Linux 2.0, there is no field giving pathname.
.TP
.I /proc/[pid]/mem
This file can be used to access the pages of a process's memory through
and
.BR epoll_wait (2)
mark the file as having an error condition.
+See
+.BR namespaces (7)
+for more information.
.TP
.IR /proc/[pid]/mountstats " (since Linux 2.6.17)"
This file exports information (statistics, configuration information)
-about the mount points in the process's name space.
+about the mount points in the process's mount namespace.
Lines in this file have the form:
.nf
.RE
.IP
This file is readable only by the owner of the process.
+
+See
+.BR namespaces (7)
+for more information.
.TP
.IR /proc/[pid]/ns/ " (since Linux 3.0)"
.\" See commit 6b4e306aa3dc94a0545eb9279475b1ab6209a31f
This is a subdirectory containing one entry for each namespace that
supports being manipulated by
.BR setns (2).
-For information about namespaces, see
-.BR clone (2).
-.TP
-.IR /proc/[pid]/ns/ipc " (since Linux 3.0)"
-Bind mounting this file (see
-.BR mount (2))
-to somewhere else in the filesystem keeps
-the IPC namespace of the process specified by
-.I pid
-alive even if all processes currently in the namespace terminate.
+For more information, see
+.BR namespaces (7).
-Opening this file returns a file handle for the IPC namespace
-of the process specified by
-.IR pid .
-As long as this file descriptor remains open,
-the IPC namespace will remain alive,
-even if all processes in the namespace terminate.
-The file descriptor can be passed to
-.BR setns (2).
-.TP
-.IR /proc/[pid]/ns/net " (since Linux 3.0)"
-Bind mounting this file (see
-.BR mount (2))
-to somewhere else in the filesystem keeps
-the network namespace of the process specified by
-.I pid
-alive even if all processes in the namespace terminate.
-
-Opening this file returns a file handle for the network namespace
-of the process specified by
-.IR pid .
-As long as this file descriptor remains open,
-the network namespace will remain alive,
-even if all processes in the namespace terminate.
-The file descriptor can be passed to
-.BR setns (2).
-.TP
-.IR /proc/[pid]/ns/uts " (since Linux 3.0)"
-Bind mounting this file (see
-.BR mount (2))
-to somewhere else in the filesystem keeps
-the UTS namespace of the process specified by
-.I pid
-alive even if all processes currently in the namespace terminate.
-
-Opening this file returns a file handle for the UTS namespace
-of the process specified by
-.IR pid .
-As long as this file descriptor remains open,
-the UTS namespace will remain alive,
-even if all processes in the namespace terminate.
-The file descriptor can be passed to
-.BR setns (2).
.TP
.IR /proc/[pid]/numa_maps " (since Linux 2.6.14)"
See
(OOM_SCORE_ADJ_MIN) to +1000 (OOM_SCORE_ADJ_MAX).
This allows user space to control the preference for OOM-killing,
ranging from always preferring a certain
-task or completely disabling it from OOM-killing.
+task or completely disabling it from OOM killing.
The lowest possible value, \-1000, is
equivalent to disabling OOM-killing entirely for that task,
since it will always report a badness score of 0.
or
.IR /proc/[pid]/oom_adj
will change the other with its scaled value.
-.\" FIXME Describe /proc/[pid]/pagemap
-.\" Added in 2.6.25
-.\" CONFIG_PROC_PAGE_MONITOR
+.TP
+.IR /proc/[pid]/pagemap " (since Linux 2.6.25)"
+This file shows the mapping of each of the process's virtual pages
+into physical page frames or swap area.
+It contains one 64-bit value for each virtual page,
+with the bits set as follows:
+.RS 12
+.TP
+63
+If set, the page is present in RAM.
+.TP
+62
+If set, the page is in swap space
+.TP
+61 (since Linux 3.5)
+The page is a file-mapped page or a shared anonymous page.
+.TP
+60-56 (since Linux 3.11)
+Zero
+.\" Not quite true; see commit 541c237c0923f567c9c4cabb8a81635baadc713f
+.TP
+55 (Since Linux 3.11)
+PTE is soft-dirty
+(see the kernel source file
+.IR Documentation/vm/soft-dirty.txt ).
+.TP
+54-0
+If the page is present in RAM (bit 63), then these bits
+provide the page frame number, which can be used to index
+.IR /proc/kpageflags
+and
+.IR /proc/kpagecount .
+If the page is present in swap (bit 62),
+then bits 4-0 give the swap type, and bits 54-5 encode the swap offset.
+.RE
+.IP
+Before Linux 3.11, bits 60-55 were
+used to encode the base-2 log of the page size.
+.IP
+To employ
+.IR /proc/[pid]/pagemap
+efficiently, use
+.IR /proc/[pid]/maps
+to determine which areas of memory are actually mapped and seek
+to skip over unmapped regions.
+.IP
+The
+.IR /proc/[pid]/pagemap
+file is present only if the
+.B CONFIG_PROC_PAGE_MONITOR
+kernel configuration option is enabled.
+.TP
+.IR /proc/[pid]/personality " (since Linux 2.6.28)"
+.\" commit 478307230810d7e2a753ed220db9066dfdf88718
+This read-only file exposes the process's execution domain, as set by
+.BR personality (2).
+The value is displayed in hexadecimal notation.
.TP
.I /proc/[pid]/root
UNIX and Linux support the idea of a per-process root of the
are not available if the main thread has already terminated
(typically by calling
.BR pthread_exit (3)).
+.\" FIXME Describe /proc/[pid]/projid_map
+.\" Added in 3.7, commit f76d207a66c3a53defea67e7d36c3eb1b7d6d61d
.\" FIXME Describe /proc/[pid]/seccomp
.\" Added in 2.6.12
+.\"
.\" FIXME Describe /proc/[pid]/sessionid
.\" Added in 2.6.25; read-only; only readable by real UID
+.\" commit 1e0bd7550ea9cf474b1ad4c6ff5729a507f75fdc
.\" CONFIG_AUDITSYSCALL
+.\"
.\" FIXME Describe /proc/[pid]/sched
.\" Added in 2.6.23
.\" CONFIG_SCHED_DEBUG, and additional fields if CONFIG_SCHEDSTATS
.\" Displays various scheduling parameters
.\" This file can be written, to reset stats
+.\" The set of fields exposed by this file have changed
+.\" significantly over time.
+.\" commit 43ae34cb4cd650d1eb4460a8253a8e747ba052ac
+.\"
.\" FIXME Describe /proc/[pid]/schedstats and
.\" /proc/[pid]/task/[tid]/schedstats
.\" Added in 2.6.9
.TP
.IR /proc/[pid]/smaps " (since Linux 2.6.14)"
This file shows memory consumption for each of the process's mappings.
+(The
+.BR pmap (1)
+command displays similar information,
+in a form that may be easier for parsing.)
For each mapping there is a series of lines such as the following:
.in +4n
.nf
Status information about the process.
This is used by
.BR ps (1).
-It is defined in
-.IR /usr/src/linux/fs/proc/array.c "."
+It is defined in the kernel source file
+.IR fs/proc/array.c "."
The fields, in order, with their proper
.BR scanf (3)
format specifiers, are:
.RS
-.TP 12
-\fIpid\fP %d
-(1) The process ID.
+.TP 10
+(1) \fIpid\fP \ %d
+.br
+The process ID.
.TP
-\fIcomm\fP %s
-(2) The filename of the executable, in parentheses.
+(2) \fIcomm\fP \ %s
+The filename of the executable, in parentheses.
This is visible whether or not the executable is swapped out.
.TP
-\fIstate\fP %c
-(3) One character from the string "RSDZTW" where R is running, S is
-sleeping in an interruptible wait, D is waiting in uninterruptible
-disk sleep, Z is zombie, T is traced or stopped (on a signal),
-and W is paging.
+(3) \fIstate\fP \ %c
+One of the following characters, indicating process state:
+.RS
+.IP R 3
+Running
+.IP S
+Sleeping in an interruptible wait
+.IP D
+Waiting in uninterruptible
+disk sleep
+.IP Z
+Zombie
+.IP T
+Stopped (on a signal) or (before Linux 2.6.33) trace stopped
+.IP t
+.\" commit 44d90df6b757c59651ddd55f1a84f28132b50d29
+Tracing stop (Linux 2.6.33 onward)
+.IP W
+Paging (only before Linux 2.6.0)
+.IP X
+Dead (from Linux 2.6.0 onward)
+.IP x
+.\" commit 44d90df6b757c59651ddd55f1a84f28132b50d29
+Dead (Linux 2.6.33 to
+.\" commit 74e37200de8e9c4e09b70c21c3f13c2071e77457
+3.13 only)
+.IP K
+.\" commit 44d90df6b757c59651ddd55f1a84f28132b50d29
+Wakekill (Linux 2.6.33 to
+.\" commit 74e37200de8e9c4e09b70c21c3f13c2071e77457
+3.13 only)
+.IP W
+.\" commit 44d90df6b757c59651ddd55f1a84f28132b50d29
+Waking (Linux 2.6.33 to
+.\" commit 74e37200de8e9c4e09b70c21c3f13c2071e77457
+3.13 only)
+.IP P
+.\" commit f2530dc71cf0822f90bb63ea4600caaef33a66bb
+Parked (Linux 3.9 to
+.\" commit 74e37200de8e9c4e09b70c21c3f13c2071e77457
+3.13 only)
+.RE
.TP
-\fIppid\fP %d
-(4) The PID of the parent.
+(4) \fIppid\fP \ %d
+The PID of the parent of this process.
.TP
-\fIpgrp\fP %d
-(5) The process group ID of the process.
+(5) \fIpgrp\fP \ %d
+The process group ID of the process.
.TP
-\fIsession\fP %d
-(6) The session ID of the process.
+(6) \fIsession\fP \ %d
+The session ID of the process.
.TP
-\fItty_nr\fP %d
-(7) The controlling terminal of the process.
+(7) \fItty_nr\fP \ %d
+The controlling terminal of the process.
(The minor device number is contained in the combination of bits
31 to 20 and 7 to 0;
the major device number is in bits 15 to 8.)
.TP
-\fItpgid\fP %d
+(8) \fItpgid\fP \ %d
.\" This field and following, up to and including wchan added 0.99.1
-(8) The ID of the foreground process group of the controlling
+The ID of the foreground process group of the controlling
terminal of the process.
.TP
-\fIflags\fP %u (%lu before Linux 2.6.22)
-(9) The kernel flags word of the process.
+(9) \fIflags\fP \ %u
+The kernel flags word of the process.
For bit meanings,
see the PF_* defines in the Linux kernel source file
.IR include/linux/sched.h .
Details depend on the kernel version.
+
+The format for this field was %lu before Linux 2.6.
.TP
-\fIminflt\fP %lu
-(10) The number of minor faults the process has made which have not
+(1) \fIminflt\fP \ %lu
+The number of minor faults the process has made which have not
required loading a memory page from disk.
.TP
-\fIcminflt\fP %lu
-(11) The number of minor faults that the process's
+(11) \fIcminflt\fP \ %lu
+The number of minor faults that the process's
waited-for children have made.
.TP
-\fImajflt\fP %lu
-(12) The number of major faults the process has made which have
+(12) \fImajflt\fP \ %lu
+The number of major faults the process has made which have
required loading a memory page from disk.
.TP
-\fIcmajflt\fP %lu
-(13) The number of major faults that the process's
+(13) \fIcmajflt\fP \ %lu
+The number of major faults that the process's
waited-for children have made.
.TP
-\fIutime\fP %lu
-(14) Amount of time that this process has been scheduled in user mode,
+(14) \fIutime\fP \ %lu
+Amount of time that this process has been scheduled in user mode,
measured in clock ticks (divide by
.IR sysconf(_SC_CLK_TCK) ).
This includes guest time, \fIguest_time\fP
so that applications that are not aware of the guest time field
do not lose that time from their calculations.
.TP
-\fIstime\fP %lu
-(15) Amount of time that this process has been scheduled in kernel mode,
+(15) \fIstime\fP \ %lu
+Amount of time that this process has been scheduled in kernel mode,
measured in clock ticks (divide by
.IR sysconf(_SC_CLK_TCK) ).
.TP
-\fIcutime\fP %ld
-(16) Amount of time that this process's
+(16) \fIcutime\fP \ %ld
+Amount of time that this process's
waited-for children have been scheduled in user mode,
measured in clock ticks (divide by
.IR sysconf(_SC_CLK_TCK) ).
This includes guest time, \fIcguest_time\fP
(time spent running a virtual CPU, see below).
.TP
-\fIcstime\fP %ld
-(17) Amount of time that this process's
+(17) \fIcstime\fP \ %ld
+Amount of time that this process's
waited-for children have been scheduled in kernel mode,
measured in clock ticks (divide by
.IR sysconf(_SC_CLK_TCK) ).
.TP
-\fIpriority\fP %ld
-(18) (Explanation for Linux 2.6)
+(18) \fIpriority\fP \ %ld
+(Explanation for Linux 2.6)
For processes running a real-time scheduling policy
.RI ( policy
below; see
the scheduler weighting given to this process.
.\" And back in kernel 1.2 days things were different again.
.TP
-\fInice\fP %ld
-(19) The nice value (see
+(19) \fInice\fP \ %ld
+The nice value (see
.BR setpriority (2)),
a value in the range 19 (low priority) to \-20 (high priority).
.\" Back in kernel 1.2 days things were different.
.\" The time in jiffies of the process's next timeout.
.\" timeout was removed sometime around 2.1/2.2
.TP
-\fInum_threads\fP %ld
-(20) Number of threads in this process (since Linux 2.6).
+(20) \fInum_threads\fP \ %ld
+Number of threads in this process (since Linux 2.6).
Before kernel 2.6, this field was hard coded to 0 as a placeholder
for an earlier removed field.
.TP
-\fIitrealvalue\fP %ld
-(21) The time in jiffies before the next
+(21) \fIitrealvalue\fP \ %ld
+The time in jiffies before the next
.B SIGALRM
is sent to the process due to an interval timer.
Since kernel 2.6.17, this field is no longer maintained,
and is hard coded as 0.
.TP
-\fIstarttime\fP %llu (was %lu before Linux 2.6)
-(22) The time the process started after system boot.
+(22) \fIstarttime\fP \ %llu
+The time the process started after system boot.
In kernels before Linux 2.6, this value was expressed in jiffies.
Since Linux 2.6, the value is expressed in clock ticks (divide by
.IR sysconf(_SC_CLK_TCK) ).
+
+The format for this field was %lu before Linux 2.6.
.TP
-\fIvsize\fP %lu
-(23) Virtual memory size in bytes.
+(23) \fIvsize\fP \ %lu
+Virtual memory size in bytes.
.TP
-\fIrss\fP %ld
-(24) Resident Set Size: number of pages the process has in real memory.
+(24) \fIrss\fP \ %ld
+Resident Set Size: number of pages the process has in real memory.
This is just the pages which
count toward text, data, or stack space.
This does not include pages
which have not been demand-loaded in, or which are swapped out.
.TP
-\fIrsslim\fP %lu
-(25) Current soft limit in bytes on the rss of the process;
+(25) \fIrsslim\fP \ %lu
+Current soft limit in bytes on the rss of the process;
see the description of
.B RLIMIT_RSS
in
.BR getrlimit (2).
.TP
-\fIstartcode\fP %lu
-(26) The address above which program text can run.
+(26) \fIstartcode\fP \ %lu
+The address above which program text can run.
.TP
-\fIendcode\fP %lu
-(27) The address below which program text can run.
+(27) \fIendcode\fP \ %lu
+The address below which program text can run.
.TP
-\fIstartstack\fP %lu
-(28) The address of the start (i.e., bottom) of the stack.
+(28) \fIstartstack\fP \ %lu
+The address of the start (i.e., bottom) of the stack.
.TP
-\fIkstkesp\fP %lu
-(29) The current value of ESP (stack pointer), as found in the
+(29) \fIkstkesp\fP \ %lu
+The current value of ESP (stack pointer), as found in the
kernel stack page for the process.
.TP
-\fIkstkeip\fP %lu
-(30) The current EIP (instruction pointer).
+(30) \fIkstkeip\fP \ %lu
+The current EIP (instruction pointer).
.TP
-\fIsignal\fP %lu
-(31) The bitmap of pending signals, displayed as a decimal number.
+(31) \fIsignal\fP \ %lu
+The bitmap of pending signals, displayed as a decimal number.
Obsolete, because it does not provide information on real-time signals; use
.I /proc/[pid]/status
instead.
.TP
-\fIblocked\fP %lu
-(32) The bitmap of blocked signals, displayed as a decimal number.
+(32) \fIblocked\fP \ %lu
+The bitmap of blocked signals, displayed as a decimal number.
Obsolete, because it does not provide information on real-time signals; use
.I /proc/[pid]/status
instead.
.TP
-\fIsigignore\fP %lu
-(33) The bitmap of ignored signals, displayed as a decimal number.
+(33) \fIsigignore\fP \ %lu
+The bitmap of ignored signals, displayed as a decimal number.
Obsolete, because it does not provide information on real-time signals; use
.I /proc/[pid]/status
instead.
.TP
-\fIsigcatch\fP %lu
-(34) The bitmap of caught signals, displayed as a decimal number.
+(34) \fIsigcatch\fP \ %lu
+The bitmap of caught signals, displayed as a decimal number.
Obsolete, because it does not provide information on real-time signals; use
.I /proc/[pid]/status
instead.
.TP
-\fIwchan\fP %lu
-(35) This is the "channel" in which the process is waiting.
+(35) \fIwchan\fP \ %lu
+This is the "channel" in which the process is waiting.
It is the address of a location in the kernel where the process is sleeping.
The corresponding symbolic name can be found in
.IR /proc/[pid]/wchan .
.TP
-\fInswap\fP %lu
-(36)
+(36) \fInswap\fP \ %lu
.\" nswap was added in 2.0
Number of pages swapped (not maintained).
.TP
-\fIcnswap\fP %lu
-(37)
+(37) \fIcnswap\fP \ %lu
.\" cnswap was added in 2.0
Cumulative \fInswap\fP for child processes (not maintained).
.TP
-\fIexit_signal\fP %d (since Linux 2.1.22)
-(38) Signal to be sent to parent when we die.
+(38) \fIexit_signal\fP \ %d \ (since Linux 2.1.22)
+Signal to be sent to parent when we die.
.TP
-\fIprocessor\fP %d (since Linux 2.2.8)
-(39) CPU number last executed on.
+(39) \fIprocessor\fP \ %d \ (since Linux 2.2.8)
+CPU number last executed on.
.TP
-\fIrt_priority\fP %u (since Linux 2.5.19; was %lu before Linux 2.6.22)
-(40) Real-time scheduling priority, a number in the range 1 to 99 for
+(40) \fIrt_priority\fP \ %u \ (since Linux 2.5.19)
+Real-time scheduling priority, a number in the range 1 to 99 for
processes scheduled under a real-time policy,
or 0, for non-real-time processes (see
.BR sched_setscheduler (2)).
.TP
-\fIpolicy\fP %u (since Linux 2.5.19; was %lu before Linux 2.6.22)
-(41) Scheduling policy (see
+(41) \fIpolicy\fP \ %u \ (since Linux 2.5.19)
+Scheduling policy (see
.BR sched_setscheduler (2)).
Decode using the SCHED_* constants in
.IR linux/sched.h .
+
+The format for this field was %lu before Linux 2.6.22.
.TP
-\fIdelayacct_blkio_ticks\fP %llu (since Linux 2.6.18)
-(42) Aggregated block I/O delays, measured in clock ticks (centiseconds).
+(42) \fIdelayacct_blkio_ticks\fP \ %llu \ (since Linux 2.6.18)
+Aggregated block I/O delays, measured in clock ticks (centiseconds).
.TP
-\fIguest_time\fP %lu (since Linux 2.6.24)
-(43) Guest time of the process (time spent running a virtual CPU
+(43) \fIguest_time\fP \ %lu \ (since Linux 2.6.24)
+Guest time of the process (time spent running a virtual CPU
for a guest operating system), measured in clock ticks (divide by
.IR sysconf(_SC_CLK_TCK) ).
.TP
-\fIcguest_time\fP %ld (since Linux 2.6.24)
-(44) Guest time of the process's children, measured in clock ticks (divide by
+(44) \fIcguest_time\fP \ %ld \ (since Linux 2.6.24)
+Guest time of the process's children, measured in clock ticks (divide by
.IR sysconf(_SC_CLK_TCK) ).
+.TP
+(45) \fIstart_data\fP \ %lu \ (since Linux 3.3)
+.\" commit b3f7f573a20081910e34e99cbc91831f4f02f1ff
+Address above which program initialized and
+uninitialized (BSS) data are placed.
+.TP
+(46) \fIend_data\fP \ %lu \ (since Linux 3.3)
+.\" commit b3f7f573a20081910e34e99cbc91831f4f02f1ff
+Address below which program initialized and
+uninitialized (BSS) data are placed.
+.TP
+(47) \fIstart_brk\fP \ %lu \ (since Linux 3.3)
+.\" commit b3f7f573a20081910e34e99cbc91831f4f02f1ff
+Address above which program heap can be expanded with
+.BR brk (2).
+.TP
+(48) \fIarg_start\fP \ %lu \ (since Linux 3.5)
+.\" commit 5b172087f99189416d5f47fd7ab5e6fb762a9ba3
+Address above which program command-line arguments
+.RI ( argv )
+are placed.
+.TP
+(49) \fIarg_end\fP \ %lu \ (since Linux 3.5)
+.\" commit 5b172087f99189416d5f47fd7ab5e6fb762a9ba3
+Address below program command-line arguments
+.RI ( argv )
+are placed.
+.TP
+(50) \fIenv_start\fP \ %lu \ (since Linux 3.5)
+.\" commit 5b172087f99189416d5f47fd7ab5e6fb762a9ba3
+Address above which program environment is placed.
+.TP
+(51) \fIenv_end\fP \ %lu \ (since Linux 3.5)
+.\" commit 5b172087f99189416d5f47fd7ab5e6fb762a9ba3
+Address below which program environment is placed.
+.TP
+(52) \fIexit_code\fP \ %d \ (since Linux 3.5)
+.\" commit 5b172087f99189416d5f47fd7ab5e6fb762a9ba3
+The thread's exit status in the form reported by
+.BR waitpid (2).
.RE
.TP
.I /proc/[pid]/statm
.IP *
.IR CapBnd :
Capability Bounding set
-(since kernel 2.6.26, see
+(since Linux 2.6.26, see
.BR capabilities (7)).
.IP *
.IR Cpus_allowed :
(since Linux 2.6.26, see
.BR cpuset (7)).
.IP *
-.IR voluntary_context_switches ", " nonvoluntary_context_switches :
+.IR voluntary_ctxt_switches ", " nonvoluntary_ctxt_switches :
Number of voluntary and involuntary context switches (since Linux 2.6.23).
.RE
.TP
+.IR /proc/[pid]/syscall " (since Linux 2.6.27)"
+.\" commit ebcb67341fee34061430f3367f2e507e52ee051b
+This file exposes the system call number and argument registers for the
+system call currently being executed by the process,
+followed by the values of the stack pointer and program counter registers.
+The values of all six argument registers are exposed,
+although most system calls use fewer registers.
+
+If the process is blocked, but not in a system call,
+then the file displays -1 in place of the system call number,
+followed by just the values of the stack pointer and program counter.
+If process is not blocked, then file contains just the string "running".
+
+This file is present only if the kernel was configured with
+.BR CONFIG_HAVE_ARCH_TRACEHOOK .
+.TP
.IR /proc/[pid]/task " (since Linux 2.6.0-test6)"
This is a directory that contains one subdirectory
for each thread in the process.
(typically by calling
.BR pthread_exit (3)).
.TP
+.IR /proc/[pid]/uid_map ", " /proc/[pid]/gid_map " (since Linux 3.5)"
+.\" commit 22d917d80e842829d0ca0a561967d728eb1d6303
+These files expose the mappings for user and group IDs
+inside the user namespace for the process
+.IR pid .
+The description here explains the details for
+.IR uid_map ;
+.IR gid_map
+is exactly the same,
+but each instance of "user ID" is replaced by "group ID".
+
+The
+.I uid_map
+file exposes the mapping of user IDs from the user namespace
+of the process
+.IR pid
+to the user namespace of the process that opened
+.IR uid_map
+(but see a qualification to this point below).
+In other words, processes that are in different user namespaces
+will potentially see different values when reading from a particular
+.I uid_map
+file, depending on the user ID mappings for the user namespaces
+of the reading processes.
+
+
+Each line in the file specifies a 1-to-1 mapping of a range of contiguous
+between two user namespaces.
+The specification in each line takes the form of
+three numbers delimited by white space.
+The first two numbers specify the starting user ID in
+each user namespace.
+The third number specifies the length of the mapped range.
+In detail, the fields are interpreted as follows:
+.RS
+.IP (1) 4
+The start of the range of user IDs in
+the user namespace of the process
+.IR pid .
+.IP (2)
+The start of the range of user
+IDs to which the user IDs specified by field one map.
+How field two is interpreted depends on whether the process that opened
+.I uid_map
+and the process
+.IR pid
+are in the same user namespace, as follows:
+.RS
+.IP a) 3
+If the two processes are in different user namespaces:
+field two is the start of a range of
+user IDs in the user namespace of the process that opened
+.IR uid_map .
+.IP b)
+If the two processes are in the same user namespace:
+field two is the start of the range of
+user IDs in the parent user namespace of the process
+.IR pid .
+(The "parent user namespace"
+is the user namespace of the process that created a user namespace
+via a call to
+.BR unshare (2)
+or
+.BR clone (2)
+with the
+.BR CLONE_NEWUSER
+flag.)
+This case enables the opener of
+.I uid_map
+(the common case here is opening
+.IR /proc/self/uid_map )
+to see the mapping of user IDs into the user namespace of the process
+that created this user namespace.
+.RE
+.IP (3)
+The length of the range of user IDs that is mapped between the two
+user namespaces.
+.RE
+.IP
+After the creation of a new user namespace, the
+.I uid_map
+file may be written to exactly once to specify
+the mapping of user IDs in the new user namespace.
+(An attempt to write more than once to the file fails with the error
+.BR EPERM .)
+.IP
+The lines written to
+.IR uid_map
+must conform to the following rules:
+.RS
+.IP * 3
+The three fields must be valid numbers,
+and the last field must be greater than 0.
+.IP *
+Lines are terminated by newline characters.
+.IP *
+There is an (arbitrary) limit on the number of lines in the file.
+As at Linux 3.8, the limit is five lines.
+.IP *
+The range of user IDs specified in each line cannot overlap with the ranges
+in any other lines.
+In the current implementation (Linux 3.8), this requirement is
+satisfied by a simplistic implementation that imposes the further
+requirement that
+the values in both field 1 and field 2 of successive lines must be
+in ascending numerical order.
+.RE
+.IP
+Writes that violate the above rules fail with the error
+.BR EINVAL .
+
+In order for a process to write to the
+.I /proc/[pid]/uid_map
+.RI ( /proc/[pid]/gid_map )
+file, the following requirements must be met:
+.RS
+.IP * 3
+The process must have the
+.BR CAP_SETUID
+.RB ( CAP_SETGID )
+capability in the user namespace of the process
+.IR pid .
+.IP *
+The process must have the
+.BR CAP_SETUID
+.RB ( CAP_SETGID )
+capability in the parent user namespace.
+.IP *
+The process must be in either the user namespace of the process
+.I pid
+or inside the parent user namespace of the process
+.IR pid .
+.RE
+For further details, see
+.BR namespaces (7).
+.TP
.IR /proc/[pid]/wchan " (since Linux 2.6.0)"
The symbolic name corresponding to the location
in the kernel where the process is sleeping.
.B CONFIG_APM
is defined at kernel compilation time.
.TP
+.I /proc/buddyinfo
+This file contains information which is used for diagnosing memory
+fragmentation issues.
+Each line starts with the identification of the node and the name
+of the zone which together identify a memory region
+This is then
+followed by the count of available chunks of a certain order in
+which these zones are split.
+The size in bytes of a certain order is given by the formual:
+
+ (2^order)\ *\ PAGE_SIZE
+
+The binary buddy allocator algorithm inside the kernel will split
+one chunk into two chunks of a smaller order (thus with half the
+size) or combine two contiguous chunks into one larger chunk of
+a higher order (thus with double the size) to satisfy allocation
+requests and to counter memory fragmentation.
+The order matches the column number, when starting to count at zero.
+
+For example on a x86_64 system:
+
+.in -12n
+.nf
+Node 0, zone DMA 1 1 1 0 2 1 1 0 1 1 3
+Node 0, zone DMA32 65 47 4 81 52 28 13 10 5 1 404
+Node 0, zone Normal 216 55 189 101 84 38 37 27 5 3 587
+.fi
+.in
+
+In this example, there is one node containing three zones and there
+are 11 different chunk sizes.
+If the page size is 4 kilobyteis, then the first zone called
+.I DMA
+(on x86 the first 16 megabyte of memory) has 1 chunk of 4 kilobytes
+(order 0) available and has 3 chunks of 4 megabytes (order 10) available.
+
+If the memory is heavily fragmentated, the counters for higher
+order chunks will be zero and allocation of large contiguous areas
+will fail.
+
+Further information about the zones can be found in
+.IR /proc/zoneinfo .
+.TP
.I /proc/bus
Contains subdirectories for installed busses.
.TP
(excepted those that are marked with "nodev").
.TP
.I /proc/fs
-Empty subdirectory.
+.\" FIXME Much more needs to be said about /proc/fs
+.\"
+Contains subdirectories that in turn contain files
+with information about (certain) mounted filesystems.
.TP
.I /proc/ide
This directory
.BR dmesg (1)
program.
.TP
+.IR /proc/kpagecount " (since Linux 2.6.25)"
+This file contains a 64-bit count of the number of
+times each physical page frame is mapped,
+indexed by page frame number (see the discussion of
+.IR /proc/[pid]/pagemap ).
+.IP
+The
+.IR /proc/kpagecount
+file is present only if the
+.B CONFIG_PROC_PAGE_MONITOR
+kernel configuration option is enabled.
+.TP
+.IR /proc/kpageflags " (since Linux 2.6.25)"
+This file contains 64-bit masks corresponding to each physical page frame;
+it is indexed by page frame number (see the discussion of
+.IR /proc/[pid]/pagemap ).
+The bits are as follows:
+
+ 0 - KPF_LOCKED
+ 1 - KPF_ERROR
+ 2 - KPF_REFERENCED
+ 3 - KPF_UPTODATE
+ 4 - KPF_DIRTY
+ 5 - KPF_LRU
+ 6 - KPF_ACTIVE
+ 7 - KPF_SLAB
+ 8 - KPF_WRITEBACK
+ 9 - KPF_RECLAIM
+ 10 - KPF_BUDDY
+ 11 - KPF_MMAP (since Linux 2.6.31)
+ 12 - KPF_ANON (since Linux 2.6.31)
+ 13 - KPF_SWAPCACHE (since Linux 2.6.31)
+ 14 - KPF_SWAPBACKED (since Linux 2.6.31)
+ 15 - KPF_COMPOUND_HEAD (since Linux 2.6.31)
+ 16 - KPF_COMPOUND_TAIL (since Linux 2.6.31)
+ 16 - KPF_HUGE (since Linux 2.6.31)
+ 18 - KPF_UNEVICTABLE (since Linux 2.6.31)
+ 19 - KPF_HWPOISON (since Linux 2.6.31)
+ 20 - KPF_NOPAGE (since Linux 2.6.31)
+ 21 - KPF_KSM (since Linux 2.6.32)
+ 22 - KPF_THP (since Linux 3.4)
+
+For further details on the meanings of these bits,
+see the kernel source file
+.IR Documentation/vm/pagemap.txt .
+Before kernel 2.6.29,
+.\" commit ad3bdefe877afb47480418fdb05ecd42842de65e
+.\" commit e07a4b9217d1e97d2f3a62b6b070efdc61212110
+.BR KPF_WRITEBACK ,
+.BR KPF_RECLAIM ,
+.BR KPF_BUDDY ,
+and
+.BR KPF_LOCKED
+did not report correctly.
+.IP
+The
+.IR /proc/kpageflags
+file is present only if the
+.B CONFIG_PROC_PAGE_MONITOR
+kernel configuration option is enabled.
+.TP
.IR /proc/ksyms " (Linux 1.1.23-2.5.47)"
See
.IR /proc/kallsyms .
Memory used by FUSE for temporary writeback buffers.
.TP
.IR CommitLimit " %lu (since Linux 2.6.10)"
-Based on the overcommit ratio ('vm.overcommit_ratio'),
-this is the total amount of memory currently available to
-be allocated on the system.
+This is the total amount of memory currently available to
+be allocated on the system, expressed in kilobytes.
This limit is adhered to
only if strict overcommit accounting is enabled (mode 2 in
-.IR /proc/sys/vm/overcommit_ratio ).
-The
-.I CommitLimit
-is calculated using the following formula:
-
- CommitLimit =
- ([total RAM pages] - [total huge TLB pages]) *
- overcommit_ratio / 100 + [total swap pages]
-
-For example, on a system with 1GB of physical RAM and 7GB
-of swap with a
-.I overcommit_ratio
-of 30, this formula yields a
-.I CommitLimit
-of 7.3GB.
-For more details, see the memory overcommit documentation
-in the kernel source file
+.IR /proc/sys/vm/overcommit_memory ).
+The limit is calculated according to the formula described under
+.IR /proc/sys/vm/overcommit_memory .
+For further details, see the kernel source file
.IR Documentation/vm/overcommit-accounting .
.TP
.IR Committed_AS " %lu"
or similar), but touches only 300MB of that memory will show up
as using only 300MB of memory even if it has the address space
allocated for the entire 1GB.
+
This 1GB is memory which has been "committed" to by the VM
and can be used at any time by the allocating application.
-With strict overcommit enabled on the system (mode 2
-.IR /proc/sys/vm/overcommit_memory ),
+With strict overcommit enabled on the system (mode 2 in
+IR /proc/sys/vm/overcommit_memory ),
allocations which would exceed the
.I CommitLimit
-(detailed above) will not be permitted.
+will not be permitted.
This is useful if one needs to guarantee that processes will not
fail due to lack of memory once that memory has been successfully allocated.
.TP
Next, it was deprecated in Linux 2.6 (still available with
.B CONFIG_PCI_LEGACY_PROC
set), and finally removed altogether since Linux 2.6.17.
-.\" FIXME /proc/sched_debug
+.\" FIXME Document /proc/sched_debug
+.\"
.\" .TP
.\" .IR /proc/sched_debug " (since Linux 2.6.23)"
.\" See also /proc/[pid]/sched
.TP
.I idle
(4) Time spent in the idle task.
-.\" FIXME Actually, the following info about the /proc/stat 'cpu' field
+.\" FIXME . Actually, the following info about the /proc/stat 'cpu' field
.\" does not seem to be quite right (at least in 2.6.12 or 3.6):
.\" the idle time in /proc/uptime does not quite match this value
This value should be USER_HZ times the
\fIswap 1 0\fP
The number of swap pages that have been brought in and out.
.TP
-.\" FIXME The following is not the full picture for the 'intr' of
+.\" FIXME . The following is not the full picture for the 'intr' of
.\" /proc/stat on 2.6:
\fIintr 1462898\fP
This line shows counts of interrupts serviced since boot time,
.\" commit 800179c9b8a1e796e441674776d11cd4c05d61d7
When the value in this file is 0,
no restrictions are placed on the creation of hard links
-(i.e., this is the historical behaviour before Linux 3.6).
+(i.e., this is the historical behavior before Linux 3.6).
When the value in this file is 1,
a hard link can be created to a target file
only if one of the following conditions is true:
.\" commit 800179c9b8a1e796e441674776d11cd4c05d61d7
When the value in this file is 0,
no restrictions are placed on following symbolic links
-(i.e., this is the historical behaviour before Linux 3.6).
+(i.e., this is the historical behavior before Linux 3.6).
When the value in this file is 1, symbolic links are followed only
in the following circumstances:
.RS
controls the handling of Ctrl-Alt-Del from the keyboard.
When the value in this file is 0, Ctrl-Alt-Del is trapped and
sent to the
-.BR init (8)
+.BR init (1)
program to handle a graceful restart.
When the value is greater than zero, Linux's reaction to a Vulcan
Nerve Pinch (tm) will be an immediate reboot, without even
.IR /proc/sys/kernel/pid_max " (since Linux 2.5.34)"
This file specifies the value at which PIDs wrap around
(i.e., the value in this file is one greater than the maximum PID).
-PIDs greater than this value not allocated;
+PIDs greater than this value are not allocated;
thus, the value in this file also acts as a system-wide limit
on the total number of processes and threads.
The default value for this file, 32768,
otherwise the "doze" mode will be used.
.TP
.I /proc/sys/kernel/printk
-The four values in this file are
-.IR console_loglevel ,
-.IR default_message_loglevel ,
-.IR minimum_console_level ,
-and
-.IR default_console_loglevel .
-These values influence
-.I printk()
-behavior when printing or logging error messages.
See
-.BR syslog (2)
-for more info on the different loglevels.
-Messages with a higher priority than
-.I console_loglevel
-will be printed to the console.
-Messages without an explicit priority will be printed with priority
-.IR default_message_level .
-.I minimum_console_loglevel
-is the minimum (highest) value to which
-.I console_loglevel
-can be set.
-.I default_console_loglevel
-is the default value for
-.IR console_loglevel .
+.BR syslog (2).
.TP
.IR /proc/sys/kernel/pty " (since Linux 2.6.4)"
This directory contains two files relating to the number of UNIX 98
Because writing to this file is a nondestructive operation and dirty objects
are not freeable, the
user should run
-.BR sync (8)
+.BR sync (1)
first.
.TP
.IR /proc/sys/vm/legacy_va_layout " (since Linux 2.6.9)"
The default value is 0.
.TP
+.IR /proc/sys/vm/overcommit_kbytes " (since Linux 3.14)"
+.\" commit 49f0ce5f92321cdcf741e35f385669a421013cb7
+This writable file provides an alternative to
+.IR /proc/sys/vm/overcommit_ratio
+for controlling the
+.I CommitLimit
+when
+.IR /proc/sys/vm/overcommit_memory
+has the value 2.
+It allows the amount of memory overcommitting to be specified as
+an absolute value (in kB),
+rather than as a percentage, as is done with
+.IR overcommit_ratio .
+This allows for finer-grained control of
+.IR CommitLimit
+on systems with extremely large memory sizes.
+
+Only one of
+.IR overcommit_kbytes
+or
+.IR overcommit_ratio
+can have an effect:
+if
+.IR overcommit_kbytes
+has a nonzero value, then it is used to calculate
+.IR CommitLimit ,
+otherwise
+.IR overcommit_ratio
+is used.
+Writing a value to either of these files causes the
+value in the other file to be set to zero.
+.TP
.I /proc/sys/vm/overcommit_memory
This file contains the kernel virtual memory accounting mode.
Values are:
.B MAP_NORESERVE
are not checked, and the default check is very weak,
leading to the risk of getting a process "OOM-killed".
-Under Linux 2.4 any nonzero value implies mode 1.
+Under Linux 2.4, any nonzero value implies mode 1.
+
In mode 2 (available since Linux 2.6), the total virtual address space
-on the system is limited to (SS + RAM*(r/100)),
-where SS is the size of the swap space, and RAM
-is the size of the physical memory, and r is the contents of the file
-.IR /proc/sys/vm/overcommit_ratio .
+that can be allocated
+.RI ( CommitLimit
+in
+.IR /proc/meminfo )
+is calculated as
+
+ CommitLimit = (total_RAM - total_huge_TLB) *
+ overcommit_ratio / 100 + total_swap
+
+where:
+.RS 12
+.IP * 3
+.I total_RAM
+is the total amount of RAM on the system;
+.IP *
+.I total_huge_TLB
+is the amount of memory set aside for huge pages;
+.IP *
+.I overcommit_ratio
+is the value in
+.IR /proc/sys/vm/overcommit_ratio ;
+and
+.IP *
+.I total_swap
+is the amount of swap space.
+.RE
+.IP
+For example, on a system with 16GB of physical RAM, 16GB
+of swap, no space dedicated to huge pages, and an
+.I overcommit_ratio
+of 50, this formula yields a
+.I CommitLimit
+of 24GB.
+
+Since Linux 3.14, if the value in
+.I /proc/sys/vm/overcommit_kbytes
+is nonzero, then
+.I CommitLimit
+is instead calculated as:
+
+ CommitLimit = overcommit_kbytes + total_swap
.TP
-.I /proc/sys/vm/overcommit_ratio
+.IR /proc/sys/vm/overcommit_ratio " (since Linux 2.6.0)"
+This writable file defines a percentage by which memory
+can be overcommitted.
+The default value in the file is 50.
See the description of
.IR /proc/sys/vm/overcommit_memory .
.TP
file is used both to control sampling facility and to read out the
sampled information.
-timer_stats collects information about the timer events which are fired in a
-Linux system over a sample period:
-
-- the pid of the task(process) which initialized the timer
-- the name of the process which initialized the timer
-- the function where the timer was initialized
-- the callback function which is associated to the timer
-- the number of events (callbacks)
-
The timer_stats functionality is inactive on bootup.
A sampling period can be started using the following command:
$ cat /proc/timer_stats
-While sampling is enabled, each readout from /proc/timer_stats will see
+While sampling is enabled, each readout from
+.I /proc/timer_stats
+will see
newly updated statistics.
Once sampling is disabled, the sampled information
is kept until a new sample period is started.
.ft
.in +2
.fi
-.\" FIXME Document /proc/timer_list
-.\" .TP
-.\" .IR /proc/timer_list " (since Linux 2.6.21)"
-.\" See the 2.6.21 Change log
-.\" FIXME Document /proc/timer_stats
-.\" .TP
-.\" .IR /proc/timer_stats " (since Linux 2.6.21)"
-.\" See the 2.6.21 Change log
+.\" FIXME 2.6.13 seems to have /proc/vmcore implemented; document this
+.\" See Documentation/kdump/kdump.txt
+.\" commit 666bfddbe8b8fd4fd44617d6c55193d5ac7edb29
+.\" Needs CONFIG_VMCORE
+.\"
.TP
.IR /proc/vmstat " (since Linux 2.6)"
This file displays various virtual memory statistics.
.BR syslog (2),
.BR slabinfo (5),
.BR hier (7),
+.BR namespaces (7),
.BR time (7),
.BR arp (8),
.BR hdparm (8),
.BR ifconfig (8),
-.BR init (8),
+.BR init (1),
.BR lsmod (8),
.BR lspci (8),
.BR mount (8),
and
.IR Documentation/sysctl/vm.txt .
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.UR http://www.iana.org\:/assignments\:/protocol-numbers
.UE
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
--- /dev/null
+.\"
+.\" %%%LICENSE_START(GPLv2+_DOC_FULL)
+.\" This is free documentation; you can redistribute it and/or
+.\" modify it under the terms of the GNU General Public License as
+.\" published by the Free Software Foundation; either version 2 of
+.\" the License, or (at your option) any later version.
+.\"
+.\" The GNU General Public License's references to "object code"
+.\" and "executables" are to be interpreted as the output of any
+.\" document formatting or typesetting system, including
+.\" intermediate and printed output.
+.\"
+.\" This manual is distributed in the hope that it will be useful,
+.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
+.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+.\" GNU General Public License for more details.
+.\"
+.\" You should have received a copy of the GNU General Public
+.\" License along with this manual; if not, see
+.\" <http://www.gnu.org/licenses/>.
+.\" %%%LICENSE_END
+.\"
+.TH REPERTOIREMAP 5 2014-06-02 "GNU" "Linux User Manual"
+.SH NAME
+repertoiremap \- map symbolic character names to Unicode code points
+.SH DESCRIPTION
+A repertoire map defines mappings between symbolic character names and
+Unicode code points when compiling a locale with
+.BR localedef (1).
+Using a repertoire map is optional, it is only needed when symbolic
+names are used instead of now preferred Unicode code points.
+.SS Syntax
+The repertoiremap file starts with a header that may consist of the
+following keywords:
+.TP
+.I <comment_char>
+is followed by a character that will be used as the
+comment character for the rest of the file.
+It defaults to the number sign (#).
+.TP
+.I <escape_char>
+is followed by a character that should be used as the escape character
+for the rest of the file to mark characters that should be interpreted
+in a special way.
+It defaults to the backslash (\\).
+.PP
+The mapping section starts with the keyword
+.B CHARIDS
+in the first column.
+
+The mapping lines have the following form:
+.TP
+.I <symbolic-name> <code-point> <comment>
+This defines exactly one mapping,
+.I <comment>
+being optional.
+.PP
+The mapping section ends with the string
+.IR "END CHARIDS" .
+.SH FILES
+.TP
+.I /usr/share/i18n/repertoiremaps
+Usual default repertoire map path.
+.SH CONFORMING TO
+POSIX.2.
+.SH NOTES
+Repertoire maps are deprecated in favor of Unicode code points.
+.SH SEE ALSO
+.BR locale (1),
+.BR localedef (1),
+.BR charmap (5),
+.BR locale (5)
+.SH COLOPHON
+This page is part of release 3.75 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.
.br
Name Server Operations Guide for BIND
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR getrpcent (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR login (1),
.BR login.defs (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
Assigned Numbers RFC, most recently RFC\ 1700, (AKA STD0002).
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR chsh (1),
.BR getusershell (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.B CONFIG_SLAB
kernel configuration option is enabled.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR termcap (3),
.BR terminfo (5)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR agetty (8),
.BR mingetty (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.I timezone/tzfile.h
in the glibc source tree
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified 1996-07-20 by Michael Haardt
.\" Modified 1997-07-02 by Nicolás Lichtmaier <nick@debian.org>
.\" Modified 2004-10-31 by aeb, following Gwenole Beauchesne
-.TH UTMP 5 2013-02-11 "Linux" "Linux Programmer's Manual"
+.TH UTMP 5 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
utmp, wtmp \- login records
.SH SYNOPSIS
messages */
struct exit_status ut_exit; /* Exit status of a process
marked as DEAD_PROCESS; not
- used by Linux init(8) */
+ used by Linux init (1 */
/* The ut_session and ut_tv fields must be the same size when
compiled 32- and 64-bit. This allows data files and shared
memory to be shared between 32- and 64-bit applications. */
of the field.
.PP
The first entries ever created result from
-.BR init (8)
+.BR init (1)
processing
.BR inittab (5).
Before an entry is processed, though,
-.BR init (8)
+.BR init (1)
cleans up utmp by setting \fIut_type\fP to \fBDEAD_PROCESS\fP, clearing
\fIut_user\fP, \fIut_host\fP, and \fIut_time\fP with null bytes for each
record which \fIut_type\fP is not \fBDEAD_PROCESS\fP or \fBRUN_LVL\fP
and where no process with PID \fIut_pid\fP exists.
If no empty record
with the needed \fIut_id\fP can be found,
-.BR init (8)
+.BR init (1)
creates a new one.
It sets \fIut_id\fP from the inittab, \fIut_pid\fP and \fIut_time\fP to the
current values, and \fIut_type\fP to \fBINIT_PROCESS\fP.
\fIut_line\fP instead of the preferable \fIut_pid\fP.
.PP
When
-.BR init (8)
+.BR init (1)
finds that a process has exited, it locates its utmp
entry by \fIut_pid\fP, sets \fIut_type\fP to \fBDEAD_PROCESS\fP, and
clears \fIut_user\fP, \fIut_host\fP and \fIut_time\fP with null bytes.
changes it.
\fIwtmp\fP is maintained by
.BR login (1),
-.BR init (8),
+.BR init (1),
and some versions of
.BR getty (8)
(e.g.,
ut.ut_tv.tv_usec = tv.tv_usec;
.fi
.in
-.PP
-Note that the \fIutmp\fP struct from libc5 has changed in libc6.
-Because of this,
-binaries using the old libc5 struct will corrupt
-.IR /var/run/utmp " and/or " /var/log/wtmp .
-.SH BUGS
-This man page is based on the libc5 one, things may work differently now.
+.\" .PP
+.\" Note that the \fIutmp\fP struct from libc5 has changed in libc6.
+.\" Because of this,
+.\" binaries using the old libc5 struct will corrupt
+.\" .IR /var/run/utmp " and/or " /var/log/wtmp .
+.\" .SH BUGS
+.\" This man page is based on the libc5 one, things may work differently now.
.SH SEE ALSO
.BR ac (1),
.BR date (1),
.BR logout (3),
.BR logwtmp (3),
.BR updwtmp (3),
-.BR init (8)
+.BR init (1)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
conditions.
Note that these can be different from page to page!
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.UR http://www.squid-cache.org\:/~adrian\:/Reprint-Pulavarty-OLS2003.pdf
.UE
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
-.\"
-.TH ARMSCII-8 7 2014-02-16 "Linux" "Linux Programmer's Manual"
-.nh
+.TH ARMSCII-8 7 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
-armscii-8 \- Armenian character set encoded in octal, decimal, and
-hexadecimal
+armscii-8 \- Armenian character set encoded in octal, decimal,
+and hexadecimal
.SH DESCRIPTION
The Armenian Standard Code for Information Interchange,
8-bit coded character set.
are printable and unlisted in the
.BR ascii (7)
manual page.
-.\" The fourth column will only show the proper glyphs
-.\" in an environment configured for ArmSCII-8.
.TS
l l l c lp-1.
Oct Dec Hex Char Description
376 254 FE ՚ ARMENIAN APOSTROPHE
.TE
.SH SEE ALSO
-.BR ascii (7)
-
+.BR ascii (7),
+.BR charsets (7),
+.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
algorithms used.
Linux 2.2+ IPv4 ARP uses the IPv6 algorithms when applicable.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
'\" t
.\" Copyright (c) 1993 Michael Haardt (michael@moria.de)
-.\" Created Fri Apr 2 11:32:09 MET DST 1993
.\"
.\" %%%LICENSE_START(GPLv2+_DOC_FULL)
.\" This is free documentation; you can redistribute it and/or
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
+.\" Created 1993-04-02 by Michael Haardt (michael@moria.de)
.\" Modified 1993-07-24 by Rik Faith (faith@cs.unc.edu)
.\" Modified 1994-05-15 by Daniel Quinlan (quinlan@yggdrasil.com)
.\" Modified 1994-11-22 by Daniel Quinlan (quinlan@yggdrasil.com)
.\" Modified 1999-08-08 by Michael Haardt (michael@moria.de)
.\" Modified 2004-04-01 by aeb
.\"
-.TH ASCII 7 2014-02-26 "Linux" "Linux Programmer's Manual"
+.TH ASCII 7 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
-ascii \- ASCII character set encoded in octal, decimal, and hexadecimal
+ascii \- ASCII character set encoded in octal, decimal,
+and hexadecimal
.SH DESCRIPTION
ASCII is the American Standard Code for Information Interchange.
It is a 7-bit code.
Many 8-bit codes (e.g., ISO 8859-1) contain ASCII as their lower half.
-The international counterpart of ASCII is known as ISO 646.
+The international counterpart of ASCII is known as ISO 646-IRV.
.LP
The following table contains the 128 ASCII characters.
.LP
l l l l l l l l.
Oct Dec Hex Char Oct Dec Hex Char
_
-000 0 00 NUL \(aq\e0\(aq 100 64 40 @
+000 0 00 NUL \(aq\e0\(aq (null character) 100 64 40 @
001 1 01 SOH (start of heading) 101 65 41 A
002 2 02 STX (start of text) 102 66 42 B
003 3 03 ETX (end of text) 103 67 43 C
.ft P
\}
.SS Tables
-For convenience, let us give more compact tables in hex and decimal.
+For convenience, below are more compact tables in hex and decimal.
.sp
.nf
.if t \{\
.\" U.S. member body of ISO; private and nonprofit.
.\"
.SH SEE ALSO
-.ad l
+.BR charsets (7),
.BR iso_8859-1 (7),
.BR iso_8859-10 (7),
+.BR iso_8859-11 (7),
.BR iso_8859-13 (7),
.BR iso_8859-14 (7),
.BR iso_8859-15 (7),
.BR iso_8859-9 (7),
.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" I tried to be as much generic in the description as possible:
.\" - General boot sequence is applicable to almost any
.\" OS/Machine (DOS/PC, Linux/PC, Solaris/SPARC, CMS/S390)
-.\" - kernel and init(8) is applicable to almost any UNIX/Linux
+.\" - kernel and init(1) is applicable to almost any UNIX/Linux
.\" - boot scripts are applicable to SYSV-R4 based UNIX/Linux
.\"
.\" Modified 2004-11-03 patch from Martin Schulze <joey@infodrom.org>
services start).
The administrator may change the current
run-level via
-.BR init (8)
+.BR init (1)
and query the current run-level via
.BR runlevel (8).
.SH SEE ALSO
.BR inittab (5),
.BR bootparam (7),
-.BR init (8),
+.BR init (1),
.BR runlevel (8),
.BR shutdown (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" This man page written 950814 by aeb, based on Paul Gortmaker's HOWTO
.\" (dated v1.0.1, 15/08/95).
.\" Major update, aeb, 970114.
-.\" FIXME ? The use of quotes on this page is inconsistent with the
+.\" FIXME . The use of quotes on this page is inconsistent with the
.\" rest of man-pages.
.\"
-.TH BOOTPARAM 7 2013-08-01 "Linux" "Linux Programmer's Manual"
+.TH BOOTPARAM 7 2014-06-13 "Linux" "Linux Programmer's Manual"
.SH NAME
bootparam \- introduction to boot time parameters of the Linux kernel
.SH DESCRIPTION
is major 8, minor 3, so you could use 'root=0x803' as an
alternative.)
.TP
+.BR "'rootdelay='"
+This parameter sets the delay (in seconds) to pause before attempting
+to mount the root filesystem.
+.TP
+.BR "'rootflags=...'"
+This parameter sets the mount option string for the root filesystem
+(see also
+.BR fstab (5)).
+.TP
.BR "'rootfstype=...'"
The 'rootfstype' option tells the kernel to mount the root filesystem as
if it where of the type specified.
An up-to-date source of information is the kernel source file
.IR Documentation/kernel-parameters.txt .
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" other capabilities where the permitted or inheritable bit is set.
.\" 2011-09-07, mtk/Serge hallyn: Add CAP_SYSLOG
.\"
-.TH CAPABILITIES 7 2014-05-21 "Linux" "Linux Programmer's Manual"
+.TH CAPABILITIES 7 2014-09-21 "Linux" "Linux Programmer's Manual"
.SH NAME
capabilities \- overview of Linux capabilities
.SH DESCRIPTION
Enable and disable kernel auditing; change auditing filter rules;
retrieve auditing status and filtering rules.
.TP
+.BR CAP_AUDIT_READ " (since Linux 3.16)"
+.\" commit a29b694aa1739f9d76538e34ae25524f9c549d59
+.\" commit 3a101b8de0d39403b2c7e5c23fd0b005668acf48
+Allow reading the audit log via a multicast netlink socket.
+.TP
.BR CAP_AUDIT_WRITE " (since Linux 2.6.11)"
Write records to kernel auditing log.
.TP
the filesystem or any of the supplementary GIDs of the calling process.
.TP
.B CAP_IPC_LOCK
-.\" FIXME As at Linux 3.2, there are some strange uses of this capability
+.\" FIXME . As at Linux 3.2, there are some strange uses of this capability
.\" in other places; they probably should be replaced with something else.
Lock memory
.RB ( mlock (2),
.BR ioctl (2)
.B KDSIGACCEPT
operation.
-.\" FIXME CAP_KILL also has an effect for threads + setting child
+.\" FIXME . CAP_KILL also has an effect for threads + setting child
.\" termination signal to other than SIGCHLD: without this
.\" capability, the termination signal reverts to SIGCHLD
.\" if the child does an exec(). What is the rationale
.TP
.B CAP_SETGID
Make arbitrary manipulations of process GIDs and supplementary GID list;
-forge GID when passing socket credentials via UNIX domain sockets.
+forge GID when passing socket credentials via UNIX domain sockets;
+write a group ID mapping in a user namespace (see
+.BR user_namespaces (7)).
.TP
.BR CAP_SETFCAP " (since Linux 2.6.24)"
Set file capabilities.
.BR setreuid (2),
.BR setresuid (2),
.BR setfsuid (2));
-make forged UID when passing socket credentials via UNIX domain sockets.
+forge UID when passing socket credentials via UNIX domain sockets;
+write a user ID mapping in a user namespace (see
+.BR user_namespaces (7)).
.\" FIXME CAP_SETUID also an effect in exec(); document this.
.TP
.B CAP_SYS_ADMIN
flags that create new namespaces with
.BR clone (2)
and
-.BR unshare (2);
+.BR unshare (2)
+(but, since Linux 3.8,
+creating user namespaces does not require any capability);
.IP *
call
.BR perf_event_open (2);
event information;
.IP *
call
-.BR setns (2);
+.BR setns (2)
+(requires
+.B CAP_SYS_ADMIN
+in the
+.I target
+namespace);
.IP *
call
.BR fanotify_init (2);
.\" migrate_pages(2):
.\" do_migrate_pages(mm, &old, &new,
.\" capable(CAP_SYS_NICE) ? MPOL_MF_MOVE_ALL : MPOL_MF_MOVE);
+.\" Document this.
.IP *
apply
.BR move_pages (2)
capabilities are compiled into the kernel.
In kernels before Linux 2.6.33,
file capabilities were an optional feature configurable via the
-CONFIG_SECURITY_FILE_CAPABILITIES
+.B CONFIG_SECURITY_FILE_CAPABILITIES
option.
Since Linux 2.6.33, the configuration option has been removed
and file capabilities are always part of the kernel.
SECBIT_NOROOT_LOCKED);
.fi
.in
+.SS Interaction with user namespaces
+For a discussion of the interaction of capabilities and user namespaces, see
+.BR user_namespaces (7).
.SH CONFORMING TO
.PP
No standards govern capabilities, but the Linux capability implementation
.UE .
.SH NOTES
Since kernel 2.5.27, capabilities are an optional kernel component,
-and can be enabled/disabled via the CONFIG_SECURITY_CAPABILITIES
+and can be enabled/disabled via the
+.B CONFIG_SECURITY_CAPABILITIES
kernel configuration option.
The
.BR capsetp (3),
.BR libcap (3),
.BR credentials (7),
+.BR user_namespaces (7),
.BR pthreads (7),
.BR getcap (8),
.BR setcap (8)
.I include/linux/capability.h
in the Linux kernel source tree
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
+'\" t -*- coding: UTF-8 -*-
.\" Copyright (c) 1996 Eric S. Raymond <esr@thyrsus.com>
.\" and Copyright (c) Andries Brouwer <aeb@cwi.nl>
.\"
.\" This is combined from many sources, including notes by aeb and
.\" research by esr. Portions derive from a writeup by Roman Czyborra.
.\"
-.\" Last changed by David Starner <dstarner98@aasaa.ofe.org>.
+.\" Changes also by David Starner <dstarner98@aasaa.ofe.org>.
.\"
-.\" FIXME This page was written long ago, and various pieces are probably
-.\" no longer quite current. A reworking by someone knowledgeable
-.\" on charsets is needed. Among other things, the page needs to
-.\" give more prominence to Unicode. mtk, May 2014
-.\"
-.TH CHARSETS 7 2014-05-28 "Linux" "Linux Programmer's Manual"
+.TH CHARSETS 7 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
-charsets \- programmer's view of character sets and internationalization
+charsets - character set standards and internationalization
.SH DESCRIPTION
-Linux is an international operating system.
-Various of its utilities
-and device drivers (including the console driver) support multilingual
-character sets including Latin-alphabet letters with diacritical
-marks, accents, ligatures, and entire non-Latin alphabets including
-Greek, Cyrillic, Arabic, and Hebrew.
+This manual page gives an overview on different character set standards
+and how they were used on Linux before Unicode became ubiquitous.
+Some of this information is still helpful for people working with legacy
+systems and documents.
+.LP
+Standards discussed include such as
+ASCII, GB 2312, ISO 8859, JIS, KOI8-R, KS, and Unicode.
.LP
-This manual page presents a programmer's-eye view of different
-character-set standards and how they fit together on Linux.
-Standards
-discussed include ASCII, ISO 8859, KOI8-R, Unicode, ISO 2022 and
-ISO 4873.
-The primary emphasis is on character sets actually used as
-locale character sets, not the myriad others that can be found in data
+The primary emphasis is on character sets that were actually used by
+locale character sets, not the myriad others that could be found in data
from other systems.
.SS ASCII
ASCII (American Standard Code For Information Interchange) is the original
7-bit character set, originally designed for American English.
-It is currently described by the ECMA-6 standard.
+Also known as US-ASCII.
+It is currently described by the ISO 646:1991 IRV
+(International Reference Version) standard.
.LP
Various ASCII variants replacing the dollar sign with other currency
-symbols and replacing punctuation with non-English alphabetic characters
-to cover German, French, Spanish, and others in 7 bits exist.
-All are
-deprecated; glibc doesn't support locales whose character sets aren't
-true supersets of ASCII.
-(These sets are also known as ISO-646, a close
-relative of ASCII that permitted replacing these characters.)
+symbols and replacing punctuation with non-English alphabetic
+characters to cover German, French, Spanish, and others in 7 bits
+emerged.
+All are deprecated;
+glibc does not support locales whose character sets are not true
+supersets of ASCII.
.LP
-As Linux was written for hardware designed in the US, it natively
-supports ASCII.
+As Unicode, when using UTF-8, is ASCII-compatible, plain ASCII text
+still renders properly on modern UTF-8 using systems.
.SS ISO 8859
-ISO 8859 is a series of 15 8-bit character sets all of which have US
-ASCII in their low (7-bit) half, invisible control characters in
-positions 128 to 159, and 96 fixed-width graphics in positions 160-255.
+ISO 8859 is a series of 15 8-bit character sets, all of which have ASCII
+in their low (7-bit) half, invisible control characters in positions
+128 to 159, and 96 fixed-width graphics in positions 160-255.
.LP
-Of these, the most important is ISO 8859-1 (Latin-1).
-It is natively
-supported in the Linux console driver, fairly well supported in X11R6,
-and is the base character set of HTML.
+Of these, the most important is ISO 8859-1
+("Latin Alphabet No .1" / Latin-1).
+It was widely adopted and supported by different systems,
+and is gradually being replaced with Unicode.
+The ISO 8859-1 characters are also the first 256 characters of Unicode.
.LP
Console support for the other 8859 character sets is available under
Linux through user-mode utilities (such as
.BR setfont (8))
-.\" // some distributions still have the deprecated consolechars
that modify keyboard bindings and the EGA graphics
table and employ the "user mapping" font table in the console
driver.
Here are brief descriptions of each set:
.TP
8859-1 (Latin-1)
-Latin-1 covers most Western European languages such as Albanian, Catalan,
-Danish, Dutch, English, Faroese, Finnish, French, German, Galician,
-Irish, Icelandic, Italian, Norwegian, Portuguese, Spanish, and
-Swedish.
-The lack of the ligatures Dutch ij, French oe and old-style
-,,German`` quotation marks is considered tolerable.
+Latin-1 covers many West European languages such as Albanian, Basque,
+Danish, English, Faroese, Galician, Icelandic, Irish, Italian,
+Norwegian, Portuguese, Spanish, and Swedish.
+The lack of the ligatures Dutch IJ/ij, French œ, and old-style „German“
+quotation marks was considered tolerable.
.TP
8859-2 (Latin-2)
-Latin-2 supports most Latin-written Slavic and Central European
-languages: Croatian, Czech, German, Hungarian, Polish, Romanian,
+Latin-2 supports many Latin-written Central and East European
+languages such as Bosnian, Croatian, Czech, German, Hungarian, Polish,
Slovak, and Slovene.
+Replacing Romanian ș/ț with ş/ţ was considered tolerable.
.TP
8859-3 (Latin-3)
-Latin-3 is popular with authors of Esperanto, Galician, and Maltese.
-(Turkish is now written with 8859-9 instead.)
+Latin-3 was designed to cover of Esperanto, Maltese, and Turkish, but
+8859-9 later superseded it for Turkish.
.TP
8859-4 (Latin-4)
-Latin-4 introduced letters for Estonian, Latvian, and Lithuanian.
-It is essentially obsolete; see 8859-10 (Latin-6) and 8859-13 (Latin-7).
+Latin-4 introduced letters for North European languages such as
+Estonian, Latvian, and Lithuanian, but was superseded by 8859-10 and
+8859-13.
.TP
8859-5
Cyrillic letters supporting Bulgarian, Byelorussian, Macedonian,
-Russian, Serbian, and Ukrainian.
-Ukrainians read the letter "ghe"
-with downstroke as "heh" and would need a ghe with upstroke to write a
-correct ghe.
-See the discussion of KOI8-R below.
+Russian, Serbian, and (almost completely) Ukrainian.
+It was never widely used, see the discussion of KOI8-R/KOI8-U below.
.TP
8859-6
-Supports Arabic.
+Was created for Arabic.
The 8859-6 glyph table is a fixed font of separate
letter forms, but a proper display engine should combine these
using the proper initial, medial, and final forms.
.TP
8859-7
-Supports Modern Greek.
+Was created for Modern Greek in 1987, updated in 2003.
.TP
8859-8
-Supports modern Hebrew without niqud (punctuation signs).
-Niqud and full-fledged Biblical Hebrew are outside the scope of this
-character set; under Linux, UTF-8 is the preferred encoding for
-these.
+Supports Modern Hebrew without niqud (punctuation signs).
+Niqud and full-fledged Biblical Hebrew were outside the scope of this
+character set.
.TP
8859-9 (Latin-5)
This is a variant of Latin-1 that replaces Icelandic letters with
Turkish ones.
.TP
8859-10 (Latin-6)
-Latin 6 adds the last Inuit (Greenlandic) and Sami (Lappish) letters
-that were missing in Latin 4 to cover the entire Nordic area.
-RFC 1345 listed a preliminary and different "latin6".
-Skolt Sami still
-needs a few more accents than these.
+Latin-6 added the Inuit (Greenlandic) and Sami (Lappish) letters that were
+missing in Latin-4 to cover the entire Nordic area.
.TP
8859-11
-This exists only as a rejected draft standard.
-The draft standard
-was identical to TIS-620, which is used under Linux for Thai.
+Supports the Thai alphabet and is nearly identical to the TIS-620
+standard.
.TP
8859-12
This set does not exist.
-While Vietnamese has been suggested for this
-space, it does not fit within the 96 (noncombining) characters ISO
-8859 offers.
-UTF-8 is the preferred character set for Vietnamese use
-under Linux.
.TP
8859-13 (Latin-7)
Supports the Baltic Rim languages; in particular, it includes Latvian
characters not found in Latin-4.
.TP
8859-14 (Latin-8)
-This is the Celtic character set, covering Gaelic and Welsh.
-This charset also contains the dotted characters needed for Old Irish.
+This is the Celtic character set, covering Old Irish, Manx, Gaelic,
+Welsh, Cornish, and Breton.
.TP
8859-15 (Latin-9)
-This adds the Euro sign and French and Finnish letters that were missing in
-Latin-1.
+Latin-9 is similar to the widely used Latin-1 but replaces some less
+common symbols with the Euro sign and French and Finnish letters that
+were missing in Latin-1.
.TP
8859-16 (Latin-10)
-This set covers many of the languages covered by 8859-2, and supports
-Romanian more completely than that set does.
-.SS KOI8-R
-KOI8-R is a non-ISO character set popular in Russia.
-The lower half
-is US ASCII; the upper is a Cyrillic character set somewhat better
-designed than ISO 8859-5.
-KOI8-U is a common character set, based off
-KOI8-R, that has better support for Ukrainian.
-Neither of these sets
-are ISO-2022 compatible, unlike the ISO-8859 series.
+This set covers many Southeast European languages, and most
+importantly supports Romanian more completely than Latin-2.
+.SS KOI8-R / KOI8-U
+KOI8-R is a non-ISO character set popular in Russia before Unicode.
+The lower half is ASCII;
+the upper is a Cyrillic character set somewhat better designed than
+ISO 8859-5.
+KOI8-U, based on KOI8-R, has better support for Ukrainian.
+Neither of these sets are ISO-2022 compatible,
+unlike the ISO-8859 series.
.LP
Console support for KOI8-R is available under Linux through user-mode
utilities that modify keyboard bindings and the EGA graphics table,
and employ the "user mapping" font table in the console driver.
+.SS GB 2312
+GB 2312 is a mainland Chinese national standard character set used
+to express simplified Chinese.
+Just like JIS X 0208, characters are
+mapped into a 94x94 two-byte matrix used to construct EUC-CN.
+EUC-CN
+is the most important encoding for Linux and includes ASCII and
+GB 2312.
+Note that EUC-CN is often called as GB, GB 2312, or CN-GB.
+.SS Big5
+Big5 was a popular character set in Taiwan to express traditional
+Chinese.
+(Big5 is both a character set and an encoding.)
+It is a superset of ASCII.
+Non-ASCII characters are expressed in two bytes.
+Bytes 0xa1-0xfe are used as leading bytes for two-byte characters.
+Big5 and its extension were widely used in Taiwan and Hong Kong.
+It is not ISO 2022 compliant.
.\" Thanks to Tomohiro KUBOTA for the following sections about
.\" national standards.
.SS JIS X 0208
as a component to construct encodings such as EUC-JP, Shift_JIS,
and ISO-2022-JP.
EUC-JP is the most important encoding for Linux
-and includes US ASCII and JIS X 0208.
+and includes ASCII and JIS X 0208.
In EUC-JP, JIS X 0208
characters are expressed in two bytes, each of which is the
JIS X 0208 code plus 0x80.
KS X 1001 is used like JIS X 0208, as a component
to construct encodings such as EUC-KR, Johab, and ISO-2022-KR.
EUC-KR is the most important encoding for Linux and includes
-US ASCII and KS X 1001.
+ASCII and KS X 1001.
KS C 5601 is an older name for KS X 1001.
-.SS GB 2312
-GB 2312 is a mainland Chinese national standard character set used
-to express simplified Chinese.
-Just like JIS X 0208, characters are
-mapped into a 94x94 two-byte matrix used to construct EUC-CN.
-EUC-CN
-is the most important encoding for Linux and includes US ASCII and
-GB 2312.
-Note that EUC-CN is often called as GB, GB 2312, or CN-GB.
-.SS Big5
-Big5 is a popular character set in Taiwan to express traditional
-Chinese.
-(Big5 is both a character set and an encoding.)
-It is a superset of US ASCII.
-Non-ASCII characters are expressed in two bytes.
-Bytes 0xa1-0xfe are used as leading bytes for two-byte characters.
-Big5 and its extension is widely used in Taiwan and Hong Kong.
-It is not ISO 2022-compliant.
-.SS TIS 620
-TIS 620 is a Thai national standard character set and a superset
-of US ASCII.
-Like ISO 8859 series, Thai characters are mapped into
-0xa1-0xfe.
-TIS 620 is the only commonly used character set under
-Linux besides UTF-8 to have combining characters.
-.SS UNICODE
-Unicode (ISO 10646) is a standard which aims to unambiguously represent every
-character in every human language.
-Unicode's structure permits 20.1 bits to encode every character.
-Since most computers don't include 20.1-bit
-integers, Unicode is usually encoded as 32-bit integers internally and
-either a series of 16-bit integers (UTF-16) (needing two 16-bit integers
-only when encoding certain rare characters) or a series of 8-bit bytes
-(UTF-8).
-Information on Unicode is available at
-.UR http://www.unicode.org
-.UE .
-.LP
-Linux represents Unicode using the 8-bit Unicode Transformation Format
-(UTF-8).
-UTF-8 is a variable length encoding of Unicode.
-It uses 1
-byte to code 7 bits, 2 bytes for 11 bits, 3 bytes for 16 bits, 4 bytes
-for 21 bits, 5 bytes for 26 bits, 6 bytes for 31 bits.
-.LP
-Let 0,1,x stand for a zero, one, or arbitrary bit.
-A byte 0xxxxxxx
-stands for the Unicode 00000000 0xxxxxxx which codes the same symbol
-as the ASCII 0xxxxxxx.
-Thus, ASCII goes unchanged into UTF-8, and
-people using only ASCII do not notice any change: not in code, and not
-in file size.
-.LP
-A byte 110xxxxx is the start of a 2-byte code, and 110xxxxx 10yyyyyy
-is assembled into 00000xxx xxyyyyyy.
-A byte 1110xxxx is the start
-of a 3-byte code, and 1110xxxx 10yyyyyy 10zzzzzz is assembled
-into xxxxyyyy yyzzzzzz.
-(When UTF-8 is used to code the 31-bit ISO 10646
-then this progression continues up to 6-byte codes.)
-.LP
-For most people who use ISO-8859 character sets, this means that the
-characters outside of ASCII are now coded with two bytes.
-This tends
-to expand ordinary text files by only one or two percent.
-For Russian
-or Greek users, this expands ordinary text files by 100%, since text in
-those languages is mostly outside of ASCII.
-For Japanese users this means
-that the 16-bit codes now in common use will take three bytes.
-While there
-are algorithmic conversions from some character sets (especially ISO-8859-1) to
-Unicode, general conversion requires carrying around conversion tables,
-which can be quite large for 16-bit codes.
-.LP
-Note that UTF-8 is self-synchronizing: 10xxxxxx is a tail, any other
-byte is the head of a code.
-Note that the only way ASCII bytes occur
-in a UTF-8 stream, is as themselves.
-In particular, there are no
-embedded NULs (\(aq\\0\(aq) or \(aq/\(aqs that form part of some larger code.
-.LP
-Since ASCII, and, in particular, NUL and \(aq/\(aq, are unchanged, the
-kernel does not notice that UTF-8 is being used.
-It does not care at
-all what the bytes it is handling stand for.
-.LP
-Rendering of Unicode data streams is typically handled through
-"subfont" tables which map a subset of Unicode to glyphs.
-Internally
-the kernel uses Unicode to describe the subfont loaded in video RAM.
-This means that in UTF-8 mode one can use a character set with 512
-different symbols.
-This is not enough for Japanese, Chinese and
-Korean, but it is enough for most other purposes.
-.LP
-At the current time, the console driver does not handle combining
-characters.
-So Thai, Sioux and any other script needing combining
-characters can't be handled on the console.
.SS ISO 2022 and ISO 4873
The ISO 2022 and 4873 standards describe a font-control model
based on VT100 practice.
This model is (partially) supported
by the Linux kernel and by
.BR xterm (1).
-It is popular in Japan and Korea.
+Several ISO 2022-based character encodings have been defined,
+especially for Japanese.
.LP
There are 4 graphic character sets, called G0, G1, G2, and G3,
and one of them is the current character set for codes with
In particular, \fB^N\fP and \fB^O\fP are not used anymore, ESC ( xx
can be used only with xx=B, and ESC ) xx, ESC * xx, ESC + xx
are equivalent to ESC \- xx, ESC . xx, ESC / xx, respectively.
+.SS TIS-620
+TIS-620 is a Thai national standard character set and a superset
+of ASCII.
+In the same fashion as the ISO 8859 series, Thai characters are mapped into
+0xa1-0xfe.
+.SS Unicode
+Unicode (ISO 10646) is a standard which aims to unambiguously represent
+every character in every human language.
+Unicode's structure permits 20.1 bits to encode every character.
+Since most computers don't include 20.1-bit integers, Unicode is
+usually encoded as 32-bit integers internally and either a series of
+16-bit integers (UTF-16) (needing two 16-bit integers only when
+encoding certain rare characters) or a series of 8-bit bytes (UTF-8).
+.LP
+Linux represents Unicode using the 8-bit Unicode Transformation Format
+(UTF-8).
+UTF-8 is a variable length encoding of Unicode.
+It uses 1
+byte to code 7 bits, 2 bytes for 11 bits, 3 bytes for 16 bits, 4 bytes
+for 21 bits, 5 bytes for 26 bits, 6 bytes for 31 bits.
+.LP
+Let 0,1,x stand for a zero, one, or arbitrary bit.
+A byte 0xxxxxxx
+stands for the Unicode 00000000 0xxxxxxx which codes the same symbol
+as the ASCII 0xxxxxxx.
+Thus, ASCII goes unchanged into UTF-8, and
+people using only ASCII do not notice any change: not in code, and not
+in file size.
+.LP
+A byte 110xxxxx is the start of a 2-byte code, and 110xxxxx 10yyyyyy
+is assembled into 00000xxx xxyyyyyy.
+A byte 1110xxxx is the start
+of a 3-byte code, and 1110xxxx 10yyyyyy 10zzzzzz is assembled
+into xxxxyyyy yyzzzzzz.
+(When UTF-8 is used to code the 31-bit ISO 10646
+then this progression continues up to 6-byte codes.)
+.LP
+For most texts in ISO-8859 character sets, this means that the
+characters outside of ASCII are now coded with two bytes.
+This tends
+to expand ordinary text files by only one or two percent.
+For Russian
+or Greek texts, this expands ordinary text files by 100%, since text in
+those languages is mostly outside of ASCII.
+For Japanese users this means
+that the 16-bit codes now in common use will take three bytes.
+While there are algorithmic conversions from some character sets
+(especially ISO 8859-1) to Unicode, general conversion requires
+carrying around conversion tables, which can be quite large for 16-bit
+codes.
+.LP
+Note that UTF-8 is self-synchronizing: 10xxxxxx is a tail, any other
+byte is the head of a code.
+Note that the only way ASCII bytes occur
+in a UTF-8 stream, is as themselves.
+In particular, there are no
+embedded NULs (\(aq\\0\(aq) or \(aq/\(aqs that form part of some larger code.
+.LP
+Since ASCII, and, in particular, NUL and \(aq/\(aq, are unchanged, the
+kernel does not notice that UTF-8 is being used.
+It does not care at
+all what the bytes it is handling stand for.
+.LP
+Rendering of Unicode data streams is typically handled through
+"subfont" tables which map a subset of Unicode to glyphs.
+Internally
+the kernel uses Unicode to describe the subfont loaded in video RAM.
+This means that in the Linux console in UTF-8 mode, one can use a character
+set with 512 different symbols.
+This is not enough for Japanese, Chinese, and
+Korean, but it is enough for most other purposes.
.SH SEE ALSO
+.BR iconv (1),
.BR console (4),
-.BR console_codes (4),
-.BR console_ioctl (4),
.BR ascii (7),
.BR iso_8859-1 (7),
.BR unicode (7),
.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ctan (3),
.BR ctanh (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
-.TH CP1251 7 2014-02-16 "Linux" "Linux Programmer's Manual"
+.TH CP\ 1251 7 2014-02-16 "Linux" "Linux Programmer's Manual"
.SH NAME
cp1251 \- CP\ 1251 character set encoded in octal, decimal,
and hexadecimal
.SH DESCRIPTION
The Windows Code Pages include several 8-bit extensions to the ASCII
character set (also known as ISO 646-IRV).
-CP\ 1251 encodes the characters used in Cyrillic scripts.
-.\" (In my system with glibc-2.8-20080929
-.\" I found only bg_BG and be_BY locales using this encoding).
+CP\ 1251 encodes the
+characters used in Cyrillic scripts.
+.SS CP\ 1251 characters
The following table displays the characters in CP\ 1251, which
are printable and unlisted in the
.BR ascii (7)
manual page.
-.\" The fourth column will only show the proper glyphs
-.\" in an environment configured for CP\ 1251.
.TS
-l2 l2 l2 c2 lp-1.
+l l l c lp-1.
Oct Dec Hex Char Description
_
200 128 80 Ђ CYRILLIC CAPITAL LETTER DJE
257 175 AF Ї CYRILLIC CAPITAL LETTER YI
260 176 B0 ° DEGREE SIGN
261 177 B1 ± PLUS-MINUS SIGN
-262 178 B2 І CYRILLIC CAPITAL LETTER BYELORUSSIAN-UKRAINIAN I
+262 178 B2 І T{
+CYRILLIC CAPITAL LETTER
+.br
+BYELORUSSIAN-UKRAINIAN I
+T}
263 179 B3 і CYRILLIC SMALL LETTER BYELORUSSIAN-UKRAINIAN I
264 180 B4 ґ CYRILLIC SMALL LETTER GHE WITH UPTURN
265 181 B5 µ MICRO SIGN
304 196 C4 Д CYRILLIC CAPITAL LETTER DE
305 197 C5 Е CYRILLIC CAPITAL LETTER IE
306 198 C6 Ж CYRILLIC CAPITAL LETTER ZHE
-307 199 C7 v CYRILLIC CAPITAL LETTER ZE
+307 199 C7 З CYRILLIC CAPITAL LETTER ZE
310 200 C8 И CYRILLIC CAPITAL LETTER I
311 201 C9 Й CYRILLIC CAPITAL LETTER SHORT I
312 202 CA К CYRILLIC CAPITAL LETTER KA
.SH NOTES
CP\ 1251 is also known as Windows Cyrillic.
.SH SEE ALSO
-.BR ascii (7)
+.BR ascii (7),
+.BR charsets (7),
+.BR iso_8859-5 (7),
+.BR koi8-r (7),
+.BR koi8-u (7),
+.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
--- /dev/null
+'\" t -*- coding: UTF-8 -*-
+.\" Copyright 2014 (C) Marko Myllynen <myllynen@redhat.com>
+.\"
+.\" %%%LICENSE_START(GPLv2+_DOC_FULL)
+.\" This is free documentation; you can redistribute it and/or
+.\" modify it under the terms of the GNU General Public License as
+.\" published by the Free Software Foundation; either version 2 of
+.\" the License, or (at your option) any later version.
+.\"
+.\" The GNU General Public License's references to "object code"
+.\" and "executables" are to be interpreted as the output of any
+.\" document formatting or typesetting system, including
+.\" intermediate and printed output.
+.\"
+.\" This manual is distributed in the hope that it will be useful,
+.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
+.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+.\" GNU General Public License for more details.
+.\"
+.\" You should have received a copy of the GNU General Public
+.\" License along with this manual; if not, see
+.\" <http://www.gnu.org/licenses/>.
+.\" %%%LICENSE_END
+.\"
+.TH CP\ 1252 7 2014-02-16 "Linux" "Linux Programmer's Manual"
+.SH NAME
+cp1252 \- CP\ 1252 character set encoded in octal, decimal,
+and hexadecimal
+.SH DESCRIPTION
+The Windows Code Pages include several 8-bit extensions to the ASCII
+character set (also known as ISO 646-IRV).
+CP\ 1252 encodes the
+characters used in many West European languages.
+.SS CP\ 1252 characters
+The following table displays the characters in CP\ 1252, which
+are printable and unlisted in the
+.BR ascii (7)
+manual page.
+.TS
+l l l c lp-1.
+Oct Dec Hex Char Description
+_
+200 128 80 € EURO SIGN
+202 130 82 ‚ SINGLE LOW-9 QUOTATION MARK
+203 131 83 ƒ LATIN SMALL LETTER F WITH HOOK
+204 132 84 „ DOUBLE LOW-9 QUOTATION MARK
+205 133 85 … HORIZONTAL ELLIPSIS
+206 134 86 † DAGGER
+207 135 87 ‡ DOUBLE DAGGER
+210 136 88 ˆ MODIFIER LETTER CIRCUMFLEX ACCENT
+211 137 89 ‰ PER MILLE SIGN
+212 138 8A Š LATIN CAPITAL LETTER S WITH CARON
+213 139 8B ‹ SINGLE LEFT-POINTING ANGLE QUOTATION MARK
+214 140 8C ΠLATIN CAPITAL LIGATURE OE
+216 142 8E Ž LATIN CAPITAL LETTER Z WITH CARON
+221 145 91 ‘ LEFT SINGLE QUOTATION MARK
+222 146 92 ’ RIGHT SINGLE QUOTATION MARK
+223 147 93 “ LEFT DOUBLE QUOTATION MARK
+224 148 94 ” RIGHT DOUBLE QUOTATION MARK
+225 149 95 • BULLET
+226 150 96 – EN DASH
+227 151 97 — EM DASH
+230 152 98 ˜ SMALL TILDE
+231 153 99 ™ TRADE MARK SIGN
+232 154 9A š LATIN SMALL LETTER S WITH CARON
+233 155 9B › SINGLE RIGHT-POINTING ANGLE QUOTATION MARK
+234 156 9C œ LATIN SMALL LIGATURE OE
+236 158 9E ž LATIN SMALL LETTER Z WITH CARON
+237 159 9F Ÿ LATIN CAPITAL LETTER Y WITH DIAERESIS
+240 160 A0 NO-BREAK SPACE
+241 161 A1 ¡ INVERTED EXCLAMATION MARK
+242 162 A2 ¢ CENT SIGN
+243 163 A3 £ POUND SIGN
+244 164 A4 ¤ CURRENCY SIGN
+245 165 A5 ¥ YEN SIGN
+246 166 A6 ¦ BROKEN BAR
+247 167 A7 § SECTION SIGN
+250 168 A8 ¨ DIAERESIS
+251 169 A9 © COPYRIGHT SIGN
+252 170 AA ª FEMININE ORDINAL INDICATOR
+253 171 AB « LEFT-POINTING DOUBLE ANGLE QUOTATION MARK
+254 172 AC ¬ NOT SIGN
+255 173 AD SOFT HYPHEN
+256 174 AE ® REGISTERED SIGN
+257 175 AF ¯ MACRON
+260 176 B0 ° DEGREE SIGN
+261 177 B1 ± PLUS-MINUS SIGN
+262 178 B2 ² SUPERSCRIPT TWO
+263 179 B3 ³ SUPERSCRIPT THREE
+264 180 B4 ´ ACUTE ACCENT
+265 181 B5 µ MICRO SIGN
+266 182 B6 ¶ PILCROW SIGN
+267 183 B7 · MIDDLE DOT
+270 184 B8 ¸ CEDILLA
+271 185 B9 ¹ SUPERSCRIPT ONE
+272 186 BA º MASCULINE ORDINAL INDICATOR
+273 187 BB » RIGHT-POINTING DOUBLE ANGLE QUOTATION MARK
+274 188 BC ¼ VULGAR FRACTION ONE QUARTER
+275 189 BD ½ VULGAR FRACTION ONE HALF
+276 190 BE ¾ VULGAR FRACTION THREE QUARTERS
+277 191 BF ¿ INVERTED QUESTION MARK
+300 192 C0 À LATIN CAPITAL LETTER A WITH GRAVE
+301 193 C1 Á LATIN CAPITAL LETTER A WITH ACUTE
+302 194 C2 Â LATIN CAPITAL LETTER A WITH CIRCUMFLEX
+303 195 C3 Ã LATIN CAPITAL LETTER A WITH TILDE
+304 196 C4 Ä LATIN CAPITAL LETTER A WITH DIAERESIS
+305 197 C5 Å LATIN CAPITAL LETTER A WITH RING ABOVE
+306 198 C6 Æ LATIN CAPITAL LETTER AE
+307 199 C7 Ç LATIN CAPITAL LETTER C WITH CEDILLA
+310 200 C8 È LATIN CAPITAL LETTER E WITH GRAVE
+311 201 C9 É LATIN CAPITAL LETTER E WITH ACUTE
+312 202 CA Ê LATIN CAPITAL LETTER E WITH CIRCUMFLEX
+313 203 CB Ë LATIN CAPITAL LETTER E WITH DIAERESIS
+314 204 CC Ì LATIN CAPITAL LETTER I WITH GRAVE
+315 205 CD Í LATIN CAPITAL LETTER I WITH ACUTE
+316 206 CE Î LATIN CAPITAL LETTER I WITH CIRCUMFLEX
+317 207 CF Ï LATIN CAPITAL LETTER I WITH DIAERESIS
+320 208 D0 Ð LATIN CAPITAL LETTER ETH
+321 209 D1 Ñ LATIN CAPITAL LETTER N WITH TILDE
+322 210 D2 Ò LATIN CAPITAL LETTER O WITH GRAVE
+323 211 D3 Ó LATIN CAPITAL LETTER O WITH ACUTE
+324 212 D4 Ô LATIN CAPITAL LETTER O WITH CIRCUMFLEX
+325 213 D5 Õ LATIN CAPITAL LETTER O WITH TILDE
+326 214 D6 Ö LATIN CAPITAL LETTER O WITH DIAERESIS
+327 215 D7 × MULTIPLICATION SIGN
+330 216 D8 Ø LATIN CAPITAL LETTER O WITH STROKE
+331 217 D9 Ù LATIN CAPITAL LETTER U WITH GRAVE
+332 218 DA Ú LATIN CAPITAL LETTER U WITH ACUTE
+333 219 DB Û LATIN CAPITAL LETTER U WITH CIRCUMFLEX
+334 220 DC Ü LATIN CAPITAL LETTER U WITH DIAERESIS
+335 221 DD Ý LATIN CAPITAL LETTER Y WITH ACUTE
+336 222 DE Þ LATIN CAPITAL LETTER THORN
+337 223 DF ß LATIN SMALL LETTER SHARP S
+340 224 E0 à LATIN SMALL LETTER A WITH GRAVE
+341 225 E1 á LATIN SMALL LETTER A WITH ACUTE
+342 226 E2 â LATIN SMALL LETTER A WITH CIRCUMFLEX
+343 227 E3 ã LATIN SMALL LETTER A WITH TILDE
+344 228 E4 ä LATIN SMALL LETTER A WITH DIAERESIS
+345 229 E5 å LATIN SMALL LETTER A WITH RING ABOVE
+346 230 E6 æ LATIN SMALL LETTER AE
+347 231 E7 ç LATIN SMALL LETTER C WITH CEDILLA
+350 232 E8 è LATIN SMALL LETTER E WITH GRAVE
+351 233 E9 é LATIN SMALL LETTER E WITH ACUTE
+352 234 EA ê LATIN SMALL LETTER E WITH CIRCUMFLEX
+353 235 EB ë LATIN SMALL LETTER E WITH DIAERESIS
+354 236 EC ì LATIN SMALL LETTER I WITH GRAVE
+355 237 ED í LATIN SMALL LETTER I WITH ACUTE
+356 238 EE î LATIN SMALL LETTER I WITH CIRCUMFLEX
+357 239 EF ï LATIN SMALL LETTER I WITH DIAERESIS
+360 240 F0 ð LATIN SMALL LETTER ETH
+361 241 F1 ñ LATIN SMALL LETTER N WITH TILDE
+362 242 F2 ò LATIN SMALL LETTER O WITH GRAVE
+363 243 F3 ó LATIN SMALL LETTER O WITH ACUTE
+364 244 F4 ô LATIN SMALL LETTER O WITH CIRCUMFLEX
+365 245 F5 õ LATIN SMALL LETTER O WITH TILDE
+366 246 F6 ö LATIN SMALL LETTER O WITH DIAERESIS
+367 247 F7 ÷ DIVISION SIGN
+370 248 F8 ø LATIN SMALL LETTER O WITH STROKE
+371 249 F9 ù LATIN SMALL LETTER U WITH GRAVE
+372 250 FA ú LATIN SMALL LETTER U WITH ACUTE
+373 251 FB û LATIN SMALL LETTER U WITH CIRCUMFLEX
+374 252 FC ü LATIN SMALL LETTER U WITH DIAERESIS
+375 253 FD ý LATIN SMALL LETTER Y WITH ACUTE
+376 254 FE þ LATIN SMALL LETTER THORN
+377 255 FF ÿ LATIN SMALL LETTER Y WITH DIAERESIS
+.TE
+.SH NOTES
+CP\ 1252 is also known as Windows-1252.
+.SH SEE ALSO
+.BR ascii (7),
+.BR charsets (7),
+.BR iso_8859-1 (7),
+.BR iso_8859-15 (7),
+.BR utf-8 (7)
+.SH COLOPHON
+This page is part of release 3.75 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.
it from the cpuset that previously contained it) by writing its
PID to that cpuset's
.I tasks
-file (with or without a trailing newline.)
+file (with or without a trailing newline).
.B Warning:
only one PID may be written to the
Flag (0 or 1).
If set (1), the cpuset has exclusive use of
its memory nodes (no sibling or cousin may overlap).
-Also if set (1), the cpuset is a \fBHardwall\fR cpuset (see below.)
+Also if set (1), the cpuset is a \fBHardwall\fR cpuset (see below).
By default this is off (0).
Newly created cpusets also initially default this to off (0).
.TP
.IR cpuset.mem_hardwall " (since Linux 2.6.26)"
Flag (0 or 1).
-If set (1), the cpuset is a \fBHardwall\fR cpuset (see below.)
+If set (1), the cpuset is a \fBHardwall\fR cpuset (see below).
Unlike \fBmem_exclusive\fR,
there is no constraint on whether cpusets
marked \fBmem_hardwall\fR may have overlapping
40000000,00000000,00000000 # just bit 94 set
00000001,00000000,00000000 # just bit 64 set
000000ff,00000000 # bits 32-39 set
-00000000,000E3862 # 1,5,6,11-13,17-19 set
+00000000,000e3862 # 1,5,6,11-13,17-19 set
.fi
.RE
.PP
.IR Documentation/cpusets.txt
in the Linux kernel source tree
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\" 2007-06-13 Creation
.\"
-.TH CREDENTIALS 7 2014-05-21 "Linux" "Linux Programmer's Manual"
+.TH CREDENTIALS 7 2014-09-21 "Linux" "Linux Programmer's Manual"
.SH NAME
credentials \- process identifiers
.SH DESCRIPTION
Aside from the purposes noted above,
a process's user IDs are also employed in a number of other contexts:
.IP * 3
-when determining the permissions for sending signals\(emsee
-.BR kill (2);
+when determining the permissions for sending signals (see
+.BR kill (2));
.IP *
when determining the permissions for setting
process-scheduling parameters (nice value, real time
and
.BR ioprio_set (2);
.IP *
-when checking resource limits; see
-.BR getrlimit (2);
+when checking resource limits (see
+.BR getrlimit (2));
.IP *
when checking the limit on the number of inotify instances
-that the process may create; see
-.BR inotify (7).
+that the process may create (see
+.BR inotify (7)).
.SH CONFORMING TO
Process IDs, parent process IDs, process group IDs, and session IDs
are specified in POSIX.1-2001.
.BR tcgetpgrp (3),
.BR tcsetpgrp (3),
.BR capabilities (7),
+.BR namespaces (7),
.BR path_resolution (7),
+.BR pid_namespaces (7),
.BR signal (7),
+.BR user_namespaces (7),
.BR unix (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.B ATADDR_BCAST
is a link
local broadcast address.
-.\" FIXME this doesn't make sense [johnl]
+.\" FIXME . this doesn't make sense [johnl]
.SS Socket options
No protocol-specific socket options are supported.
.SS /proc interfaces
All ioctls described in
.BR socket (7)
apply to DDP.
-.\" FIXME Add a section about multicasting
+.\" FIXME . Add a section about multicasting
.SH ERRORS
-.\" FIXME document all errors. We should really fix the kernels to
+.\" FIXME . document all errors. We should really fix the kernels to
.\" give more uniform error returns (ENOMEM vs ENOBUFS, EPERM vs
.\" EACCES etc.)
.TP
.BR capabilities (7),
.BR socket (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Modified Wed Jan 24 06:37:24 2001 by Eric S. Raymond (esr@thyrsus.com)
.\" Modified Thu Dec 13 23:53:27 2001 by Martin Schulze <joey@infodrom.org>
.\"
-.TH ENVIRON 7 2014-01-18 "Linux" "Linux Programmer's Manual"
+.TH ENVIRON 7 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
environ \- user environment
.SH SYNOPSIS
(This variable must be declared in the user program,
but is declared in the header file
.I <unistd.h>
-in case the header files came from libc4 or libc5, and
-in case they came from glibc and
+if the
.B _GNU_SOURCE
-was defined.)
+feature test macro is defined.)
This array of strings is made available to the process by the
.BR exec (3)
call that started the process.
should consider renaming their option to
.BR GZIP_OPT .
.SH SEE ALSO
+.BR env (1),
.BR bash (1),
.BR csh (1),
.BR login (1),
+.BR printenv (1),
.BR sh (1),
.BR tcsh (1),
.BR execve (2),
.BR putenv (3),
.BR setenv (3),
.BR unsetenv (3),
-.BR locale (7)
+.BR locale (7),
+.BR ld.so (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\" Davide Libenzi <davidel@xmailserver.org>
.\"
-.TH EPOLL 7 2012-04-17 "Linux" "Linux Programmer's Manual"
+.TH EPOLL 7 2014-07-08 "Linux" "Linux Programmer's Manual"
.SH NAME
epoll \- I/O event notification facility
.SH SYNOPSIS
.BR epoll_ctl (2)
with
.BR EPOLL_CTL_MOD .
+.SS Interaction with autosleep
+If the system is in
+.B autosleep
+mode via
+.I /sys/power/autosleep
+and an event happens which wakes the device from sleep, the device
+driver will only keep the device awake until that event is queued.
+To keep the device awake until the event has been processed,
+it is necessary to use the
+.BR epoll (7)
+.B EPOLLWAKEUP
+flag.
+
+When the
+.B EPOLLWAKEUP
+flag is set in the
+.B events
+field for a
+.IR "struct epoll_event" ,
+the system will be kept awake from the moment the event is queued,
+through the
+.BR epoll_wait (2)
+call which returns the event until the subsequent
+.BR epoll_wait (2)
+call.
+If the event should keep the system awake beyond that time,
+then a separate
+.I wake_lock
+should be taken before the second
+.BR epoll_wait (2)
+call.
.SS /proc interfaces
The following interfaces can be used to limit the amount of
kernel memory consumed by epoll:
.BR epoll_ctl (2),
.BR epoll_wait (2)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
As of Linux 3.15,
the following bugs exist:
.IP * 3
-.\" FIXME: A patch was proposed.
+.\" FIXME . A patch was proposed.
When an event is generated,
no check is made to see whether the user ID of the
receiving process has authorization to read or write the file
.BR fanotify_mark (2),
.BR inotify (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.I /usr/include/features.h
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mkfifo (3),
.BR pipe (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.UR ftp://ftp.kernel.org\:/pub\:/linux\:/kernel\:/people\:/rusty/
.UE .
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR locale (7),
.BR regex (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
The Filesystem Hierarchy Standard
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Hostname appeared in
.\" 4.2BSD.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.IR /proc/sys/net/ipv4/ .
Most of these parameters are rate limitations for specific ICMP types.
Linux 2.2 uses a token bucket filter to limit ICMPs.
-.\" FIXME better description needed
+.\" FIXME . better description needed
The value is the timeout in jiffies until the token bucket filter is
cleared after a burst.
A jiffy is a system dependent unit, usually 10ms on i386 and
.PP
RFC\ 792 for a description of the ICMP protocol.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH INOTIFY 7 2014-05-23 "Linux" "Linux Programmer's Manual"
+.TH INOTIFY 7 2014-09-06 "Linux" "Linux Programmer's Manual"
.SH NAME
inotify \- monitoring filesystem events
.SH DESCRIPTION
the underlying object and its resources are
freed for reuse by the kernel;
all associated watches are automatically freed.
-
+.PP
With careful programming,
an application can use inotify to efficiently monitor and cache
the state of a set of filesystem objects.
.\" I submitted a patch to fix this. See the LKML thread
.\" "[patch] Fix type errors in inotify interfaces", 18 Nov 2008
.\" Glibc bug filed: http://sources.redhat.com/bugzilla/show_bug.cgi?id=7040
- uint32_t mask; /* Mask of events */
+ uint32_t mask; /* Mask describing event */
uint32_t cookie; /* Unique cookie associating related
events (for rename(2)) */
uint32_t len; /* Size of \fIname\fP field */
.BR read (2):
.RS 4
.TP
-.BR IN_ACCESS " (*)"
+.BR IN_ACCESS " (+)"
File was accessed (e.g.,
.BR read (2),
.BR execve (2)).
and user/group ID (e.g.,
.BR chown (2)).
.TP
-.BR IN_CLOSE_WRITE " (*)"
+.BR IN_CLOSE_WRITE " (+)"
File opened for writing was closed.
.TP
.BR IN_CLOSE_NOWRITE " (*)"
-File not opened for writing was closed.
+File or directory not opened for writing was closed.
.TP
-.BR IN_CREATE " (*)"
+.BR IN_CREATE " (+)"
File/directory created in watched directory (e.g.,
.BR open (2)
.BR O_CREAT ,
.BR bind (2)
on a UNIX domain socket).
.TP
-.BR IN_DELETE " (*)"
+.BR IN_DELETE " (+)"
File/directory deleted from watched directory.
.TP
.B IN_DELETE_SELF
.B IN_IGNORED
event will subsequently be generated for the watch descriptor.
.TP
-.BR IN_MODIFY " (*)"
+.BR IN_MODIFY " (+)"
File was modified (e.g.,
.BR write (2),
.BR truncate (2)).
.B IN_MOVE_SELF
Watched file/directory was itself moved.
.TP
-.BR IN_MOVED_FROM " (*)"
+.BR IN_MOVED_FROM " (+)"
Generated for the directory containing the old filename
when a file is renamed.
.TP
-.BR IN_MOVED_TO " (*)"
+.BR IN_MOVED_TO " (+)"
Generated for the directory containing the new filename
when a file is renamed.
.TP
.BR IN_OPEN " (*)"
-File was opened.
+File or directory was opened.
.RE
.PP
-When monitoring a directory,
-the events marked with an asterisk (*) above can occur for
-files in the directory, in which case the
+When monitoring a directory:
+.IP * 3
+the events marked above with an asterisk (*) can occur both
+for the directory itself and for objects inside the directory; and
+.IP *
+the events marked with a plus sign (+) occur only for objects
+inside the directory (not for the directory itself).
+.PP
+When events are generated for objects inside a watched directory, the
.I name
field in the returned
.I inotify_event
they have been unlinked from the watched directory.
.TP
.B IN_MASK_ADD
-Add (OR) events to watch mask for this pathname if
-it already exists (instead of replacing mask).
+If a watch instance already exists for the filesystem object corresponding to
+.IR pathname ,
+add (OR) the events in
+.I mask
+to the watch mask (instead of replacing the mask).
.TP
.B IN_ONESHOT
-Monitor
+Monitor the filesystem object corresponding to
.I pathname
for one event, then remove from
watch list.
Only watch
.I pathname
if it is a directory.
+Using this flag provides an application with a race-free way of
+ensuring that the monitored object is a directory.
.RE
.PP
The following bits may be set in the
and
.B IN_MOVED_TO
events.
+Furthermore, it is not guaranteed that the event pair is atomically
+inserted into the queue: there may be a brief interval where the
+.B IN_MOVED_FROM
+has appeared, but the
+.B IN_MOVED_TO
+has not.
Matching up the
.B IN_MOVED_FROM
and the accompanying
.B IN_MOVED_TO
event might be fetched only on the next
-.BR read (2).
+.BR read (2),
+which should be done with a (small) timeout to allow for the fact that
+insertion of the
+.BR IN_MOVED_FROM - IN_MOVED_TO
+event pair is not atomic,
+and also the possibility that there may not be any
+.B IN_MOVED_TO
+event.
.SH BUGS
-.\" FIXME kernel commit 611da04f7a31b2208e838be55a42c7a1310ae321
+.\" FIXME . kernel commit 611da04f7a31b2208e838be55a42c7a1310ae321
.\" implies that unmount events were buggy 2.6.11 to 2.6.36
.\"
In kernels before 2.6.16, the
instead checked if the most recent event could be coalesced with the
.I oldest
unread event.
+
+When a watch descriptor is removed by calling
+.BR inotify_rm_watch (2)
+(or because a watch file is deleted or the filesystem
+that contains it is unmounted),
+any pending unread events for that watch descriptor remain available to read.
+As watch descriptors are subsequently allocated with
+.BR inotify_add_watch (2),
+the kernel cycles through the range of possible watch descriptors (0 to
+.BR INT_MAX )
+incrementally.
+When allocating a free watch descriptor, no check is made to see whether that
+watch descriptor number has any pending unread events in the inotify queue.
+Thus, it can happen that a watch descriptor is reallocated even
+when pending unread events exist for a previous incarnation of
+that watch descriptor number, with the result that the application
+might then read those events and interpret them as belonging to
+the file associated with the newly recycled watch descriptor.
+In practice, the likelihood of hitting this bug may be extremely low,
+since it requires that an application cycle through
+.B INT_MAX
+watch descriptors,
+release a watch descriptor while leaving unread events for that
+watch descriptor in the queue,
+and then recycle that watch descriptor.
+For this reason, and because there have been no reports
+of the bug occurring in real-world applications,
+as of Linux 3.15,
+.\" FIXME . https://bugzilla.kernel.org/show_bug.cgi?id=77111
+no kernel changes have yet been made to eliminate this possible bug.
.SH EXAMPLE
The following program demonstrates the usage of the inotify API.
It marks the directories passed as a command-line arguments
.IR Documentation/filesystems/inotify.txt
in the Linux kernel source tree
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.SH SEE ALSO
.BR standards (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\" $Id: ip.7,v 1.19 2000/12/20 18:10:31 ak Exp $
.\"
-.\" FIXME: The following socket options are yet to be documented
+.\" FIXME The following socket options are yet to be documented
.\" IP_XFRM_POLICY (2.5.48)
.\" Needs CAP_NET_ADMIN
.\" IP_IPSEC_POLICY (2.5.47)
.B ip
contains a level 2 multicasting implementation conforming to RFC\ 1112.
It also contains an IP router including a packet filter.
-.\" FIXME has someone verified that 2.1 is really 1812 compliant?
+.\" FIXME . has someone verified that 2.1 is really 1812 compliant?
.PP
The programming interface is BSD-sockets compatible.
For more information on sockets, see
To bootstrap the path MTU discovery process on unconnected sockets, it
is possible to start with a big datagram size
(up to 64K-headers bytes long) and let it shrink by updates of the path MTU.
-.\" FIXME this is an ugly hack
+.\" FIXME . this is an ugly hack
To get an initial estimate of the
path MTU, connect a datagram socket to the destination address using
.fi
.in
.IP
-.\" FIXME elaborate on that.
+.\" FIXME . elaborate on that.
.I ipi_ifindex
is the unique index of the interface the packet was received on.
.I ipi_spec_dst
is called on a stream socket that was not previously bound;
.IP *
.BR connect (2)
-was called on a socket that was not not previously bound;
+was called on a socket that was not previously bound;
.IP *
.BR sendto (2)
-is called on a datagram socket that was not not previously bound.
+is called on a datagram socket that was not previously bound.
.RE
.IP
Allocation of ephemeral ports starts with the first number in
.IR ip_local_port_range
and ends with the second number.
If the range of ephemeral ports is exhausted,
-then the relevant system call returns an error (but see BUGS)
+then the relevant system call returns an error (but see BUGS).
.IP
Note that the port range in
.IR ip_local_port_range
See
.BR arp (7).
.\" FIXME Document the conf/*/* interfaces
+.\"
.\" FIXME Document the route/* interfaces
-.\" FIXME document them all
.SS Ioctls
All ioctls described in
.BR socket (7)
Other errors may be generated by the overlaying protocols; see
.BR tcp (7),
.BR raw (7),
-.BR udp (7)
+.BR udp (7),
and
.BR socket (7).
.SH NOTES
RFC\ 791 for the original IP specification.
RFC\ 1122 for the IPv4 host requirements.
RFC\ 1812 for the IPv4 router requirements.
-.\" FIXME autobind INADDR REUSEADDR
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" commit c4062dfc425e94290ac427a98d6b4721dd2bc91f
.\" Author: Erich E. Hoover <ehoover@mines.edu>
.\"
-.TH IPV6 7 2012-12-16 "Linux" "Linux Programmer's Manual"
+.TH IPV6 7 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
ipv6 \- Linux IPv6 protocol implementation
.SH SYNOPSIS
The default value for that file is 0 (false).
.\" FLOWLABEL_MGR, FLOWINFO_SEND
.SH ERRORS
-.\" FIXME document all errors.
.TP
.B ENODEV
The user tried to
structure is not a valid
interface index.
.SH VERSIONS
-The older
-.I libinet6
-libc5 based IPv6 API implementation for Linux is not described here
-and may vary in details.
-.PP
Linux 2.4 will break binary compatibility for the
.I sockaddr_in6
for 64-bit
Linux tries to be compliant to this.
RFC\ 2460: IPv6 specification.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\" Slightly rearranged, aeb, 950713
.\" Updated, dpo, 990531
-.TH ISO_8859-1 7 2014-02-16 "Linux" "Linux Programmer's Manual"
-.nh
+.TH ISO_8859-1 7 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
iso_8859-1 \- ISO 8859-1 character set encoded in octal, decimal,
and hexadecimal
.SH DESCRIPTION
The ISO 8859 standard includes several 8-bit extensions to the ASCII
character set (also known as ISO 646-IRV).
-Especially important is
-ISO 8859-1, the "Latin Alphabet No. 1", which has become widely
-implemented and may already be seen as the de-facto standard ASCII
-replacement.
-.P
-ISO 8859-1 supports the following languages: Afrikaans, Basque,
-Catalan, Danish, Dutch, English, Faeroese, Finnish, French, Galician,
-German, Icelandic, Irish, Italian, Norwegian, Portuguese, Scottish,
-Spanish, and Swedish.
-.P
-Note that the ISO 8859-1 characters are also the first 256 characters
-of ISO 10646 (Unicode).
+ISO 8859-1 encodes the
+characters used in many West European languages.
.SS ISO 8859 alphabets
The full set of ISO 8859 alphabets includes:
.TS
ISO 8859-16 Romanian (Latin-10)
.TE
.SS ISO 8859-1 characters
-The following table displays the characters in ISO 8859-1 (Latin-1),
-which are printable and unlisted in the
+The following table displays the characters in ISO 8859-1, which
+are printable and unlisted in the
.BR ascii (7)
manual page.
-.\" The fourth column will only show the proper glyphs
-.\" in an environment configured for ISO 8859-1.
.TS
-l2 l2 l2 c2 lp-1.
+l l l c lp-1.
Oct Dec Hex Char Description
_
240 160 A0 NO-BREAK SPACE
252 170 AA ª FEMININE ORDINAL INDICATOR
253 171 AB « LEFT-POINTING DOUBLE ANGLE QUOTATION MARK
254 172 AC ¬ NOT SIGN
-255 173 AD SOFT HYPHEN (shown as a hyphen at line breaks) [1]
+255 173 AD SOFT HYPHEN
256 174 AE ® REGISTERED SIGN
257 175 AF ¯ MACRON
260 176 B0 ° DEGREE SIGN
376 254 FE þ LATIN SMALL LETTER THORN
377 255 FF ÿ LATIN SMALL LETTER Y WITH DIAERESIS
.TE
-.IP [1] 4
-See
-.BR groff_char (7)
-(soft hyphen) and the standard ISO 8859-1 ("shy",
-paragraph 6.3.3)
-or the equivalent version from your national standardization body.
+.SH NOTES
+ISO 8859-1 is also known as Latin-1.
.SH SEE ALSO
.BR ascii (7),
-.BR iso_8859-15 (7)
+.BR charsets (7),
+.BR iso_8859-15 (7),
+.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
-.TH ISO_8859-10 7 2014-02-16 "Linux" "Linux Programmer's Manual"
+.TH ISO_8859-10 7 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
iso_8859-10 \- ISO 8859-10 character set encoded in octal, decimal,
and hexadecimal
character set (also known as ISO 646-IRV).
ISO 8859-10 encodes the
characters used in Nordic languages.
-.\" (Though in my system with glibc-2.8-20080929
-.\" I found only lg_UG using this charset, and certainly UG
-.\" is not a "Nordic" country!).
.SS ISO 8859 alphabets
The full set of ISO 8859 alphabets includes:
.TS
are printable and unlisted in the
.BR ascii (7)
manual page.
-.\" The fourth column will only show the proper glyphs
-.\" in an environment configured for ISO 8859-10.
.TS
l l l c lp-1.
Oct Dec Hex Char Description
254 172 AC Ž LATIN CAPITAL LETTER Z WITH CARON
255 173 AD SOFT HYPHEN
256 174 AE Ū LATIN CAPITAL LETTER U WITH MACRON
-257 175 AF Ŋ LATIN CAPITAL LETTER ENG (Sami)
+257 175 AF Ŋ LATIN CAPITAL LETTER ENG
260 176 B0 ° DEGREE SIGN
261 177 B1 ą LATIN SMALL LETTER A WITH OGONEK
262 178 B2 ē LATIN SMALL LETTER E WITH MACRON
274 188 BC ž LATIN SMALL LETTER Z WITH CARON
275 189 BD ― HORIZONTAL BAR
276 190 BE ū LATIN SMALL LETTER U WITH MACRON
-277 191 BF ŋ LATIN SMALL LETTER ENG (Sami)
+277 191 BF ŋ LATIN SMALL LETTER ENG
300 192 C0 Ā LATIN CAPITAL LETTER A WITH MACRON
301 193 C1 Á LATIN CAPITAL LETTER A WITH ACUTE
302 194 C2 Â LATIN CAPITAL LETTER A WITH CIRCUMFLEX
315 205 CD Í LATIN CAPITAL LETTER I WITH ACUTE
316 206 CE Î LATIN CAPITAL LETTER I WITH CIRCUMFLEX
317 207 CF Ï LATIN CAPITAL LETTER I WITH DIAERESIS
-320 208 D0 Ð LATIN CAPITAL LETTER ETH (Icelandic)
+320 208 D0 Ð LATIN CAPITAL LETTER ETH
321 209 D1 Ņ LATIN CAPITAL LETTER N WITH CEDILLA
322 210 D2 Ō LATIN CAPITAL LETTER O WITH MACRON
323 211 D3 Ó LATIN CAPITAL LETTER O WITH ACUTE
333 219 DB Û LATIN CAPITAL LETTER U WITH CIRCUMFLEX
334 220 DC Ü LATIN CAPITAL LETTER U WITH DIAERESIS
335 221 DD Ý LATIN CAPITAL LETTER Y WITH ACUTE
-336 222 DE Þ LATIN CAPITAL LETTER THORN (Icelandic)
-337 223 DF ß LATIN SMALL LETTER SHARP S (German)
+336 222 DE Þ LATIN CAPITAL LETTER THORN
+337 223 DF ß LATIN SMALL LETTER SHARP S
340 224 E0 ā LATIN SMALL LETTER A WITH MACRON
341 225 E1 á LATIN SMALL LETTER A WITH ACUTE
342 226 E2 â LATIN SMALL LETTER A WITH CIRCUMFLEX
355 237 ED í LATIN SMALL LETTER I WITH ACUTE
356 238 EE î LATIN SMALL LETTER I WITH CIRCUMFLEX
357 239 EF ï LATIN SMALL LETTER I WITH DIAERESIS
-360 240 F0 ð LATIN SMALL LETTER ETH (Icelandic)
+360 240 F0 ð LATIN SMALL LETTER ETH
361 241 F1 ņ LATIN SMALL LETTER N WITH CEDILLA
362 242 F2 ō LATIN SMALL LETTER O WITH MACRON
363 243 F3 ó LATIN SMALL LETTER O WITH ACUTE
373 251 FB û LATIN SMALL LETTER U WITH CIRCUMFLEX
374 252 FC ü LATIN SMALL LETTER U WITH DIAERESIS
375 253 FD ý LATIN SMALL LETTER Y WITH ACUTE
-376 254 FE þ LATIN SMALL LETTER THORN (Icelandic)
-377 255 FF ĸ LATIN SMALL LETTER KRA (Greenlandic)
+376 254 FE þ LATIN SMALL LETTER THORN
+377 255 FF ĸ LATIN SMALL LETTER KRA
.TE
.SH NOTES
ISO 8859-10 is also known as Latin-6.
.SH SEE ALSO
-.BR ascii (7)
+.BR ascii (7),
+.BR charsets (7),
+.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\"Thanomsub Noppaburana <donga.nb@gmail.com> made valuable suggestions.
.\"
-.TH ISO_8859-11 7 2014-02-16 "Linux" "Linux Programmer's Manual"
+.TH ISO_8859-11 7 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
iso_8859-11 \- ISO 8859-11 character set encoded in octal, decimal,
and hexadecimal
.SH DESCRIPTION
The ISO 8859 standard includes several 8-bit extensions to the ASCII
character set (also known as ISO 646-IRV).
-ISO 8859-11 encodes the characters used in the Thai language.
+ISO 8859-11 encodes the
+characters used in the Thai language.
.SS ISO 8859 alphabets
The full set of ISO 8859 alphabets includes:
.TS
are printable and unlisted in the
.BR ascii (7)
manual page.
-.\" The fourth column will only show the proper glyphs
-.\" in an environment configured for ISO 8859-11.
.TS
l l l c lp-1.
Oct Dec Hex Char Description
.TE
.SH NOTES
ISO 8859-11 is the same as TIS (Thai Industrial Standard) 620-2253,
-commonly known as TIS-620, except for the character in position a0:
-ISO 8859-11 defines this as "nonbreaking space",
-while TIS 620 leaves it undefined.
+commonly known as TIS-620, except for the character in position A0:
+ISO 8859-11 defines this as NO-BREAK SPACE,
+while TIS-620 leaves it undefined.
.SH SEE ALSO
-.BR ascii (7)
+.BR ascii (7),
+.BR charsets (7),
+.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
-.TH ISO_8859-13 7 2014-02-16 "Linux" "Linux Programmer's Manual"
+.TH ISO_8859-13 7 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
iso_8859-13 \- ISO 8859-13 character set encoded in octal, decimal,
and hexadecimal
.SH DESCRIPTION
The ISO 8859 standard includes several 8-bit extensions to the ASCII
character set (also known as ISO 646-IRV).
-ISO 8859-13 encodes the characters used in Baltic Rim languages.
-.\" In my system with glibc-2.8-20080929 is used for
-.\" Lithuanian, Latvian and the Maori language in New Zealand.
+ISO 8859-13 encodes the
+characters used in Baltic Rim languages.
.SS ISO 8859 alphabets
The full set of ISO 8859 alphabets includes:
.TS
are printable and unlisted in the
.BR ascii (7)
manual page.
-.\" The fourth column will only show the proper glyphs
-.\" in an environment configured for ISO 8859-13.
.TS
l l l c lp-1.
Oct Dec Hex Char Description
.SH NOTES
ISO 8859-13 is also known as Latin-7.
.SH SEE ALSO
-.BR ascii (7)
+.BR ascii (7),
+.BR charsets (7),
+.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
-.TH ISO_8859-14 7 2014-02-16 "Linux" "Linux Programmer's Manual"
+.TH ISO_8859-14 7 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
iso_8859-14 \- ISO 8859-14 character set encoded in octal, decimal,
and hexadecimal
.SH DESCRIPTION
The ISO 8859 standard includes several 8-bit extensions to the ASCII
character set (also known as ISO 646-IRV).
-ISO 8859-14 encodes the characters used in Celtic languages.
+ISO 8859-14 encodes the
+characters used in Celtic languages.
.SS ISO 8859 alphabets
The full set of ISO 8859 alphabets includes:
.TS
are printable and unlisted in the
.BR ascii (7)
manual page.
-.\" The fourth column will only show the proper glyphs
-.\" in an environment configured for ISO 8859-14.
.TS
l l l c lp-1.
Oct Dec Hex Char Description
.SH NOTES
ISO 8859-14 is also known as Latin-8.
.SH SEE ALSO
-.BR ascii (7)
+.BR ascii (7),
+.BR charsets (7),
+.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
-.TH ISO_8859-15 7 2014-02-16 "Linux" "Linux Programmer's Manual"
-.nh
+.TH ISO_8859-15 7 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
iso_8859-15 \- ISO 8859-15 character set encoded in octal, decimal,
and hexadecimal
.SH DESCRIPTION
The ISO 8859 standard includes several 8-bit extensions to the ASCII
character set (also known as ISO 646-IRV).
-Especially important is
-ISO 8859-1, the "Latin Alphabet No. 1", which has become widely
-implemented and may already be seen as the de-facto standard ASCII
-replacement.
-However, it lacks the EURO symbol and does not fully
-cover Finnish and French.
-ISO 8859-15 is a modification of ISO 8859-1
-that covers these needs.
-.P
-ISO 8859-15 supports the following languages: Albanian, Basque, Breton,
-Catalan, Danish, Dutch, English, Estonian, Faroese, Finnish, French,
-Frisian, Galician, German, Greenlandic, Icelandic, Irish Gaelic,
-Italian, Latin, Luxemburgish, Norwegian, Portuguese, Rhaeto-Romanic,
-Scottish Gaelic, Spanish, and Swedish.
+ISO 8859-15 encodes the
+characters used in many West European languages and adds the Euro sign.
.SS ISO 8859 alphabets
The full set of ISO 8859 alphabets includes:
.TS
ISO 8859-16 Romanian (Latin-10)
.TE
.SS ISO 8859-15 characters
-The following table displays the characters in ISO 8859-15 (Latin-9),
-which are printable and unlisted in the
+The following table displays the characters in ISO 8859-15, which
+are printable and unlisted in the
.BR ascii (7)
manual page.
-.\" The fourth column will only show the proper glyphs
-.\" in an environment configured for ISO 8859-15.
.TS
l l l c lp-1.
Oct Dec Hex Char Description
376 254 FE þ LATIN SMALL LETTER THORN
377 255 FF ÿ LATIN SMALL LETTER Y WITH DIAERESIS
.TE
+.SH NOTES
+ISO 8859-15 is also known as Latin-9 (or sometimes as Latin-0).
.SH SEE ALSO
.BR ascii (7),
-.BR iso_8859-1 (7)
+.BR charsets (7),
+.BR iso_8859-1 (7),
+.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
-.TH ISO_8859-16 7 2014-02-16 "Linux" "Linux Programmer's Manual"
-.nh
+.TH ISO_8859-16 7 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
iso_8859-16 \- ISO 8859-16 character set encoded in octal, decimal,
and hexadecimal
.SH DESCRIPTION
The ISO 8859 standard includes several 8-bit extensions to the ASCII
character set (also known as ISO 646-IRV).
-ISO 8859-16, the "Latin
-Alphabet No. 10" is used to encode Central and Eastern European Latin
-characters and is not implemented yet by any program vendors.
-.P
-ISO 8859-16 supports the following languages: Albanian, Bosnian,
-Croatian, English, Finnish, German, Hungarian, Irish, Polish,
-Romanian, Slovenian, and Serbian.
-.P
-Also note that the following Cyrillic-based languages have one-to-one
-transliterations to Latin 10: Macedonian and Serbian.
+ISO 8859-16 encodes the
+Latin characters used in Southeast European languages.
.SS ISO 8859 alphabets
The full set of ISO 8859 alphabets includes:
.TS
ISO 8859-16 Romanian (Latin-10)
.TE
.SS ISO 8859-16 characters
-The following table displays the characters in ISO 8859-16 (Latin-10),
-which are printable and unlisted in the
+The following table displays the characters in ISO 8859-16, which
+are printable and unlisted in the
.BR ascii (7)
manual page.
-.\" The fourth column will only show the proper glyphs
-.\" in an environment configured for ISO 8859-16.
.TS
l l l c lp-1.
Oct Dec Hex Char Description
376 254 FE ț LATIN SMALL LETTER T WITH COMMA BELOW
377 255 FF ÿ LATIN SMALL LETTER Y WITH DIAERESIS
.TE
+.SH NOTES
+ISO 8859-16 is also known as Latin-10.
.SH SEE ALSO
.BR ascii (7),
-.BR iso_8859-1 (7),
-.BR iso_8859-15 (7),
-.BR iso_8859-2 (7)
-
-.I ISO 8859-16 (Latin 10) Resources
-.UR http://bucovina.chem.tue.nl\:/fonturi\:/index-en.html
-.UE .
+.BR charsets (7),
+.BR iso_8859-3 (7),
+.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\" Slightly rearranged, aeb, 950713
.\" Updated, dpo, 990531
-.TH ISO_8859-2 7 2014-02-16 "Linux" "Linux Programmer's Manual"
-.nh
+.TH ISO_8859-2 7 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
iso_8859-2 \- ISO 8859-2 character set encoded in octal, decimal,
and hexadecimal
.SH DESCRIPTION
The ISO 8859 standard includes several 8-bit extensions to the ASCII
character set (also known as ISO 646-IRV).
-ISO 8859-2, the "Latin
-Alphabet No. 2" is used to encode Central and Eastern European Latin
-characters and is implemented by several program vendors.
-.P
-ISO 8859-2 supports the following languages: Albanian, Bosnian,
-Croatian, Czech, English, Finnish, German, Hungarian, Irish, Polish,
-Slovak, Slovenian, and Sorbian.
-.P
-Also note that the following Cyrillic-based languages have one-to-one
-transliterations to Latin 2: Macedonian and Serbian.
+ISO 8859-2 encodes the
+Latin characters used in many Central and East European languages.
.SS ISO 8859 alphabets
The full set of ISO 8859 alphabets includes:
.TS
ISO 8859-16 Romanian (Latin-10)
.TE
.SS ISO 8859-2 characters
-The following table displays the characters in ISO 8859-2 (Latin-2),
-which are printable and unlisted in the
+The following table displays the characters in ISO 8859-2, which
+are printable and unlisted in the
.BR ascii (7)
manual page.
-.\" The fourth column will only show the proper glyphs
-.\" in an environment configured for ISO 8859-2.
.TS
l l l c lp-1.
Oct Dec Hex Char Description
376 254 FE ţ LATIN SMALL LETTER T WITH CEDILLA
377 255 FF ˙ DOT ABOVE
.TE
+.SH NOTES
+ISO 8859-2 is also known as Latin-2.
.SH SEE ALSO
.BR ascii (7),
+.BR charsets (7),
.BR iso_8859-1 (7),
-.BR iso_8859-16 (7)
-
-.I ISO 8859-2 (Latin 2) Resources
-.UR http://sizif.mf.uni-lj.si\:/linux\:/cee\:/iso8859-2.html
-.UE .
+.BR iso_8859-16 (7),
+.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
-.TH ISO_8859-3 7 2014-02-16 "Linux" "Linux Programmer's Manual"
-.nh
+.TH ISO_8859-3 7 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
iso_8859-3 \- ISO 8859-3 character set encoded in octal, decimal,
and hexadecimal
.SH DESCRIPTION
The ISO 8859 standard includes several 8-bit extensions to the ASCII
character set (also known as ISO 646-IRV).
-ISO 8859-3 encodes the characters used in Southeast European languages.
-.\" (Though in my system with glibc-2.8-20080929
-.\" I found only mt_MT (Malta) using this charset).
+ISO 8859-3 encodes the
+characters used in certain Southeast European languages.
.SS ISO 8859 alphabets
The full set of ISO 8859 alphabets includes:
.TS
are printable and unlisted in the
.BR ascii (7)
manual page.
-.\" The fourth column will only show the proper glyphs
-.\" in an environment configured for ISO 8859-3.
.TS
l l l c lp-1.
Oct Dec Hex Char Description
334 220 DC Ü LATIN CAPITAL LETTER U WITH DIAERESIS
335 221 DD Ŭ LATIN CAPITAL LETTER U WITH BREVE
336 222 DE Ŝ LATIN CAPITAL LETTER S WITH CIRCUMFLEX
-337 223 DF ß LATIN SMALL LETTER SHARP S (German)
+337 223 DF ß LATIN SMALL LETTER SHARP S
340 224 E0 à LATIN SMALL LETTER A WITH GRAVE
341 225 E1 á LATIN SMALL LETTER A WITH ACUTE
342 226 E2 â LATIN SMALL LETTER A WITH CIRCUMFLEX
374 252 FC ü LATIN SMALL LETTER U WITH DIAERESIS
375 253 FD ŭ LATIN SMALL LETTER U WITH BREVE
376 254 FE ŝ LATIN SMALL LETTER S WITH CIRCUMFLEX
-377 255 FF ˙ DOT ABOVE (Mandarin Chinese light tone)
+377 255 FF ˙ DOT ABOVE
.TE
.SH NOTES
ISO 8859-3 is also known as Latin-3.
.SH SEE ALSO
-.BR ascii (7)
+.BR ascii (7),
+.BR charsets (7),
+.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
-.TH ISO_8859-4 7 2014-02-16 "Linux" "Linux Programmer's Manual"
+.TH ISO_8859-4 7 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
iso_8859-4 \- ISO 8859-4 character set encoded in octal, decimal,
and hexadecimal
.SH DESCRIPTION
The ISO 8859 standard includes several 8-bit extensions to the ASCII
character set (also known as ISO 646-IRV).
-ISO 8859-4 encodes the characters used in
-Scandinavian and Baltic languages (Latin-4).
+ISO 8859-4 encodes the
+characters used in Scandinavian and Baltic languages.
.SS ISO 8859 alphabets
The full set of ISO 8859 alphabets includes:
.TS
are printable and unlisted in the
.BR ascii (7)
manual page.
-.\" The fourth column will only show the proper glyphs
-.\" in an environment configured for ISO 8859-4.
.TS
l l l c lp-1.
Oct Dec Hex Char Description
264 180 B4 ´ ACUTE ACCENT
265 181 B5 ĩ LATIN SMALL LETTER I WITH TILDE
266 182 B6 ļ LATIN SMALL LETTER L WITH CEDILLA
-267 183 B7 ˇ CARON (Mandarin Chinese third tone)
+267 183 B7 ˇ CARON
270 184 B8 ¸ CEDILLA
271 185 B9 š LATIN SMALL LETTER S WITH CARON
272 186 BA ē LATIN SMALL LETTER E WITH MACRON
273 187 BB ģ LATIN SMALL LETTER G WITH CEDILLA
274 188 BC ŧ LATIN SMALL LETTER T WITH STROKE
-275 189 BD Ŋ LATIN CAPITAL LETTER ENG (Sami)
+275 189 BD Ŋ LATIN CAPITAL LETTER ENG
276 190 BE ž LATIN SMALL LETTER Z WITH CARON
-277 191 BF ŋ LATIN SMALL LETTER ENG (Sami)
+277 191 BF ŋ LATIN SMALL LETTER ENG
300 192 C0 Ā LATIN CAPITAL LETTER A WITH MACRON
301 193 C1 Á LATIN CAPITAL LETTER A WITH ACUTE
302 194 C2 Â LATIN CAPITAL LETTER A WITH CIRCUMFLEX
334 220 DC Ü LATIN CAPITAL LETTER U WITH DIAERESIS
335 221 DD Ũ LATIN CAPITAL LETTER U WITH TILDE
336 222 DE Ū LATIN CAPITAL LETTER U WITH MACRON
-337 223 DF ß LATIN SMALL LETTER SHARP S (German)
+337 223 DF ß LATIN SMALL LETTER SHARP S
340 224 E0 ā LATIN SMALL LETTER A WITH MACRON
341 225 E1 á LATIN SMALL LETTER A WITH ACUTE
342 226 E2 â LATIN SMALL LETTER A WITH CIRCUMFLEX
374 252 FC ü LATIN SMALL LETTER U WITH DIAERESIS
375 253 FD ũ LATIN SMALL LETTER U WITH TILDE
376 254 FE ū LATIN SMALL LETTER U WITH MACRON
-377 255 FF ˙ DOT ABOVE (Mandarin Chinese light tone)
+377 255 FF ˙ DOT ABOVE
.TE
+.SH NOTES
+ISO 8859-4 is also known as Latin-4.
.SH SEE ALSO
-.BR ascii (7)
+.BR ascii (7),
+.BR charsets (7),
+.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
-.TH ISO_8859-5 7 2014-02-16 "Linux" "Linux Programmer's Manual"
+.TH ISO_8859-5 7 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
iso_8859-5 \- ISO 8859-5 character set encoded in octal, decimal,
and hexadecimal
.SH DESCRIPTION
The ISO 8859 standard includes several 8-bit extensions to the ASCII
character set (also known as ISO 646-IRV).
-ISO 8859-5 encodes the Cyrillic alphabet as used in Russian and Macedonian.
+ISO 8859-5 encodes the
+Cyrillic characters used in many East European languages.
.SS ISO 8859 alphabets
The full set of ISO 8859 alphabets includes:
.TS
are printable and unlisted in the
.BR ascii (7)
manual page.
-.\" The fourth column will only show the proper glyphs
-.\" in an environment configured for ISO 8859-5.
.TS
l l l c lp-1.
Oct Dec Hex Char Description
_
240 160 A0 NO-BREAK SPACE
241 161 A1 Ё CYRILLIC CAPITAL LETTER IO
-242 162 A2 Ђ CYRILLIC CAPITAL LETTER DJE (Serbocroatian)
+242 162 A2 Ђ CYRILLIC CAPITAL LETTER DJE
243 163 A3 Ѓ CYRILLIC CAPITAL LETTER GJE
244 164 A4 Є CYRILLIC CAPITAL LETTER UKRAINIAN IE
245 165 A5 Ѕ CYRILLIC CAPITAL LETTER DZE
.br
BYELORUSSIAN-UKRAINIAN I
T}
-247 167 A7 Ї CYRILLIC CAPITAL LETTER YI (Ukrainian)
+247 167 A7 Ї CYRILLIC CAPITAL LETTER YI
250 168 A8 Ј CYRILLIC CAPITAL LETTER JE
251 169 A9 Љ CYRILLIC CAPITAL LETTER LJE
252 170 AA Њ CYRILLIC CAPITAL LETTER NJE
-253 171 AB Ћ CYRILLIC CAPITAL LETTER TSHE (Serbocroatian)
+253 171 AB Ћ CYRILLIC CAPITAL LETTER TSHE
254 172 AC Ќ CYRILLIC CAPITAL LETTER KJE
255 173 AD SOFT HYPHEN
-256 174 AE Ў CYRILLIC CAPITAL LETTER SHORT U (Byelorussian)
+256 174 AE Ў CYRILLIC CAPITAL LETTER SHORT U
257 175 AF Џ CYRILLIC CAPITAL LETTER DZHE
260 176 B0 А CYRILLIC CAPITAL LETTER A
261 177 B1 Б CYRILLIC CAPITAL LETTER BE
357 239 EF я CYRILLIC SMALL LETTER YA
360 240 F0 № NUMERO SIGN
361 241 F1 ё CYRILLIC SMALL LETTER IO
-362 242 F2 ђ CYRILLIC SMALL LETTER DJE (Serbocroatian)
+362 242 F2 ђ CYRILLIC SMALL LETTER DJE
363 243 F3 ѓ CYRILLIC SMALL LETTER GJE
364 244 F4 є CYRILLIC SMALL LETTER UKRAINIAN IE
365 245 F5 ѕ CYRILLIC SMALL LETTER DZE
366 246 F6 і CYRILLIC SMALL LETTER BYELORUSSIAN-UKRAINIAN I
-367 247 F7 ї CYRILLIC SMALL LETTER YI (Ukrainian)
+367 247 F7 ї CYRILLIC SMALL LETTER YI
370 248 F8 ј CYRILLIC SMALL LETTER JE
371 249 F9 љ CYRILLIC SMALL LETTER LJE
372 250 FA њ CYRILLIC SMALL LETTER NJE
-373 251 FB ј CYRILLIC SMALL LETTER TSHE (Serbocroatian)
+373 251 FB ј CYRILLIC SMALL LETTER TSHE
374 252 FC ќ CYRILLIC SMALL LETTER KJE
375 253 FD § SECTION SIGN
-376 254 FE ў CYRILLIC SMALL LETTER SHORT U (Byelorussian)
+376 254 FE ў CYRILLIC SMALL LETTER SHORT U
377 255 FF џ CYRILLIC SMALL LETTER DZHE
.TE
.SH SEE ALSO
.BR ascii (7),
-.BR koi8-r (7)
+.BR charsets (7),
+.BR koi8-r (7),
+.BR koi8-u (7),
+.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
-.TH ISO_8859-6 7 2014-02-16 "Linux" "Linux Programmer's Manual"
+.TH ISO_8859-6 7 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
iso_8859-6 \- ISO 8859-6 character set encoded in octal, decimal,
and hexadecimal
.SH DESCRIPTION
The ISO 8859 standard includes several 8-bit extensions to the ASCII
character set (also known as ISO 646-IRV).
-ISO 8859-6 encodes the characters used in the Arabic language.
+ISO 8859-6 encodes the
+characters used in the Arabic language.
.SS ISO 8859 alphabets
The full set of ISO 8859 alphabets includes:
.TS
are printable and unlisted in the
.BR ascii (7)
manual page.
-.\" The fourth column will only show the proper glyphs
-.\" in an environment configured for ISO 8859-6.
.TS
l l l c lp-1.
Oct Dec Hex Char Description
ISO 8859-6 lacks the glyphs required for many related languages,
such as Urdu and Persian (Farsi).
.SH SEE ALSO
-.BR ascii (7)
+.BR ascii (7),
+.BR charsets (7),
+.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
-.TH ISO_8859-7 7 2014-02-16 "Linux" "Linux Programmer's Manual"
-.nh
+.TH ISO_8859-7 7 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
iso_8859-7 \- ISO 8859-7 character set encoded in octal, decimal,
and hexadecimal
are printable and unlisted in the
.BR ascii (7)
manual page.
-.\" The fourth column will only show the proper glyphs
-.\" in an environment configured for ISO 8859-7.
.TS
l l l c lp-1.
Oct Dec Hex Char Description
.SH NOTES
ISO 8859-7 was formerly known as ELOT-928 or ECMA-118:1986.
.SH SEE ALSO
-.BR ascii (7)
+.BR ascii (7),
+.BR charsets (7),
+.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\" Eli Zaretskii <eliz@gnu.org> made valuable suggestions
.\"
-.TH ISO_8859-8 7 2014-02-16 "Linux" "Linux Programmer's Manual"
+.TH ISO_8859-8 7 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
iso_8859-8 \- ISO 8859-8 character set encoded in octal, decimal,
and hexadecimal
.SH DESCRIPTION
The ISO 8859 standard includes several 8-bit extensions to the ASCII
character set (also known as ISO 646-IRV).
-ISO 8859-8, or "ISO Hebrew" encodes the
-characters used in Modern Hebrew (or Ivrit).
-Neither short vowels nor diacritical marks are included,
-and Yiddish is not provided for.
+ISO 8859-8 encodes the
+characters used in Modern Hebrew.
.SS ISO 8859 alphabets
The full set of ISO 8859 alphabets includes:
.TS
are printable and unlisted in the
.BR ascii (7)
manual page.
-.\" The fourth column will only show the proper glyphs
-.\" in an environment configured for ISO 8859-8.
.TS
l l l c lp-1.
Oct Dec Hex Char Description
.TE
.SH NOTES
ISO 8859-8 was also known as ISO-IR-138.
+ISO 8859-8 includes neither short vowels nor diacritical marks,
+and Yiddish is not provided for.
.SH SEE ALSO
-.BR ascii (7)
+.BR ascii (7),
+.BR charsets (7),
+.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
-.TH ISO_8859-9 7 2014-02-16 "Linux" "Linux Programmer's Manual"
-.nh
+.TH ISO_8859-9 7 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
iso_8859-9 \- ISO 8859-9 character set encoded in octal, decimal,
and hexadecimal
.SH DESCRIPTION
The ISO 8859 standard includes several 8-bit extensions to the ASCII
character set (also known as ISO 646-IRV).
-ISO 8859-9, also known as
-the "Latin Alphabet No. 5", encodes the characters used in Turkish.
+ISO 8859-9 encodes the
+characters used in Turkish.
.SS ISO 8859 alphabets
The full set of ISO 8859 alphabets includes:
.TS
ISO 8859-16 Romanian (Latin-10)
.TE
.SS ISO 8859-9 characters
-The following table displays the characters in ISO 8859-9 (Latin-5),
-which are printable and unlisted in the
+The following table displays the characters in ISO 8859-9, which
+are printable and unlisted in the
.BR ascii (7)
manual page.
-.\" The fourth column will only show the proper glyphs
-.\" in an environment configured for ISO 8859-9.
.TS
l l l c lp-1.
Oct Dec Hex Char Description
376 254 FE ş LATIN SMALL LETTER S WITH CEDILLA
377 255 FF ÿ LATIN SMALL LETTER Y WITH DIAERESIS
.TE
+.SH NOTES
+ISO 8859-9 is also known as Latin-5.
.SH SEE ALSO
-.BR ascii (7)
+.BR ascii (7),
+.BR charsets (7),
+.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
'\" t -*- coding: UTF-8 -*-
.\" Copyright 2001 Alexey Mahotkin <alexm@hsys.msk.ru>
.\"
-.\" Lots of text ripped from http://koi8.pp.ru/
-.\"
.\" %%%LICENSE_START(GPLv2+_DOC_FULL)
.\" This is free documentation; you can redistribute it and/or
.\" modify it under the terms of the GNU General Public License as
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
-.TH KOI8-R 7 2014-02-16 "Linux" "Linux Programmer's Manual"
-.nh
+.TH KOI8-R 7 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
-koi8-r \- Russian character set encoded in octal, decimal, and
-hexadecimal
+koi8-r \- Russian character set encoded in octal, decimal,
+and hexadecimal
.SH DESCRIPTION
-KOI8-R is the character set of choice for encoding Russian texts for
-many UNIX-like operation systems.
-KOI8-R is a successor for KOI-8, a
-de-facto standard for Internet Mail, News, WWW, and other interactive
-services at least all over the ex-SU territory.
-.PP
-KOI8-R is defined by RFC\ 1489 (Registration of a Cyrillic Character
-Set).
-.SH NOTES
-KOI8-R was designed for mixed Russian/English texts and covers
-only Russian Cyrillic characters,
-so if you're looking for Cyrillic characters for Ukrainian,
-Byelorussian, and so on,
-try ISO-IR-111, or KOI8-U
-(Ukrainian Character Set), or KOI8-C (for ancient Russian texts)
-instead, which are identical to KOI8-R in the Russian Cyrillic letters
-area.
-.PP
-A more complete set of Cyrillic characters is also defined by the
-ISO-8859-5 character set.
+RFC\ 1489 defines an 8-bit character set, KOI8-R.
+KOI8-R encodes the
+characters used in Russian.
.SS KOI8-R characters
The following table displays the characters in KOI8-R, which
are printable and unlisted in the
376 254 FE Ч CYRILLIC CAPITAL LETTER CHE
377 255 FF Ъ CYRILLIC CAPITAL LETTER HARD SIGN
.TE
+.SH NOTES
+The differences with KOI8-U are in the hex positions
+A4, A6, A7, AD, B4, B6, B7, and BD.
.SH SEE ALSO
.BR ascii (7),
-.BR iso-8859-5 (7),
-.BR koi8-u (7)
-
-RFC\ 1489,
-.UR http://koi8.pp.ru/
-.UE
+.BR charsets (7),
+.BR iso_8859-5 (7),
+.BR koi8-u (7),
+.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\" 2009-01-15, mtk, Some edits
.\"
-.TH KOI8-U 7 2014-03-18 "Linux" "Linux Programmer's Manual"
-.nh
+.TH KOI8-U 7 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
-koi8-u \- Ukrainian character set encoded in octal, decimal, and
-hexadecimal
+koi8-u \- Ukrainian character set encoded in octal, decimal,
+and hexadecimal
.SH DESCRIPTION
-KOI8-U (KOI8 Ukrainian, described in RFC\ 2310)
-is the de-facto standard character set for encoding Ukrainian texts.
-KOI8-U is compatible with KOI8-R (RFC 1489)
-for all Russian letters, and extends KOI8-R with four
-Ukrainian letters (in both uppercase and lowercase)
-in locations that are compliant with ISO-IR-111.
+RFC\ 2310 defines an 8-bit character set, KOI8-U.
+KOI8-U encodes the
+characters used in Ukrainian and Byelorussian.
.SS KOI8-U characters
The following table displays the characters in KOI8-U, which
are printable and unlisted in the
.BR ascii (7)
manual page.
-.\" The fourth column will only show the proper glyphs
-.\" in an environment configured for koi8-u.
.TS
l l l c lp-1.
Oct Dec Hex Char Description
A4, A6, A7, AD, B4, B6, B7, and BD.
.SH SEE ALSO
.BR ascii (7),
-.BR koi8-r (7)
+.BR charsets (7),
+.BR iso_8859-5 (7),
+.BR koi8-r (7),
+.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH LIBC 7 2014-04-20 "Linux" "Linux Programmer's Manual"
+.TH LIBC 7 2014-07-08 "Linux" "Linux Programmer's Manual"
.SH NAME
libc \- overview of standard C libraries on Linux
.SH DESCRIPTION
(as well as many minor versions of those releases).
For a while,
Linux libc was the standard C library in many Linux distributions.
+
However, notwithstanding the original motivations of the Linux libc effort,
-by the time glibc 2.0 was released, it was clearly superior to Linux libc,
+by the time glibc 2.0 was released (in 1997),
+it was clearly superior to Linux libc,
and all major Linux distributions that had been using Linux libc
soon switched back to glibc.
-(Since this switch occurred over a decade ago,
+Since this switch occurred long ago,
.I man-pages
no longer takes care to document Linux libc details.
Nevertheless, the history is visible in vestiges of information
in particular, references to
.IR libc4
and
-.IR libc5 .)
+.IR libc5 .
.SS Other C libraries
There are various other less widely used C libraries for Linux.
These libraries are generally smaller than glibc,
.UR http://www.musl-libc.org/
.I "musl libc"
.UE .
-Details of these libraries are generally not covered by the
+Details of these libraries are covered by the
.I man-pages
-project.
+project, where they are known.
.SH SEE ALSO
.BR syscalls (2),
.BR getauxval (3),
.BR standards (7),
.BR vdso (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
(a period in most English-speaking countries,
but a comma in many other regions).
It affects functions such as
-.BR printf (3)
+.BR printf (3),
.BR scanf (3),
and
.BR strtod (3).
This category governs the formatting used for date and time values.
For example, most of Europe uses a 24-hour clock versus the
12-hour clock used in the United States.
-the setting of this category affects the behavior of functions such as
+The setting of this category affects the behavior of functions such as
.BR strftime (3)
and
.BR strptime (3).
.BR strxfrm (3),
.BR uselocale (3),
.BR wcstombs (3),
-.BR locale (5)
+.BR locale (5),
+.BR charsets (7),
+.BR unicode (7),
+.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
RFC\ 2822 (Internet Message Format)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2007-05-30 created by mtk, using text from old man.7 plus
.\" rewrites and additional text.
.\"
-.TH MAN-PAGES 7 2014-03-16 "Linux" "Linux Programmer's Manual"
+.TH MAN-PAGES 7 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
man-pages \- conventions for writing Linux man pages
.SH SYNOPSIS
.IR 7 ).
.TP
.I date
-The date of the last revision\(emremember to change this every time a
-nontrivial change is made to the man page.
+The date of the last nontrivial change that was made to the man page.
+(Within the
+.I man-pages
+project, the necessary updates to these timetamps are handled
+automatically by scripts, so there is no need to manually update
+them as part of a patch.)
Dates should be written in the form YYYY-MM-DD.
.TP
.I source
.TP 14
.B NAME
The name of this manual page.
+
See
.BR man (7)
for important details of the line(s) that should follow the
dictates otherwise.
.TP
.B SYNOPSIS
-briefly describes the command or function's interface.
+A brief summary of the command or function's interface.
+
For commands, this shows the syntax of the command and its arguments
(including options);
boldface is used for as-is text and italics are used to
.TP
.B CONFIGURATION
Configuration details for a device.
+
This section normally appears only in Section 4 pages.
.TP
.B DESCRIPTION
-gives an explanation of what the program, function, or format does.
+An explanation of what the program, function, or format does.
+
Discuss how it interacts with files and standard input, and what it
produces on standard output or standard error.
Omit internals and implementation details unless they're critical for
(which is typical in embedded systems, for example).
.TP
.B OPTIONS
-describes the command-line options accepted by a
+A description of the command-line options accepted by a
program and how they change its behavior.
+
This section should appear only for Section 1 and 8 manual pages.
.\" .TP
.\" .B USAGE
.\" describes the grammar of any sublanguage this implements.
.TP
.B EXIT STATUS
-lists the possible exit status values of a program and
+A list of the possible exit status values of a program and
the conditions that cause these values to be returned.
+
This section should appear only for Section 1 and 8 manual pages.
.TP
.B RETURN VALUE
.I errno
in the event of an error, along with information about the cause
of the errors.
+
.IR "The error list should be in alphabetical order" .
.TP
.B ENVIRONMENT
-lists all environment variables that affect the program or function
+A list of all environment variables that affect the program or function
and how they affect it.
.TP
.B FILES
-lists the files the program or function uses, such as
+A list of the files the program or function uses, such as
configuration files, startup files,
and files the program directly operates on.
+
Give the full pathname of these files, and use the installation
process to modify the directory part to match user preferences.
For many programs, the default installation location is in
.B ATTRIBUTES
A summary of various attributes of the function(s) documented on this page,
broken into subsections.
+
The following subsections are defined:
.sp
.RS
A brief summary of the Linux kernel or glibc versions where a
system call or library function appeared,
or changed significantly in its operation.
+
As a general rule, every new interface should
include a VERSIONS section in its manual page.
Unfortunately,
in which various system calls first appeared.
.TP
.B CONFORMING TO
-describes any standards or conventions that relate to the function
+A description of any standards or conventions that relate to the function
or command described by the manual page.
+
The preferred terms to use for the various standards are listed as
headings in
.BR standards (7).
+
For a page in Section 2 or 3,
this section should note the POSIX.1
version(s) that the call conforms to,
or the SVr4 and 4.xBSD implementation standards,
unless the call was specified in those standards,
but isn't in the current version of POSIX.1.)
-(See
-.BR standards (7).)
If the call is not governed by any standards but commonly
exists on other systems, note them.
terminate the list with a period (\(aq.\(aq).
.TP
.B NOTES
-provides miscellaneous notes.
+Miscellaneous notes.
+
For Section 2 and 3 man pages you may find it useful to include
subsections (\fBSS\fP) named \fILinux Notes\fP and \fIGlibc Notes\fP.
+
+In Section 2, use the heading
+.I "C library/kernel ABI differences"
+to mark off notes that describe the differences (if any) between
+the C library wrapper function for a system call and
+the raw system call interface provided by the kernel.
.TP
.B BUGS
-lists limitations, known defects or inconveniences,
+A list of limitations, known defects or inconveniences,
and other questionable activities.
.TP
.B EXAMPLE
-provides one or more examples describing how this function, file or
+One or more examples demonstrating how this function, file or
command is used.
+
For details on writing example programs,
see \fIExample Programs\fP below.
.TP
.B AUTHORS
-lists authors of the documentation or program.
+A list of authors of the documentation or program.
+
\fBUse of an AUTHORS section is strongly discouraged\fP.
Generally, it is better not to clutter every page with a list
of (over time potentially numerous) authors;
an address for reporting bugs, place this under the BUGS section.
.TP
.B SEE ALSO
-provides a comma-separated list of related man pages,
-ordered by section number and
-then alphabetically by name, possibly followed by
+A comma-separated list of related man pages, possibly followed by
other related pages or documents.
+
+The list should be ordered by section number and
+then alphabetically by name
Do not terminate this with a period.
.IP
Where the SEE ALSO list contains many long manual page names,
.BR man (7),
.BR mdoc (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR mdoc (7),
.BR mdoc.samples (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.I "info libc"
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.Xr man 7 ,
.Xr man-pages 7
.Sh COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.Em man-pages
project.
A description of the project,
.Xr groff_mdoc 7 ,
.Xr mdoc 7
.Sh COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.Em man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH MQ_OVERVIEW 7 2009-09-27 "Linux" "Linux Programmer's Manual"
+.TH MQ_OVERVIEW 7 2014-09-21 "Linux" "Linux Programmer's Manual"
.SH NAME
mq_overview \- overview of POSIX message queues
.SH DESCRIPTION
.IR librt .
.SS /proc interfaces
The following interfaces can be used to limit the amount of
-kernel memory consumed by POSIX message queues:
+kernel memory consumed by POSIX message queues and to set
+the default attributes for new message queues:
+.TP
+.IR /proc/sys/fs/mqueue/msg_default " (since Linux 3.5)"
+This file defines the value used for a new queue's
+.I mq_maxmsg
+setting when the queue is created with a call to
+.BR mq_open (3)
+where
+.I attr
+is specified as NULL.
+The default value for this file is 10.
+The minimum and maximum are as for
+.IR /proc/sys/fs/mqueue/msg_max .
+A new queue's default
+.I mq_maxmsg
+value will be the smaller of
+.IR msg_default
+and
+.IR msg_max .
+Up until Linux 2.6.28, the default
+.I mq_maxmsg
+was 10;
+from Linux 2.6.28 to Linux 3.4, the default was the value defined for the
+.I msg_max
+limit.
.TP
.I /proc/sys/fs/mqueue/msg_max
This file can be used to view and change the ceiling value for the
is 10.
The minimum value is 1 (10 in kernels before 2.6.28).
The upper limit is
-.BR HARD_MAX :
-.IR "(131072\ /\ sizeof(void\ *))"
-(32768 on Linux/86).
-This limit is ignored for privileged processes
+.BR HARD_MSGMAX .
+The
+.I msg_max
+limit is ignored for privileged processes
.RB ( CAP_SYS_RESOURCE ),
but the
-.BR HARD_MAX
+.BR HARD_MSGMAX
ceiling is nevertheless imposed.
+
+The definition of
+.BR HARD_MSGMAX
+has changed across kernel versions:
+.RS
+.IP * 3
+Up to Linux 2.6.32:
+.IR "131072\ /\ sizeof(void\ *)"
+.IP *
+Linux 2.6.33 to 3.4:
+.IR "(32768\ *\ sizeof(void\ *) / 4)"
+.IP *
+Since Linux 3.5:
+.\" commit 5b5c4d1a1440e94994c73dddbad7be0676cd8b9a
+65,536
+.RE
+.TP
+.IR /proc/sys/fs/mqueue/msgsize_default " (since Linux 3.5)"
+This file defines the value used for a new queue's
+.I mq_msgsize
+setting when the queue is created with a call to
+.BR mq_open (3)
+where
+.I attr
+is specified as NULL.
+The default value for this file is 8192 (bytes).
+The minimum and maximum are as for
+.IR /proc/sys/fs/mqueue/msgsize_max .
+If
+.IR msgsize_default
+exceeds
+.IR msgsize_max ,
+a new queue's default
+.I mq_msgsize
+value is capped to the
+.I msgsize_max
+limit.
+Up until Linux 2.6.28, the default
+.I mq_msgsize
+was 8192;
+from Linux 2.6.28 to Linux 3.4, the default was the value defined for the
+.I msgsize_max
+limit.
.TP
.I /proc/sys/fs/mqueue/msgsize_max
This file can be used to view and change the ceiling on the
The minimum value is 128 (8192 in kernels before 2.6.28).
The upper limit for
.I msgsize_max
-is 1,048,576 (in kernels before 2.6.28, the upper limit was
-.BR INT_MAX ;
-that is, 2,147,483,647 on Linux/86).
-This limit is ignored for privileged processes
-.RB ( CAP_SYS_RESOURCE ).
+has varied across kernel versions:
+.RS
+.IP * 3
+Before Linux 2.6.28, the upper limit is
+.BR INT_MAX .
+.IP *
+From Linux 2.6.28 to 3.4, the limit is 1,048,576.
+.IP *
+Since Linux 3.5, the limit is 16,777,216
+.RB ( HARD_MSGSIZEMAX ).
+.RE
+.IP
+The
+.I msgsize_max
+limit is ignored for privileged process
+.RB ( CAP_SYS_RESOURCE ),
+but, since Linux 3.5, the
+.BR HARD_MSGSIZEMAX
+ceiling is enforced for privileged processes.
.TP
.I /proc/sys/fs/mqueue/queues_max
This file can be used to view and change the system-wide limit on the
number of message queues that can be created.
-Only privileged processes
-.RB ( CAP_SYS_RESOURCE )
-can create new message queues once this limit has been reached.
The default value for
.I queues_max
-is 256; it can be changed to any value in the range 0 to INT_MAX.
+is 256.
+No ceiling is imposed on the
+.I queues_max
+limit; privileged processes
+.RB ( CAP_SYS_RESOURCE )
+can exceed the limit (but see BUGS).
.SS Resource limit
The
.B RLIMIT_MSGQUEUE
or
.BR epoll (7).
This is not portable.
+.SS IPC namespaces
+For a discussion of the interaction of System V IPC objects and
+IPC namespaces, see
+.BR namespaces (7).
.SH CONFORMING TO
POSIX.1-2001.
.SH NOTES
.SH EXAMPLE
An example of the use of various message queue functions is shown in
.BR mq_notify (3).
+.SH BUGS
+In Linux versions 3.5 to 3.14, the kernel imposed a ceiling of 1024
+.RB ( HARD_QUEUESMAX )
+on the value to which the
+.I queues_max
+limit could be raised,
+and the ceiling was enforced even for privileged processes.
+This ceiling value was removed in Linux 3.14,
+and patches to stable kernels 3.5.x to 3.13.x also removed the ceiling.
.SH SEE ALSO
.BR getrlimit (2),
.BR mq_getsetattr (2),
.BR mq_receive (3),
.BR mq_send (3),
.BR mq_unlink (3),
-.BR epoll (7)
+.BR epoll (7),
+.BR namespaces (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
--- /dev/null
+.\" Copyright (c) 2013 by Michael Kerrisk <mtk.manpages@gmail.com>
+.\" and Copyright (c) 2012 by Eric W. Biederman <ebiederm@xmission.com>
+.\"
+.\" %%%LICENSE_START(VERBATIM)
+.\" Permission is granted to make and distribute verbatim copies of this
+.\" manual provided the copyright notice and this permission notice are
+.\" preserved on all copies.
+.\"
+.\" Permission is granted to copy and distribute modified versions of this
+.\" manual under the conditions for verbatim copying, provided that the
+.\" entire resulting derived work is distributed under the terms of a
+.\" permission notice identical to this one.
+.\"
+.\" Since the Linux kernel and libraries are constantly changing, this
+.\" manual page may be incorrect or out-of-date. The author(s) assume no
+.\" responsibility for errors or omissions, or for damages resulting from
+.\" the use of the information contained herein. The author(s) may not
+.\" have taken the same level of care in the production of this manual,
+.\" which is licensed free of charge, as they might when working
+.\" professionally.
+.\"
+.\" Formatted or processed versions of this manual, if unaccompanied by
+.\" the source, must acknowledge the copyright and authors of this work.
+.\" %%%LICENSE_END
+.\"
+.\"
+.TH NAMESPACES 7 2014-09-21 "Linux" "Linux Programmer's Manual"
+.SH NAME
+namespaces \- overview of Linux namespaces
+.SH DESCRIPTION
+A namespace wraps a global system resource in an abstraction that
+makes it appear to the processes within the namespace that they
+have their own isolated instance of the global resource.
+Changes to the global resource are visible to other processes
+that are members of the namespace, but are invisible to other processes.
+One use of namespaces is to implement containers.
+
+Linux provides the following namespaces:
+
+.TS
+lB lB lB
+l lB l.
+Namespace Constant Isolates
+IPC CLONE_NEWIPC System V IPC, POSIX message queues
+Network CLONE_NEWNET Network devices, stacks, ports, etc.
+Mount CLONE_NEWNS Mount points
+PID CLONE_NEWPID Process IDs
+User CLONE_NEWUSER User and group IDs
+UTS CLONE_NEWUTS Hostname and NIS domain name
+.TE
+
+This page describes the various namespaces and the associated
+.I /proc
+files, and summarizes the APIs for working with namespaces.
+.\"
+.\" ==================== The namespaces API ====================
+.\"
+.SS The namespaces API
+As well as various
+.I /proc
+files described below,
+the namespaces API includes the following system calls:
+.TP
+.BR clone (2)
+The
+.BR clone (2)
+system call creates a new process.
+If the
+.I flags
+argument of the call specifies one or more of the
+.B CLONE_NEW*
+flags listed below, then new namespaces are created for each flag,
+and the child process is made a member of those namespaces.
+(This system call also implements a number of features
+unrelated to namespaces.)
+.TP
+.BR setns (2)
+The
+.BR setns (2)
+system call allows the calling process to join an existing namespace.
+The namespace to join is specified via a file descriptor that refers to
+one of the
+.IR /proc/[pid]/ns
+files described below.
+.TP
+.BR unshare (2)
+The
+.BR unshare (2)
+system call moves the calling process to a new namespace.
+If the
+.I flags
+argument of the call specifies one or more of the
+.B CLONE_NEW*
+flags listed below, then new namespaces are created for each flag,
+and the calling process is made a member of those namespaces.
+(This system call also implements a number of features
+unrelated to namespaces.)
+.PP
+Creation of new namespaces using
+.BR clone (2)
+and
+.BR unshare (2)
+in most cases requires the
+.BR CAP_SYS_ADMIN
+capability.
+User namespaces are the exception: since Linux 3.8,
+no privilege is required to create a user namespace.
+.\"
+.\" ==================== The /proc/[pid]/ns/ directory ====================
+.\"
+.SS The /proc/[pid]/ns/ directory
+Each process has a
+.IR /proc/[pid]/ns/
+.\" See commit 6b4e306aa3dc94a0545eb9279475b1ab6209a31f
+subdirectory containing one entry for each namespace that
+supports being manipulated by
+.BR setns (2):
+
+.in +4n
+.nf
+$ \fBls -l /proc/$$/ns\fP
+total 0
+lrwxrwxrwx. 1 mtk mtk 0 Jan 14 01:20 ipc -> ipc:[4026531839]
+lrwxrwxrwx. 1 mtk mtk 0 Jan 14 01:20 mnt -> mnt:[4026531840]
+lrwxrwxrwx. 1 mtk mtk 0 Jan 14 01:20 net -> net:[4026531956]
+lrwxrwxrwx. 1 mtk mtk 0 Jan 14 01:20 pid -> pid:[4026531836]
+lrwxrwxrwx. 1 mtk mtk 0 Jan 14 01:20 user -> user:[4026531837]
+lrwxrwxrwx. 1 mtk mtk 0 Jan 14 01:20 uts -> uts:[4026531838]
+.fi
+.in
+
+Bind mounting (see
+.BR mount (2))
+one of the files in this directory
+to somewhere else in the filesystem keeps
+the corresponding namespace of the process specified by
+.I pid
+alive even if all processes currently in the namespace terminate.
+
+Opening one of the files in this directory
+(or a file that is bind mounted to one of these files)
+returns a file handle for
+the corresponding namespace of the process specified by
+.IR pid .
+As long as this file descriptor remains open,
+the namespace will remain alive,
+even if all processes in the namespace terminate.
+The file descriptor can be passed to
+.BR setns (2).
+
+In Linux 3.7 and earlier, these files were visible as hard links.
+Since Linux 3.8, they appear as symbolic links.
+If two processes are in the same namespace, then the inode numbers of their
+.IR /proc/[pid]/ns/xxx
+symbolic links will be the same; an application can check this using the
+.I stat.st_ino
+field returned by
+.BR stat (2).
+The content of this symbolic link is a string containing
+the namespace type and inode number as in the following example:
+
+.in +4n
+.nf
+$ \fBreadlink /proc/$$/ns/uts\fP
+uts:[4026531838]
+.fi
+.in
+
+The files in this subdirectory are as follows:
+.TP
+.IR /proc/[pid]/ns/ipc " (since Linux 3.0)"
+This file is a handle for the IPC namespace of the process.
+.TP
+.IR /proc/[pid]/ns/mnt " (since Linux 3.8)"
+This file is a handle for the mount namespace of the process.
+.TP
+.IR /proc/[pid]/ns/net " (since Linux 3.0)"
+This file is a handle for the network namespace of the process.
+.TP
+.IR /proc/[pid]/ns/pid " (since Linux 3.8)"
+This file is a handle for the PID namespace of the process.
+.TP
+.IR /proc/[pid]/ns/user " (since Linux 3.8)"
+This file is a handle for the user namespace of the process.
+.TP
+.IR /proc/[pid]/ns/uts " (since Linux 3.0)"
+This file is a handle for the UTS namespace of the process.
+.\"
+.\" ==================== IPC namespaces ====================
+.\"
+.SS IPC namespaces (CLONE_NEWIPC)
+IPC namespaces isolate certain IPC resources,
+namely, System V IPC objects (see
+.BR svipc (7))
+and (since Linux 2.6.30)
+.\" commit 7eafd7c74c3f2e67c27621b987b28397110d643f
+.\" https://lwn.net/Articles/312232/
+POSIX message queues (see
+.BR mq_overview (7).
+The common characteristic of these IPC mechanisms is that IPC
+objects are identified by mechanisms other than filesystem
+pathnames.
+
+Each IPC namespace has its own set of System V IPC identifiers and
+its own POSIX message queue filesystem.
+Objects created in an IPC namespace are visible to all other processes
+that are members of that namespace,
+but are not visible to processes in other IPC namespaces.
+
+The following
+.I /proc
+interfaces are distinct in each IPC namespace:
+.IP * 3
+The POSIX message queue interfaces in
+.IR /proc/sys/fs/mqueue .
+.IP *
+The System V IPC interfaces in
+.IR /proc/sys/kernel ,
+namely:
+.IR msgmax ,
+.IR msgmnb ,
+.IR msgmni ,
+.IR sem ,
+.IR shmall ,
+.IR shmmax ,
+.IR shmmni ,
+and
+.IR shm_rmid_forced .
+.IP *
+The System V IPC interfaces in
+.IR /proc/sysvipc .
+.PP
+When an IPC namespace is destroyed
+(i.e., when the last process that is a member of the namespace terminates),
+all IPC objects in the namespace are automatically destroyed.
+
+Use of IPC namespaces requires a kernel that is configured with the
+.B CONFIG_IPC_NS
+option.
+.\"
+.\" ==================== Network namespaces ====================
+.\"
+.SS Network namespaces (CLONE_NEWNET)
+Network namespaces provide isolation of the system resources associated
+with networking: network devices, IPv4 and IPv6 protocol stacks,
+IP routing tables, firewalls, the
+.I /proc/net
+directory, the
+.I /sys/class/net
+directory, port numbers (sockets), and so on.
+A physical network device can live in exactly one
+network namespace.
+A virtual network device ("veth") pair provides a pipe-like abstraction
+.\" FIXME Add pointer to veth(4) page when it is eventually completed
+that can be used to create tunnels between network namespaces,
+and can be used to create a bridge to a physical network device
+in another namespace.
+
+When a network namespace is freed
+(i.e., when the last process in the namespace terminates),
+its physical network devices are moved back to the
+initial network namespace (not to the parent of the process).
+
+Use of network namespaces requires a kernel that is configured with the
+.B CONFIG_NET_NS
+option.
+.\"
+.\" ==================== Mount namespaces ====================
+.\"
+.SS Mount namespaces (CLONE_NEWNS)
+Mount namespaces isolate the set of filesystem mount points,
+meaning that processes in different mount namespaces can
+have different views of the filesystem hierarchy.
+The set of mounts in a mount namespace is modified using
+.BR mount (2)
+and
+.BR umount (2).
+
+The
+.IR /proc/[pid]/mounts
+file (present since Linux 2.4.19)
+lists all the filesystems currently mounted in the
+process's mount namespace.
+The format of this file is documented in
+.BR fstab (5).
+Since kernel version 2.6.15, this file is pollable:
+after opening the file for reading, a change in this file
+(i.e., a filesystem mount or unmount) causes
+.BR select (2)
+to mark the file descriptor as readable, and
+.BR poll (2)
+and
+.BR epoll_wait (2)
+mark the file as having an error condition.
+
+The
+.IR /proc/[pid]/mountstats
+file (present since Linux 2.6.17)
+exports information (statistics, configuration information)
+about the mount points in the process's mount namespace.
+This file is only readable by the owner of the process.
+Lines in this file have the form:
+.RS
+.in 12
+.nf
+
+device /dev/sda7 mounted on /home with fstype ext3 [statistics]
+( 1 ) ( 2 ) (3 ) (4)
+.fi
+.in
+
+The fields in each line are:
+.TP 5
+(1)
+The name of the mounted device
+(or "nodevice" if there is no corresponding device).
+.TP
+(2)
+The mount point within the filesystem tree.
+.TP
+(3)
+The filesystem type.
+.TP
+(4)
+Optional statistics and configuration information.
+Currently (as at Linux 2.6.26), only NFS filesystems export
+information via this field.
+.RE
+.\"
+.\" ==================== PID namespaces ====================
+.\"
+.SS PID namespaces (CLONE_NEWPID)
+See
+.BR pid_namespaces (7).
+.\"
+.\" ==================== User namespaces ====================
+.\"
+.SS User namespaces (CLONE_NEWUSER)
+See
+.BR user_namespaces (7).
+.\"
+.\" ==================== UTS namespaces ====================
+.\"
+.SS UTS namespaces (CLONE_NEWUTS)
+UTS namespaces provide isolation of two system identifiers:
+the hostname and the NIS domain name.
+These identifiers are set using
+.BR sethostname (2)
+and
+.BR setdomainname (2),
+and can be retrieved using
+.BR uname (2),
+.BR gethostname (2),
+and
+.BR getdomainname (2).
+
+Use of UTS namespaces requires a kernel that is configured with the
+.B CONFIG_UTS_NS
+option.
+.SH CONFORMING TO
+Namespaces are a Linux-specific feature.
+.SH EXAMPLE
+See
+.BR user_namespaces (7).
+.SH SEE ALSO
+.BR nsenter (1),
+.BR readlink (1),
+.BR unshare (1),
+.BR clone (2),
+.BR setns (2),
+.BR unshare (2),
+.BR proc (5),
+.BR credentials (7),
+.BR capabilities (7),
+.BR pid_namespaces (7),
+.BR user_namespaces (7),
+.BR switch_root (8)
+.SH COLOPHON
+This page is part of release 3.75 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.
.\" .IR ifr_slave .
.\" Setting the slave device is a privileged operation.
.\" .PP
-.\" FIXME add amateur radio stuff.
+.\" FIXME . add amateur radio stuff.
.PP
Most protocols support their own ioctls to configure protocol-specific
interface options.
.BR ip (7),
.BR rtnetlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
Return all entries matching criteria passed in message content.
Not implemented yet.
T}
-.\" FIXME NLM_F_ATOMIC is not used any more?
+.\" FIXME NLM_F_ATOMIC is not used anymore?
NLM_F_ATOMIC:Return an atomic snapshot of the table.
NLM_F_DUMP:T{
Convenience macro; equivalent to
RFC 3549 "Linux Netlink as an IP Services Protocol"
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR cpuset (7),
.BR numactl (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.fi
.\"
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\" $Id: packet.7,v 1.13 2000/08/14 08:03:45 ak Exp $
.\"
-.TH PACKET 7 2014-04-28 "Linux" "Linux Programmer's Manual"
+.TH PACKET 7 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
packet \- packet interface on device level
.SH SYNOPSIS
.nf
.B #include <sys/socket.h>
.br
-.B #include <netpacket/packet.h>
+.B #include <linux/if_packet.h>
.br
.B #include <net/ethernet.h> /* the L2 protocols */
.sp
Earlier Linux versions supported only
.BR SOCK_PACKET .
.PP
-The include file
-.I <netpacket/packet.h>
-is present since glibc 2.1.
-Older systems need:
-.sp
-.in +4n
-.nf
-#include <asm/types.h>
-#include <linux/if_packet.h>
-#include <linux/if_ether.h> /* The L2 protocols */
-.fi
-.in
.SH NOTES
For portable programs it is suggested to use
.B AF_PACKET
.fi
.in
-This is fixed in later glibc versions and also does not occur on
-libc5 systems.
+This is fixed in later glibc versions.
The IEEE 802.2/803.3 LLC handling could be considered as a bug.
and
.BR PACKET_TX_RING .
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
instead of the effective group ID.
See
.BR setfsgid (2).
-.\" FIXME say something about filesystem mounted read-only ?
+.\" FIXME . say something about filesystem mounted read-only ?
.SS Bypassing permission checks: superuser and capabilities
On a traditional UNIX system, the superuser
.RI ( root ,
.B CAP_DAC_READ_SEARCH
capability grants read and search permission
on directories, and read permission on ordinary files.
-.\" FIXME say something about immutable files
-.\" FIXME say something about ACLs
+.\" FIXME . say something about immutable files
+.\" FIXME . say something about ACLs
.SH SEE ALSO
.BR readlink (2),
.BR capabilities (7),
.BR credentials (7),
.BR symlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
--- /dev/null
+.\" Copyright (c) 2013 by Michael Kerrisk <mtk.manpages@gmail.com>
+.\" and Copyright (c) 2012 by Eric W. Biederman <ebiederm@xmission.com>
+.\"
+.\" %%%LICENSE_START(VERBATIM)
+.\" Permission is granted to make and distribute verbatim copies of this
+.\" manual provided the copyright notice and this permission notice are
+.\" preserved on all copies.
+.\"
+.\" Permission is granted to copy and distribute modified versions of this
+.\" manual under the conditions for verbatim copying, provided that the
+.\" entire resulting derived work is distributed under the terms of a
+.\" permission notice identical to this one.
+.\"
+.\" Since the Linux kernel and libraries are constantly changing, this
+.\" manual page may be incorrect or out-of-date. The author(s) assume no
+.\" responsibility for errors or omissions, or for damages resulting from
+.\" the use of the information contained herein. The author(s) may not
+.\" have taken the same level of care in the production of this manual,
+.\" which is licensed free of charge, as they might when working
+.\" professionally.
+.\"
+.\" Formatted or processed versions of this manual, if unaccompanied by
+.\" the source, must acknowledge the copyright and authors of this work.
+.\" %%%LICENSE_END
+.\"
+.\"
+.TH PID_NAMESPACES 7 2014-09-21 "Linux" "Linux Programmer's Manual"
+.SH NAME
+pid_namespaces \- overview of Linux PID namespaces
+.SH DESCRIPTION
+For an overview of namespaces, see
+.BR namespaces (7).
+
+PID namespaces isolate the process ID number space,
+meaning that processes in different PID namespaces can have the same PID.
+PID namespaces allow containers to provide functionality
+such as suspending/resuming the set of processes in the container and
+migrating the container to a new host
+while the processes inside the container maintain the same PIDs.
+
+PIDs in a new PID namespace start at 1,
+somewhat like a standalone system, and calls to
+.BR fork (2),
+.BR vfork (2),
+or
+.BR clone (2)
+will produce processes with PIDs that are unique within the namespace.
+
+Use of PID namespaces requires a kernel that is configured with the
+.B CONFIG_PID_NS
+option.
+.\"
+.\" ============================================================
+.\"
+.SS The namespace "init" process
+The first process created in a new namespace
+(i.e., the process created using
+.BR clone (2)
+with the
+.BR CLONE_NEWPID
+flag, or the first child created by a process after a call to
+.BR unshare (2)
+using the
+.BR CLONE_NEWPID
+flag) has the PID 1, and is the "init" process for the namespace (see
+.BR init (1)).
+A child process that is orphaned within the namespace will be reparented
+to this process rather than
+.BR init (1)
+(unless one of the ancestors of the child
+in the same PID namespace employed the
+.BR prctl (2)
+.B PR_GET_CHILD_SUBREAPER
+command to mark itself as the reaper of orphaned descendant processes).
+
+If the "init" process of a PID namespace terminates,
+the kernel terminates all of the processes in the namespace via a
+.BR SIGKILL
+signal.
+This behavior reflects the fact that the "init" process
+is essential for the correct operation of a PID namespace.
+In this case, a subsequent
+.BR fork (2)
+into this PID namespace will fail with the error
+.BR ENOMEM ;
+it is not possible to create a new processes in a PID namespace whose "init"
+process has terminated.
+Such scenarios can occur when, for example,
+a process uses an open file descriptor for a
+.I /proc/[pid]/ns/pid
+file corresponding to a process that was in a namespace to
+.BR setns (2)
+into that namespace after the "init" process has terminated.
+Another possible scenario can occur after a call to
+.BR unshare (2):
+if the first child subsequently created by a
+.BR fork (2)
+terminates, then subsequent calls to
+.BR fork (2)
+will fail with
+.BR ENOMEM .
+
+Only signals for which the "init" process has established a signal handler
+can be sent to the "init" process by other members of the PID namespace.
+This restriction applies even to privileged processes,
+and prevents other members of the PID namespace from
+accidentally killing the "init" process.
+
+Likewise, a process in an ancestor namespace
+can\(emsubject to the usual permission checks described in
+.BR kill (2)\(emsend
+signals to the "init" process of a child PID namespace only
+if the "init" process has established a handler for that signal.
+(Within the handler, the
+.I siginfo_t
+.I si_pid
+field described in
+.BR sigaction (2)
+will be zero.)
+.B SIGKILL
+or
+.B SIGSTOP
+are treated exceptionally:
+these signals are forcibly delivered when sent from an ancestor PID namespace.
+Neither of these signals can be caught by the "init" process,
+and so will result in the usual actions associated with those signals
+(respectively, terminating and stopping the process).
+
+Starting with Linux 3.4, the
+.BR reboot (2)
+system causes a signal to be sent to the namespace "init" process.
+See
+.BR reboot (2)
+for more details.
+.\"
+.\" ============================================================
+.\"
+.SS Nesting PID namespaces
+PID namespaces can be nested:
+each PID namespace has a parent,
+except for the initial ("root") PID namespace.
+The parent of a PID namespace is the PID namespace of the process that
+created the namespace using
+.BR clone (2)
+or
+.BR unshare (2).
+PID namespaces thus form a tree,
+with all namespaces ultimately tracing their ancestry to the root namespace.
+
+A process is visible to other processes in its PID namespace,
+and to the processes in each direct ancestor PID namespace
+going back to the root PID namespace.
+In this context, "visible" means that one process
+can be the target of operations by another process using
+system calls that specify a process ID.
+Conversely, the processes in a child PID namespace can't see
+processes in the parent and further removed ancestor namespace.
+More succinctly: a process can see (e.g., send signals with
+.BR kill (2),
+set nice values with
+.BR setpriority (2),
+etc.) only processes contained in its own PID namespace
+and in descendants of that namespace.
+
+A process has one process ID in each of the layers of the PID
+namespace hierarchy in which is visible,
+and walking back though each direct ancestor namespace
+through to the root PID namespace.
+System calls that operate on process IDs always
+operate using the process ID that is visible in the
+PID namespace of the caller.
+A call to
+.BR getpid (2)
+always returns the PID associated with the namespace in which
+the process was created.
+
+Some processes in a PID namespace may have parents
+that are outside of the namespace.
+For example, the parent of the initial process in the namespace
+(i.e., the
+.BR init (1)
+process with PID 1) is necessarily in another namespace.
+Likewise, the direct children of a process that uses
+.BR setns (2)
+to cause its children to join a PID namespace are in a different
+PID namespace from the caller of
+.BR setns (2).
+Calls to
+.BR getppid (2)
+for such processes return 0.
+.\"
+.\" ============================================================
+.\"
+.SS setns(2) and unshare(2) semantics
+Calls to
+.BR setns (2)
+that specify a PID namespace file descriptor
+and calls to
+.BR unshare (2)
+with the
+.BR CLONE_NEWPID
+flag cause children subsequently created
+by the caller to be placed in a different PID namespace from the caller.
+These calls do not, however,
+change the PID namespace of the calling process,
+because doing so would change the caller's idea of its own PID
+(as reported by
+.BR getpid ()),
+which would break many applications and libraries.
+
+To put things another way:
+a process's PID namespace membership is determined when the process is created
+and cannot be changed thereafter.
+Among other things, this means that the parental relationship
+between processes mirrors the parental relationship between PID namespaces:
+the parent of a process is either in the same namespace
+or resides in the immediate parent PID namespace.
+.SS Compatibility of CLONE_NEWPID with other CLONE_* flags
+.BR CLONE_NEWPID
+can't be combined with some other
+.BR CLONE_*
+flags:
+.IP * 3
+.B CLONE_THREAD
+requires being in the same PID namespace in order that that
+the threads in a process can send signals to each other.
+Similarly, it must be possible to see all of the threads
+of a processes in the
+.BR proc (5)
+filesystem.
+.IP *
+.BR CLONE_SIGHAND
+requires being in the same PID namespace;
+otherwise the process ID of the process sending a signal
+could not be meaningfully encoded when a signal is sent
+(see the description of the
+.I siginfo_t
+type in
+.BR sigaction (2)).
+A signal queue shared by processes in multiple PID namespaces
+will defeat that.
+.IP *
+.BR CLONE_VM
+requires all of the threads to be in the same PID namespace,
+because, from the point of view of a core dump,
+if two processes share the same address space they are threads and will
+be core dumped together.
+When a core dump is written, the PID of each
+thread is written into the core dump.
+Writing the process IDs could not meaningfully succeed
+if some of the process IDs were in a parent PID namespace.
+.PP
+To summarize: there is a technical requirement for each of
+.BR CLONE_THREAD ,
+.BR CLONE_SIGHAND ,
+and
+.BR CLONE_VM
+to share a PID namespace.
+(Note furthermore that in
+.BR clone (2)
+requires
+.BR CLONE_VM
+to be specified if
+.BR CLONE_THREAD
+or
+.BR CLONE_SIGHAND
+is specified.)
+Thus, call sequences such as the following will fail (with the error
+.BR EINVAL ):
+
+.nf
+ unshare(CLONE_NEWPID);
+ clone(..., CLONE_VM, ...); /* Fails */
+
+ setns(fd, CLONE_NEWPID);
+ clone(..., CLONE_VM, ...); /* Fails */
+
+ clone(..., CLONE_VM, ...);
+ setns(fd, CLONE_NEWPID); /* Fails */
+
+ clone(..., CLONE_VM, ...);
+ unshare(CLONE_NEWPID); /* Fails */
+.fi
+.\"
+.\" ============================================================
+.\"
+.SS /proc and PID namespaces
+A
+.I /proc
+filesystem shows (in the
+.I /proc/PID
+directories) only processes visible in the PID namespace
+of the process that performed the mount, even if the
+.I /proc
+filesystem is viewed from processes in other namespaces.
+
+After creating a new PID namespace,
+it is useful for the child to change its root directory
+and mount a new procfs instance at
+.I /proc
+so that tools such as
+.BR ps (1)
+work correctly.
+If a new mount namespace is simultaneously created by including
+.BR CLONE_NEWNS
+in the
+.IR flags
+argument of
+.BR clone (2)
+or
+.BR unshare (2),
+then it isn't necessary to change the root directory:
+a new procfs instance can be mounted directly over
+.IR /proc .
+
+From a shell, the command to mount
+.I /proc
+is:
+
+ $ mount -t proc proc /proc
+
+Calling
+.BR readlink (2)
+on the path
+.I /proc/self
+yields the process ID of the caller in the PID namespace of the procfs mount
+(i.e., the PID namespace of the process that mounted the procfs).
+This can be useful for introspection purposes,
+when a process wants to discover its PID in other namespaces.
+.\"
+.\" ============================================================
+.\"
+.SS Miscellaneous
+When a process ID is passed over a UNIX domain socket to a
+process in a different PID namespace (see the description of
+.B SCM_CREDENTIALS
+in
+.BR unix (7)),
+it is translated into the corresponding PID value in
+the receiving process's PID namespace.
+.SH CONFORMING TO
+Namespaces are a Linux-specific feature.
+.SH EXAMPLE
+See
+.BR user_namespaces (7).
+.SH SEE ALSO
+.BR clone (2),
+.BR setns (2),
+.BR unshare (2),
+.BR proc (5),
+.BR credentials (7),
+.BR capabilities (7),
+.BR user_namespaces (7),
+.BR switch_root (8)
+.SH COLOPHON
+This page is part of release 3.75 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.TH PIPE 7 2005-12-08 "Linux" "Linux Programmer's Manual"
+.TH PIPE 7 2014-07-08 "Linux" "Linux Programmer's Manual"
.SH NAME
pipe \- overview of pipes and FIFOs
.SH DESCRIPTION
In Linux versions before 2.6.11, the capacity of a pipe was the same as
the system page size (e.g., 4096 bytes on i386).
Since Linux 2.6.11, the pipe capacity is 65536 bytes.
+Since Linux 2.6.35, the default pipe capacity is 65536 bytes,
+but the capacity can be queried and set using the
+.BR fcntl (2)
+.BR F_GETPIPE_SZ
+and
+.BR F_SETPIPE_SZ
+operations.
+See
+.BR fcntl (2)
+for more information.
+
.SS PIPE_BUF
POSIX.1-2001 says that
.BR write (2)s
.BR epoll (7),
.BR fifo (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sysconf (3),
.BR standards (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
and
.BR pthread_testcancel (3)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR tty (4),
.BR tty_ioctl (4)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.I <linux/ip.h>
header file for the IP protocol.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.PP
POSIX.2, section 2.8 (Regular Expression Notation).
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
and can be used to modify subsequent auditing of, this PLT entry, as for
.BR la_symbind* ().
-.\" FIXME is the following correct?
+.\" FIXME . Is the following correct?
The
.IR framesizep
argument points to a
.B LD_AUDIT
results in a run-time crash.
This is reportedly fixed in glibc 2.10.
-.\" FIXME Specifying multiple audit libraries doesn't work on GNU.
+.\" FIXME . Specifying multiple audit libraries doesn't work on GNU.
.\" My simple tests on Solaris work okay, but not on Linux -- mtk, Jan 2009
.\" glibc bug filed: http://sourceware.org/bugzilla/show_bug.cgi?id=9733
.\" Reportedly, this is fixed on 16 Mar 2009 (i.e., for glibc 2.10)
.BR ld.so (8),
.BR ldconfig (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
It is based on netlink messages; see
.BR netlink (7)
for more information.
-.\" FIXME ? all these macros could be moved to rtnetlink(3)
+.\" FIXME . ? all these macros could be moved to rtnetlink(3)
.SS Routing attributes
Some rtnetlink messages have optional attributes after the initial header:
};
.fi
-.\" FIXME ifi_type
+.\" FIXME Document ifinfomsg.ifi_type
.I ifi_flags
contains the device flags, see
.BR netdevice (7);
IFA_ANYCAST:raw protocol address:anycast address
IFA_CACHEINFO:struct ifa_cacheinfo:Address information.
.TE
-.\" FIXME struct ifa_cacheinfo
+.\" FIXME Document struct ifa_cacheinfo
.TP
.BR RTM_NEWROUTE ", " RTM_DELROUTE ", " RTM_GETROUTE
Create, remove or receive information about a network route.
NTF_ROUTER:an IPv6 router
.TE
-.\" FIXME
+.\" FIXME .
.\" document the members of the struct better
The
.I rtattr
.BR ip (7),
.BR netlink (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\" Worth looking at: http://rt.wiki.kernel.org/index.php
.\"
-.TH SCHED 7 2014-05-13 "Linux" "Linux Programmer's Manual"
+.TH SCHED 7 2014-10-02 "Linux" "Linux Programmer's Manual"
.SH NAME
sched \- overview of scheduling APIs
.SH DESCRIPTION
.BR sched_setattr (2).
These fields express value in nanoseconds.
.\" FIXME It looks as though specifying sched_period as 0 means
-.\" "make sched_period the same as sched_deadline", right?
+.\" "make sched_period the same as sched_deadline".
.\" This needs to be documented.
If
.IR sched_period
.\" fails with EINVAL, but sched_getscheduler() succeeds.
.\" Is that intended? (Why?)
.\"
-.\"
.SS SCHED_OTHER: Default Linux time-sharing scheduling
\fBSCHED_OTHER\fP can be used at only static priority 0.
\fBSCHED_OTHER\fP is the standard Linux time-sharing scheduler that is
will cause the scheduler to always assume
that the thread is CPU-intensive.
Consequently, the scheduler will apply a small scheduling
-penalty with respect to wakeup behaviour,
+penalty with respect to wakeup behavior,
so that this thread is mildly disfavored in scheduling decisions.
.\" The following paragraph is drawn largely from the text that
.ad l
.nh
.BR chrt (1),
+.BR taskset (1),
.BR getpriority (2),
.BR mlock (2),
.BR mlockall (2),
and
.IR Documentation/scheduler/sched-nice-design.txt
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR sem_wait (3),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR shm_unlink (3),
.BR sem_overview (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR aio (7),
.BR pthreads (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Added section on stop/cont signals interrupting syscalls.
.\" 2008-10-05, mtk: various additions
.\"
-.TH SIGNAL 7 2013-07-30 "Linux" "Linux Programmer's Manual"
+.TH SIGNAL 7 2014-10-15 "Linux" "Linux Programmer's Manual"
.SH NAME
signal \- overview of signals
.SH DESCRIPTION
.BR connect (2),
.BR recv (2),
.BR recvfrom (2),
+.BR recvmmsg (2),
.BR recvmsg (2),
.BR send (2),
.BR sendto (2),
and
+.\" FIXME . What about sendmmsg()?
.BR sendmsg (2),
unless a timeout has been set on the socket (see below).
.IP *
(since Linux 2.6.22; beforehand, always failed with
.BR EINTR ).
.IP *
+.BR pthread_mutex_lock (3),
+.BR pthread_cond_wait (3),
+and related APIs.
+.IP *
POSIX semaphore interfaces:
.BR sem_wait (3)
and
.\" on interruption by a signal handler.
.RS 4
.IP * 2
-Socket interfaces, when a timeout has been set on the socket using
+"Input" socket interfaces, when a timeout
+.RB ( SO_RCVTIMEO )
+has been set on the socket using
.BR setsockopt (2):
.BR accept (2),
.BR recv (2),
.BR recvfrom (2),
+.BR recvmmsg (2)
+(also with a non-NULL
+.IR timeout
+argument),
and
-.BR recvmsg (2),
-if a receive timeout
+.BR recvmsg (2).
+.IP *
+"Output" socket interfaces, when a timeout
.RB ( SO_RCVTIMEO )
-has been set;
+has been set on the socket using
+.BR setsockopt (2):
.BR connect (2),
.BR send (2),
.BR sendto (2),
and
-.BR sendmsg (2),
-if a send timeout
-.RB ( SO_SNDTIMEO )
-has been set.
+.\" FIXME . What about sendmmsg()?
+.BR sendmsg (2).
.IP *
Interfaces used to wait for signals:
.BR pause (2),
The Linux interfaces that display this behavior are:
.RS 4
.IP * 2
-Socket interfaces, when a timeout has been set on the socket using
+"Input" socket interfaces, when a timeout
+.RB ( SO_RCVTIMEO )
+has been set on the socket using
.BR setsockopt (2):
.BR accept (2),
.BR recv (2),
.BR recvfrom (2),
+.BR recvmmsg (2)
+(also with a non-NULL
+.IR timeout
+argument),
and
-.BR recvmsg (2),
-if a receive timeout
+.BR recvmsg (2).
+.IP *
+"Output" socket interfaces, when a timeout
.RB ( SO_RCVTIMEO )
-has been set;
+has been set on the socket using
+.BR setsockopt (2):
.BR connect (2),
.BR send (2),
.BR sendto (2),
and
+.\" FIXME . What about sendmmsg()?
.BR sendmsg (2),
if a send timeout
.RB ( SO_SNDTIMEO )
.BR pthreads (7),
.BR sigevent (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" Author: Keller, Jacob E <jacob.e.keller@intel.com>
.\" SO_MAX_PACING_RATE (3.13)
.\" commit 62748f32d501f5d3712a7c372bbb92abc7c62bc7
+.\" SO_BPF_EXTENSIONS (3.14)
+.\" commit ea02f9411d9faa3553ed09ce0ec9f00ceae9885e
.\"
-.TH SOCKET 7 2014-02-21 Linux "Linux Programmer's Manual"
+.TH SOCKET 7 2014-07-08 Linux "Linux Programmer's Manual"
.SH NAME
socket \- Linux socket interface
.SH SYNOPSIS
.I optval
is a pointer to an
.IR int .
-.\" FIXME
+.\" FIXME .
.\" In the list below, the text used to describe argument types
.\" for each socket option should be more consistent
.\"
and this doubled value is returned by
.BR getsockopt (2).
.\" The following thread on LMKL is quite informative:
-.\" getsockopt/setsockopt with SO_RCVBUF and SO_SNDBUF "non-standard" behaviour
+.\" getsockopt/setsockopt with SO_RCVBUF and SO_SNDBUF "non-standard" behavior
.\" 17 July 2012
.\" http://thread.gmane.org/gmane.linux.kernel/1328935
The default value is set by the
.BR udp (7),
.BR unix (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.I The Cell Broadband Engine Architecture (CBEA) specification
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR libc (7),
.BR posixoptions (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR file (1),
.BR make (1)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
-.\" FIXME There is now duplication of some of the information
+.\" FIXME . There is now duplication of some of the information
.\" below in semctl.2, msgctl.2, and shmctl.2 -- MTK, Nov 04
.\"
-.\" FIXME Ultimately, there should probably be
+.\" FIXME . Ultimately, there should probably be
.\" svmq_overview(7), svshm_overview(7), and sem_overview(7)
.\" that provide an overview of each System V IPC mechanism.
.\" In that case:
.\" * The only part that uniquely belongs in svipc(7) is perphaps
.\" the discussion of ipc_perm.
.\"
-.TH SVIPC 7 2013-02-12 "Linux" "Linux Programmer's Manual"
+.TH SVIPC 7 2014-09-21 "Linux" "Linux Programmer's Manual"
.SH NAME
svipc \- System V interprocess communication mechanisms
.SH SYNOPSIS
.BR shmctl (2)
system call that changed
.IR shmid_ds .
+.SS IPC namespaces
+For a discussion of the interaction of System V IPC objects and
+IPC namespaces, see
+.BR namespaces (7).
.SH SEE ALSO
.BR ipcmk (1),
.BR ipcrm (1),
.BR shmctl (2),
.BR shmdt (2),
.BR shmget (2),
-.BR ftok (3)
+.BR ftok (3),
+.BR namespaces (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR lutimes (3),
.BR path_resolution (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.B SIOCOUTQ
is defined in
.IR <linux/sockios.h> .
-.\" FIXME http://sources.redhat.com/bugzilla/show_bug.cgi?id=12002,
+.\" FIXME . http://sources.redhat.com/bugzilla/show_bug.cgi?id=12002,
.\" filed 2010-09-10, may cause SIOCOUTQ to be defined in glibc headers
Alternatively,
you can use the synonymous
.br
RFC\ 2018 and RFC\ 2883 for SACK and extensions to SACK.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR tty (4),
.BR tty_ioctl (4)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR rtc (4),
.BR hwclock (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.br
RFC\ 1191 for a description of path MTU discovery.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\"
.\" $Id: udplite.7,v 1.12 2008/07/23 15:22:22 gerrit Exp gerrit $
.\"
-.TH UDPLITE 7 2008-12-03 "Linux" "Linux Programmer's Manual"
+.TH UDPLITE 7 2014-07-08 "Linux" "Linux Programmer's Manual"
.SH NAME
udplite \- Lightweight User Datagram Protocol
.SH SYNOPSIS
The UDP-Lite implementation is a full extension of
.BR udp (7)\(emthat
-is, it shares the same API and API behaviour, and in addition
+is, it shares the same API and API behavior, and in addition
offers two socket options to control the checksum coverage.
.SS Address format
UDP-Litev4 uses the
.I Documentation/networking/udplite.txt
in the Linux kernel source tree
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" 2001-05-11 Markus Kuhn <mgk25@cl.cam.ac.uk>
.\" Update
.\"
-.TH UNICODE 7 2012-08-05 "GNU" "Linux Programmer's Manual"
+.TH UNICODE 7 2014-06-13 "GNU" "Linux Programmer's Manual"
.SH NAME
Unicode \- universal character set
.SH DESCRIPTION
-The international standard
-.B ISO 10646
-defines the
-.BR "Universal Character Set (UCS)" .
+The international standard ISO 10646 defines the
+Universal Character Set (UCS).
UCS contains all characters of all other character set standards.
-It also guarantees
-.BR "round-trip compatibility";
+It also guarantees "round-trip compatibility";
in other words,
conversion tables can be built such that no information is lost
when a string is converted from any other encoding to UCS and back.
systems, and more are being added.
The UCS standard (ISO 10646) describes a
-.I "31-bit character set architecture"
+31-bit character set architecture
consisting of 128 24-bit
.IR groups ,
each divided into 256 16-bit
with 256
.I column
positions, one for each character.
-Part 1 of the standard
-.RB ( "ISO 10646-1" )
+Part 1 of the standard (ISO 10646-1)
defines the first 65534 code positions (0x0000 to 0xfffd), which form
the
-.IR "Basic Multilingual Plane (BMP)" ,
-that is plane 0 in group 0.
-Part 2 of the standard
-.RB ( "ISO 10646-2" )
+.IR "Basic Multilingual Plane"
+(BMP), that is plane 0 in group 0.
+Part 2 of the standard (ISO 10646-2)
adds characters to group 0 outside the BMP in several
.I "supplementary planes"
in the range 0x10000 to 0x10ffff.
enthusiast needs.
.PP
The representation of each UCS character as a 2-byte word is referred
-to as the
-.B UCS-2
-form (only for BMP characters), whereas
-.B UCS-4
-is the representation of each character by a 4-byte word.
-In addition, there exist two encoding forms
-.B UTF-8
-for backward compatibility with ASCII processing software and
-.B UTF-16
+to as the UCS-2 form (only for BMP characters),
+whereas UCS-4 is the representation of each character by a 4-byte word.
+In addition, there exist two encoding forms UTF-8
+for backward compatibility with ASCII processing software and UTF-16
for the backward-compatible handling of non-BMP characters up to
0x10ffff by UCS-2 software.
.PP
The UCS characters 0x0000 to 0x007f are identical to those of the
-classic
-.B US-ASCII
+classic US-ASCII
character set and the characters in the range 0x0000 to 0x00ff
are identical to those in
-.BR "ISO 8859-1 Latin-1" .
+ISO 8859-1 (Latin-1).
.SS Combining characters
-Some code points in
-.B UCS
+Some code points in UCS
have been assigned to
.IR "combining characters" .
These are similar to the nonspacing accent keys on a typewriter.
of UCS:
.TP 0.9i
Level 1
-Combining characters and
-.B Hangul Jamo
+Combining characters and Hangul Jamo
(a variant encoding of the Korean script, where a Hangul syllable
glyph is coded as a triplet or pair of vovel/consonant codes) are not
supported.
Arabic, Devanagari, Malayalam).
.TP
Level 3
-All
-.B UCS
-characters are supported.
+All UCS characters are supported.
.PP
-The
-.B Unicode 3.0 Standard
-published by the
-.B Unicode Consortium
-contains exactly the
-.B UCS Basic Multilingual Plane
+The Unicode 3.0 Standard
+published by the Unicode Consortium
+contains exactly the UCS Basic Multilingual Plane
at implementation level 3, as described in ISO 10646-1:2000.
-.B Unicode 3.1
-added the supplemental planes of ISO 10646-2.
+Unicode 3.1 added the supplemental planes of ISO 10646-2.
The Unicode standard and
technical reports published by the Unicode Consortium provide much
additional information on the semantics and recommended usages of
.I wchar_t
is a signed 32-bit integer type.
Its values are always interpreted
-by the C library as
-.B UCS
+by the C library as UCS
code values (in all locales), a convention that is signaled by the GNU
C library to applications by defining the constant
.B __STDC_ISO_10646__
UCS/Unicode can be used just like ASCII in input/output streams,
terminal communication, plaintext files, filenames, and environment
-variables in the ASCII compatible
-.B UTF-8
-multibyte encoding.
+variables in the ASCII compatible UTF-8 multibyte encoding.
To signal the use of UTF-8 as the character
encoding to all applications, a suitable
.I locale
tells, how many positions (0\(en2) the cursor is advanced by the
output of a character.
.PP
-Under Linux, in general only the BMP at implementation level 1 should
-be used at the moment.
-Up to two combining characters per base
-character for certain scripts (in particular Thai) are also supported
-by some UTF-8 terminal emulators and ISO 10646 fonts (level 2), but in
-general precomposed characters should be preferred where available
-(Unicode calls this
-.BR "Normalization Form C" ).
.SS Private area
-In the
-.BR BMP ,
+In the Basic Multilingual Plane,
the range 0xe000 to 0xf8ff will never be assigned to any characters by
the standard and is reserved for private usage.
For the Linux
and the Linux zone in the range 0xf000 to 0xf8ff where extensions are
coordinated among all Linux users.
The registry of the characters
-assigned to the Linux zone is currently maintained by H. Peter Anvin
-<Peter.Anvin@linux.org>.
+assigned to the Linux zone is maintained by LANANA and the registry
+itself is
+.I Documentation/unicode.txt
+in the Linux kernel sources.
.SS Literature
-.TP 0.2i
-*
+.IP * 3
Information technology \(em Universal Multiple-Octet Coded Character
Set (UCS) \(em Part 1: Architecture and Basic Multilingual Plane.
International Standard ISO/IEC 10646-1, International Organization
for Standardization, Geneva, 2000.
-This is the official specification of
-.BR UCS .
-Available as a PDF file on CD-ROM from
+This is the official specification of UCS .
+Available from
.UR http://www.iso.ch/
.UE .
-.TP
-*
+.IP *
The Unicode Standard, Version 3.0.
The Unicode Consortium, Addison-Wesley,
Reading, MA, 2000, ISBN 0-201-61633-5.
-.TP
-*
+.IP *
S. Harbison, G. Steele. C: A Reference Manual. Fourth edition,
Prentice Hall, Englewood Cliffs, 1995, ISBN 0-13-326224-3.
adds a large number of new C library functions for handling wide and
multibyte character encodings, but it does not yet cover ISO C99,
which improved wide and multibyte character support even further.
-.TP
-*
+.IP *
Unicode Technical Reports.
.RS
-.UR http://www.unicode.org\:/unicode\:/reports/
+.UR http://www.unicode.org\:/reports/
.UE
.RE
-.TP
-*
+.IP *
Markus Kuhn: UTF-8 and Unicode FAQ for UNIX/Linux.
.RS
.UR http://www.cl.cam.ac.uk\:/~mgk25\:/unicode.html
.UE
-
-Provides subscription information for the
-.I linux-utf8
-mailing list, which is the best place to look for advice on using
-Unicode under Linux.
.RE
-.TP
-*
+.IP *
Bruno Haible: Unicode HOWTO.
.RS
-.UR ftp://ftp.ilog.fr\:/pub\:/Users\:/haible\:/utf8\:/Unicode-HOWTO.html
+.UR http://www.tldp.org\:/HOWTO\:/Unicode-HOWTO.html
.UE
.RE
-.SH BUGS
-When this man page was last revised, the GNU C Library support for
-.B UTF-8
-locales was mature and XFree86 support was in an advanced state, but
-work on making applications (most notably editors) suitable for use in
-.B UTF-8
-locales was still fully in progress.
-Current general
-.B UCS
-support under Linux usually provides for CJK double-width characters
-and sometimes even simple overstriking combining characters, but
-usually does not include support for scripts with right-to-left
-writing direction or ligature substitution requirements such as
-Hebrew, Arabic, or the Indic scripts.
-These scripts are currently
-supported only in certain GUI applications (HTML viewers, word processors)
-with sophisticated text rendering engines.
.\" .SH AUTHOR
.\" Markus Kuhn <mgk25@cl.cam.ac.uk>
.SH SEE ALSO
+.BR locale (1),
.BR setlocale (3),
.BR charsets (7),
.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
the MB are megabytes and the KiB are kibibytes.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" This man page is Copyright (C) 1999 Andi Kleen <ak@muc.de>.
+.\" and Copyright (C) 2008-2014, Michael Kerrisk <mtk.manpages@gmail.com>
.\"
.\" %%%LICENSE_START(VERBATIM_ONE_PARA)
+.\" and Copyright (C) 2008, 2012 Michael Kerrisk <mtk.manpages@gmail.com>
.\" Permission is granted to distribute possibly modified copies
.\" of this page provided the header is included verbatim,
.\" and in case of nontrivial modification author and date
.\" address that can appear in the sockaddr_un structure: pathname,
.\" unnamed, and abstract.
.\"
-.TH UNIX 7 2012-05-10 "Linux" "Linux Programmer's Manual"
+.TH UNIX 7 2014-10-15 "Linux" "Linux Programmer's Manual"
.SH NAME
unix \- sockets for local interprocess communication
.SH SYNOPSIS
Linux also supports an abstract namespace which is independent of the
filesystem.
-Valid types are:
+Valid socket types in the UNIX domain are:
.BR SOCK_STREAM ,
-for a stream-oriented socket and
+for a stream-oriented socket;
.BR SOCK_DGRAM ,
for a datagram-oriented socket that preserves message boundaries
(as on most UNIX implementations, UNIX domain datagram
.fi
.in
.PP
+The
.I sun_family
-always contains
+field always contains
.BR AF_UNIX .
-Three types of address are distinguished in this structure:
+Various systems calls (for example,
+.BR bind (2),
+.BR connect (2),
+and
+.BR sendto (2))
+take a
+.I sockaddr_un
+argument as input.
+Some other system calls (for example,
+.BR getsockname (2),
+.BR getpeername (2),
+.BR recvfrom (2),
+and
+.BR accept (2))
+return an argument of this type.
+
+Three types of address are distinguished in the
+.I sockaddr_un
+structure:
.IP * 3
.IR pathname :
a UNIX domain socket can be bound to a null-terminated
filesystem pathname using
.BR bind (2).
-When the address of the socket is returned by
-.BR getsockname (2),
-.BR getpeername (2),
-and
-.BR accept (2),
+When the address of a pathname socket is returned
+(by one of the system calls noted above),
its length is
offsetof(struct sockaddr_un, sun_path) + strlen(sun_path) + 1
and
.I sun_path
contains the null-terminated pathname.
+(On Linux, the above
+.BR offsetof ()
+expression equates to the same value as
+.IR sizeof(sa_family_t) ,
+but some other implementations include other fields before
+.IR sun_path ,
+so the
+.BR offsetof ()
+expression more portably describes the size of the address structure.)
+.IP
+For further details of pathname sockets, see below.
.IP *
.IR unnamed :
A stream socket that has not been bound to a pathname using
Likewise, the two sockets created by
.BR socketpair (2)
are unnamed.
-When the address of an unnamed socket is returned by
-.BR getsockname (2),
-.BR getpeername (2),
-and
-.BR accept (2),
+When the address of an unnamed socket is returned,
its length is
.IR "sizeof(sa_family_t)" ,
and
.\" says the length is 16 bytes, HP-UX 11 says it's zero bytes.
.IP *
.IR abstract :
-an abstract socket address is distinguished by the fact that
+an abstract socket address is distinguished (from a pathname socket)
+by the fact that
.IR sun_path[0]
is a null byte (\(aq\\0\(aq).
The socket's address in this namespace is given by the additional
that are covered by the specified length of the address structure.
(Null bytes in the name have no special significance.)
The name has no connection with filesystem pathnames.
-When the address of an abstract socket is returned by
-.BR getsockname (2),
-.BR getpeername (2),
-and
-.BR accept (2),
+When the address of an abstract socket is returned,
the returned
.I addrlen
is greater than
bytes of
.IR sun_path .
The abstract socket namespace is a nonportable Linux extension.
+.SS Pathname sockets
+When binding a socket to a pathname, a few rules should be observed
+for maximum portability and ease of coding:
+.IP * 3
+The pathname in
+.I sun_path
+should be null-terminated.
+.IP *
+The length of the pathname, including the terminating null byte,
+should not exceed the size of
+.IR sun_path .
+.IP *
+The
+.I addrlen
+argument that describes the enclosing
+.I sockaddr_un
+structure should have a value of at least:
+
+.nf
+ offsetof(struct sockaddr_un, sun_path)+strlen(addr.sun_path)+1
+.fi
+.IP
+or, more simply,
+.I addrlen
+can be specified as
+.IR "sizeof(struct sockaddr_un)" .
+.PP
+There is some variation in how implementations handle UNIX domain
+socket addresses that do not follow the above rules.
+For example, some (but not all) implementations
+.\" Linux does this, including for the case where the supplied path
+.\" is 108 bytes
+append a null terminator if none is present in the supplied
+.IR sun_path .
+
+When coding portable applications,
+keep in mind that some implementations
+.\" HP-UX
+have
+.I sun_path
+as short as 92 bytes.
+.\" Modern BSDs generally have 104, Tru64 and AIX have 104,
+.\" Solaris and Irix have 108
+
+Various system calls
+.RB ( accept (2),
+.BR recvfrom (2),
+.BR getsockname (2),
+.BR getpeername (2))
+return socket address structures.
+When applied to UNIX domain sockets, the value-result
+.I addrlen
+argument supplied to the call should be initialized as above.
+Upon return, the argument is set to indicate the
+.I actual
+size of the address structure.
+The caller should check the value returned in this argument:
+if the output value exceeds the input value,
+then there is no guarantee that a null terminator is present in
+.IR sun_path .
+(See BUGS.)
.SS Socket options
For historical reasons these socket options are specified with a
.B SOL_SOCKET
.B SIOCINQ
is defined in
.IR <linux/sockios.h> .
-.\" FIXME http://sources.redhat.com/bugzilla/show_bug.cgi?id=12002,
+.\" FIXME . http://sources.redhat.com/bugzilla/show_bug.cgi?id=12002,
.\" filed 2010-09-10, may cause SIOCINQ to be defined in glibc headers
Alternatively,
you can use the synonymous
The remote address specified by
.BR connect (2)
was not a listening socket.
-This error can also occur if the target filename is not a socket.
+This error can also occur if the target pathname is not a socket.
.TP
.B ECONNRESET
Remote socket was unexpectedly closed.
.SH NOTES
In the Linux implementation, sockets which are visible in the
filesystem honor the permissions of the directory they are in.
-Their owner, group and their permissions can be changed.
+Their owner, group, and permissions can be changed.
Creation of a new socket will fail if the process does not have write and
search (execute) permission on the directory the socket is created in.
Connecting to the socket object requires read/write permission.
call.
UNIX domain stream sockets do not support the notion of out-of-band data.
+.\"
+.SH BUGS
+When binding a socket to an address,
+Linux is one of the implementations that appends a null terminator
+if none is supplied in
+.IR sun_path .
+In most cases this is unproblematic:
+when the socket address is retrieved,
+it will be one byte longer than that supplied when the socket was bound.
+However, there is one case where confusing behavior can result:
+if 108 non-null bytes are supplied when a socket is bound,
+then the addition of the null terminator takes the length of
+the pathname beyond
+.IR sizeof(sun_path) .
+Consequently, when retrieving the socket address
+(for example, via
+.BR accept (2)),
+.\" The behavior on Solaris is quite similar.
+if the input
+.I addrlen
+argument for the retrieving call is specified as
+.IR "sizeof(struct sockaddr_un)" ,
+then the returned address structure
+.I won't
+have a null terminator in
+.IR sun_path .
+
+In addition, some implementations
+.\" i.e., traditional BSD
+don't require a null terminator when binding a socket (the
+.I addrlen
+argument is used to determine the length of
+.IR sun_path )
+and when the socket address is retrieved on these implementations,
+there is no null terminator in
+.IR sun_path .
+
+Applications that retrieve socket addresses can (portably) code
+to handle the possibility that there is no null terminator in
+.IR sun_path
+by respecting the fact that the number of valid bytes in the pathname is:
+
+ strnlen(addr.sun_path, addrlen \- offsetof(sockaddr_un, sun_path))
+.\" The following patch to amend kernel behavior was rejected:
+.\" http://thread.gmane.org/gmane.linux.kernel.api/2437
+.\" Subject: [patch] Fix handling of overlength pathname in AF_UNIX sun_path
+.\" 2012-04-17
+.\" And there was a related discussion in the Austin list:
+.\" http://thread.gmane.org/gmane.comp.standards.posix.austin.general/5735
+.\" Subject: Having a sun_path with no null terminator
+.\" 2012-04-18
+.\"
+.\" FIXME . Track http://austingroupbugs.net/view.php?id=561
+
+Alternatively, an application can retrieve
+the socket address by allocating a buffer of size
+.I "sizeof(struct sockaddr_un)+1"
+that is zeroed out before the retrieval.
+The retrieving call can specify
+.I addrlen
+as
+.IR "sizeof(struct sockaddr_un)" ,
+and the extra zero byte ensures that there will be
+a null terminator for the string returned in
+.IR sun_path :
+
+.nf
+.in +3
+void *addrp;
+
+addrlen = sizeof(struct sockaddr_un);
+addrp = malloc(addrlen + 1);
+if (addrp == NULL)
+ /* Handle error */ ;
+memset(addrp, 0, addrlen + 1);
+
+if (getsockname(sfd, (struct sockaddr *) addrp, &addrlen)) != \-1)
+ /* handle error */ ;
+
+printf("sun_path = %s\\n", ((struct sockaddr_un *) addrp)\->sun_path);
+.in
+.fi
+
+This sort of messiness can be avoided if it is guaranteed
+that the applications that
+.I create
+pathname sockets follow the rules outlined above under
+.IR "Pathname sockets" .
.SH EXAMPLE
See
.BR bind (2).
.BR credentials (7),
.BR socket (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
IETF RFC\ 2255
.UE
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
--- /dev/null
+.\" Copyright (c) 2013, 2014 by Michael Kerrisk <mtk.manpages@gmail.com>
+.\" and Copyright (c) 2012, 2014 by Eric W. Biederman <ebiederm@xmission.com>
+.\"
+.\" %%%LICENSE_START(VERBATIM)
+.\" Permission is granted to make and distribute verbatim copies of this
+.\" manual provided the copyright notice and this permission notice are
+.\" preserved on all copies.
+.\"
+.\" Permission is granted to copy and distribute modified versions of this
+.\" manual under the conditions for verbatim copying, provided that the
+.\" entire resulting derived work is distributed under the terms of a
+.\" permission notice identical to this one.
+.\"
+.\" Since the Linux kernel and libraries are constantly changing, this
+.\" manual page may be incorrect or out-of-date. The author(s) assume no
+.\" responsibility for errors or omissions, or for damages resulting from
+.\" the use of the information contained herein. The author(s) may not
+.\" have taken the same level of care in the production of this manual,
+.\" which is licensed free of charge, as they might when working
+.\" professionally.
+.\"
+.\" Formatted or processed versions of this manual, if unaccompanied by
+.\" the source, must acknowledge the copyright and authors of this work.
+.\" %%%LICENSE_END
+.\"
+.\"
+.TH USER_NAMESPACES 7 2014-09-21 "Linux" "Linux Programmer's Manual"
+.SH NAME
+user_namespaces \- overview of Linux user_namespaces
+.SH DESCRIPTION
+For an overview of namespaces, see
+.BR namespaces (7).
+
+User namespaces isolate security-related identifiers and attributes,
+in particular,
+user IDs and group IDs (see
+.BR credentials (7),
+the root directory,
+keys (see
+.BR keyctl (2)),
+.\" FIXME: This page says very little about the interaction
+.\" of user namespaces and keys. Add something on this topic.
+and capabilities (see
+.BR capabilities (7)).
+A process's user and group IDs can be different
+inside and outside a user namespace.
+In particular,
+a process can have a normal unprivileged user ID outside a user namespace
+while at the same time having a user ID of 0 inside the namespace;
+in other words,
+the process has full privileges for operations inside the user namespace,
+but is unprivileged for operations outside the namespace.
+.\"
+.\" ============================================================
+.\"
+.SS Nested namespaces, namespace membership
+User namespaces can be nested;
+that is, each user namespace\(emexcept the initial ("root")
+namespace\(emhas a parent user namespace,
+and can have zero or more child user namespaces.
+The parent user namespace is the user namespace
+of the process that creates the user namespace via a call to
+.BR unshare (2)
+or
+.BR clone (2)
+with the
+.BR CLONE_NEWUSER
+flag.
+
+The kernel imposes (since version 3.11) a limit of 32 nested levels of
+.\" commit 8742f229b635bf1c1c84a3dfe5e47c814c20b5c8
+user namespaces.
+.\" FIXME Explain the rationale for this limit. (What is the rationale?)
+Calls to
+.BR unshare (2)
+or
+.BR clone (2)
+that would cause this limit to be exceeded fail with the error
+.BR EUSERS .
+
+Each process is a member of exactly one user namespace.
+A process created via
+.BR fork (2)
+or
+.BR clone (2)
+without the
+.BR CLONE_NEWUSER
+flag is a member of the same user namespace as its parent.
+A single-threaded process can join another user namespace with
+.BR setns (2)
+if it has the
+.BR CAP_SYS_ADMIN
+in that namespace;
+upon doing so, it gains a full set of capabilities in that namespace.
+
+A call to
+.BR clone (2)
+or
+.BR unshare (2)
+with the
+.BR CLONE_NEWUSER
+flag makes the new child process (for
+.BR clone (2))
+or the caller (for
+.BR unshare (2))
+a member of the new user namespace created by the call.
+.\"
+.\" ============================================================
+.\"
+.SS Capabilities
+The child process created by
+.BR clone (2)
+with the
+.BR CLONE_NEWUSER
+flag starts out with a complete set
+of capabilities in the new user namespace.
+Likewise, a process that creates a new user namespace using
+.BR unshare (2)
+or joins an existing user namespace using
+.BR setns (2)
+gains a full set of capabilities in that namespace.
+On the other hand,
+that process has no capabilities in the parent (in the case of
+.BR clone (2))
+or previous (in the case of
+.BR unshare (2)
+and
+.BR setns (2))
+user namespace,
+even if the new namespace is created or joined by the root user
+(i.e., a process with user ID 0 in the root namespace).
+
+Note that a call to
+.BR execve (2)
+will cause a process's capabilities to be recalculated in the usual way (see
+.BR capabilities (7)),
+so that usually,
+unless it has a user ID of 0 within the namespace or the executable file
+has a nonempty inheritable capabilities mask,
+it will lose all capabilities.
+See the discussion of user and group ID mappings, below.
+
+A call to
+.BR clone (2),
+.BR unshare (2),
+or
+.BR setns (2)
+using the
+.BR CLONE_NEWUSER
+flag sets the "securebits" flags
+(see
+.BR capabilities (7))
+to their default values (all flags disabled) in the child (for
+.BR clone (2))
+or caller (for
+.BR unshare (2),
+or
+.BR setns (2)).
+Note that because the caller no longer has capabilities
+in its original user namespace after a call to
+.BR setns (2),
+it is not possible for a process to reset its "securebits" flags while
+retaining its user namespace membership by using a pair of
+.BR setns (2)
+calls to move to another user namespace and then return to
+its original user namespace.
+
+Having a capability inside a user namespace
+permits a process to perform operations (that require privilege)
+only on resources governed by that namespace.
+The rules for determining whether or not a process has a capability
+in a particular user namespace are as follows:
+.IP 1. 3
+A process has a capability inside a user namespace
+if it is a member of that namespace and
+it has the capability in its effective capability set.
+A process can gain capabilities in its effective capability
+set in various ways.
+For example, it may execute a set-user-ID program or an
+executable with associated file capabilities.
+In addition,
+a process may gain capabilities via the effect of
+.BR clone (2),
+.BR unshare (2),
+or
+.BR setns (2),
+as already described.
+.\" In the 3.8 sources, see security/commoncap.c::cap_capable():
+.IP 2.
+If a process has a capability in a user namespace,
+then it has that capability in all child (and further removed descendant)
+namespaces as well.
+.IP 3.
+.\" * The owner of the user namespace in the parent of the
+.\" * user namespace has all caps.
+When a user namespace is created, the kernel records the effective
+user ID of the creating process as being the "owner" of the namespace.
+.\" (and likewise associates the effective group ID of the creating process
+.\" with the namespace).
+A process that resides
+in the parent of the user namespace
+.\" See kernel commit 520d9eabce18edfef76a60b7b839d54facafe1f9 for a fix
+.\" on this point
+and whose effective user ID matches the owner of the namespace
+has all capabilities in the namespace.
+.\" This includes the case where the process executes a set-user-ID
+.\" program that confers the effective UID of the creator of the namespace.
+By virtue of the previous rule,
+this means that the process has all capabilities in all
+further removed descendant user namespaces as well.
+.\"
+.\" ============================================================
+.\"
+.SS Interaction of user namespaces and other types of namespaces
+Starting in Linux 3.8, unprivileged processes can create user namespaces,
+and mount, PID, IPC, network, and UTS namespaces can be created with just the
+.B CAP_SYS_ADMIN
+capability in the caller's user namespace.
+
+When a non-user-namespace is created,
+it is owned by the user namespace in which the creating process
+was a member at the time of the creation of the namespace.
+Actions on the non-user-namespace
+require capabilities in the corresponding user namespace.
+
+If
+.BR CLONE_NEWUSER
+is specified along with other
+.B CLONE_NEW*
+flags in a single
+.BR clone (2)
+or
+.BR unshare (2)
+call, the user namespace is guaranteed to be created first,
+giving the child
+.RB ( clone (2))
+or caller
+.RB ( unshare (2))
+privileges over the remaining namespaces created by the call.
+Thus, it is possible for an unprivileged caller to specify this combination
+of flags.
+
+When a new IPC, mount, network, PID, or UTS namespace is created via
+.BR clone (2)
+or
+.BR unshare (2),
+the kernel records the user namespace of the creating process against
+the new namespace.
+(This association can't be changed.)
+When a process in the new namespace subsequently performs
+privileged operations that operate on global
+resources isolated by the namespace,
+the permission checks are performed according to the process's capabilities
+in the user namespace that the kernel associated with the new namespace.
+.\"
+.\" ============================================================
+.\"
+.SS Restrictions on mount namespaces
+
+Note the following points with respect to mount namespaces:
+.IP * 3
+A mount namespace has an owner user namespace.
+A mount namespace whose owner user namespace is different from
+the owner user namespace of its parent mount namespace is
+considered a less privileged mount namespace.
+.IP *
+When creating a less privileged mount namespace,
+shared mounts are reduced to slave mounts.
+This ensures that mappings performed in less
+privileged mount namespaces will not propagate to more privileged
+mount namespaces.
+.IP *
+.\" FIXME .
+.\" What does "come as a single unit from more privileged mount" mean?
+Mounts that come as a single unit from more privileged mount are
+locked together and may not be separated in a less privileged mount
+namespace.
+(The
+.BR unshare (2)
+.B CLONE_NEWNS
+operation brings across all of the mounts from the original
+mount namespace as a single unit,
+and recursive mounts that propagate between
+mount namespaces propagate as a single unit.)
+.IP *
+The
+.BR mount (2)
+flags
+.BR MS_RDONLY ,
+.BR MS_NOSUID ,
+.BR MS_NOEXEC ,
+and the "atime" flags
+.RB ( MS_NOATIME ,
+.BR MS_NODIRATIME ,
+.BR MS_RELATIME)
+settings become locked
+.\" commit 9566d6742852c527bf5af38af5cbb878dad75705
+.\" Author: Eric W. Biederman <ebiederm@xmission.com>
+.\" Date: Mon Jul 28 17:26:07 2014 -0700
+.\"
+.\" mnt: Correct permission checks in do_remount
+.\"
+when propagated from a more privileged to
+a less privileged mount namespace,
+and may not be changed in the less privileged mount namespace.
+.IP *
+.\" (As of 3.18-rc1 (in Al Viro's 2014-08-30 vfs.git#for-next tree))
+A file or directory that is a mount point in one namespace that is not
+a mount point in another namespace, may be renamed, unlinked, or removed
+.RB ( rmdir (2))
+in the mount namespace in which it is not a mount point
+(subject to the usual permission checks).
+.IP
+Previously, attempting to unlink, rename, or remove a file or directory
+that was a mount point in another mount namespace would result in the error
+.BR EBUSY .
+That behavior had technical problems of enforcement (e.g., for NFS)
+and permitted denial-of-service attacks against more privileged users.
+(i.e., preventing individual files from being updated
+by bind mounting on top of them).
+.\"
+.\" ============================================================
+.\"
+.SS User and group ID mappings: uid_map and gid_map
+When a user namespace is created,
+it starts out without a mapping of user IDs (group IDs)
+to the parent user namespace.
+The
+.IR /proc/[pid]/uid_map
+and
+.IR /proc/[pid]/gid_map
+files (available since Linux 3.5)
+.\" commit 22d917d80e842829d0ca0a561967d728eb1d6303
+expose the mappings for user and group IDs
+inside the user namespace for the process
+.IR pid .
+These files can be read to view the mappings in a user namespace and
+written to (once) to define the mappings.
+
+The description in the following paragraphs explains the details for
+.IR uid_map ;
+.IR gid_map
+is exactly the same,
+but each instance of "user ID" is replaced by "group ID".
+
+The
+.I uid_map
+file exposes the mapping of user IDs from the user namespace
+of the process
+.IR pid
+to the user namespace of the process that opened
+.IR uid_map
+(but see a qualification to this point below).
+In other words, processes that are in different user namespaces
+will potentially see different values when reading from a particular
+.I uid_map
+file, depending on the user ID mappings for the user namespaces
+of the reading processes.
+
+Each line in the
+.I uid_map
+file specifies a 1-to-1 mapping of a range of contiguous
+user IDs between two user namespaces.
+(When a user namespace is first created, this file is empty.)
+The specification in each line takes the form of
+three numbers delimited by white space.
+The first two numbers specify the starting user ID in
+each of the two user namespaces.
+The third number specifies the length of the mapped range.
+In detail, the fields are interpreted as follows:
+.IP (1) 4
+The start of the range of user IDs in
+the user namespace of the process
+.IR pid .
+.IP (2)
+The start of the range of user
+IDs to which the user IDs specified by field one map.
+How field two is interpreted depends on whether the process that opened
+.I uid_map
+and the process
+.IR pid
+are in the same user namespace, as follows:
+.RS
+.IP a) 3
+If the two processes are in different user namespaces:
+field two is the start of a range of
+user IDs in the user namespace of the process that opened
+.IR uid_map .
+.IP b)
+If the two processes are in the same user namespace:
+field two is the start of the range of
+user IDs in the parent user namespace of the process
+.IR pid .
+This case enables the opener of
+.I uid_map
+(the common case here is opening
+.IR /proc/self/uid_map )
+to see the mapping of user IDs into the user namespace of the process
+that created this user namespace.
+.RE
+.IP (3)
+The length of the range of user IDs that is mapped between the two
+user namespaces.
+.PP
+System calls that return user IDs (group IDs)\(emfor example,
+.BR getuid (2),
+.BR getgid (2),
+and the credential fields in the structure returned by
+.BR stat (2)\(emreturn
+the user ID (group ID) mapped into the caller's user namespace.
+
+When a process accesses a file, its user and group IDs
+are mapped into the initial user namespace for the purpose of permission
+checking and assigning IDs when creating a file.
+When a process retrieves file user and group IDs via
+.BR stat (2),
+the IDs are mapped in the opposite direction,
+to produce values relative to the process user and group ID mappings.
+
+The initial user namespace has no parent namespace,
+but, for consistency, the kernel provides dummy user and group
+ID mapping files for this namespace.
+Looking at the
+.I uid_map
+file
+.RI ( gid_map
+is the same) from a shell in the initial namespace shows:
+
+.in +4n
+.nf
+$ \fBcat /proc/$$/uid_map\fP
+ 0 0 4294967295
+.fi
+.in
+
+This mapping tells us
+that the range starting at user ID 0 in this namespace
+maps to a range starting at 0 in the (nonexistent) parent namespace,
+and the length of the range is the largest 32-bit unsigned integer.
+(This deliberately leaves 4294967295 (the 32-bit signed \-1 value) unmapped.
+This is deliberate:
+.IR "(uid_t)\ -\1"
+is used in several interfaces (e.g.,
+.BR setreuid (2))
+as a way to specify "no user ID".
+Leaving
+.IR "(uid_t)\ -\1"
+unmapped and unusable guarantees that there will be no
+confusion when using these interfaces.
+.\"
+.\" ============================================================
+.\"
+.SS Defining user and group ID mappings: writing to uid_map and gid_map
+.PP
+After the creation of a new user namespace, the
+.I uid_map
+file of
+.I one
+of the processes in the namespace may be written to
+.I once
+to define the mapping of user IDs in the new user namespace.
+An attempt to write more than once to a
+.I uid_map
+file in a user namespace fails with the error
+.BR EPERM .
+Similar rules apply for
+.I gid_map
+files.
+
+The lines written to
+.IR uid_map
+.RI ( gid_map )
+must conform to the following rules:
+.IP * 3
+The three fields must be valid numbers,
+and the last field must be greater than 0.
+.IP *
+Lines are terminated by newline characters.
+.IP *
+There is an (arbitrary) limit on the number of lines in the file.
+As at Linux 3.8, the limit is five lines.
+In addition, the number of bytes written to
+the file must be less than the system page size,
+.\" FIXME(Eric): the restriction "less than" rather than "less than or equal"
+.\" seems strangely arbitrary. Furthermore, the comment does not agree
+.\" with the code in kernel/user_namespace.c. Which is correct?
+and the write must be performed at the start of the file (i.e.,
+.BR lseek (2)
+and
+.BR pwrite (2)
+can't be used to write to nonzero offsets in the file).
+.IP *
+The range of user IDs (group IDs)
+specified in each line cannot overlap with the ranges
+in any other lines.
+In the initial implementation (Linux 3.8), this requirement was
+satisfied by a simplistic implementation that imposed the further
+requirement that
+the values in both field 1 and field 2 of successive lines must be
+in ascending numerical order,
+which prevented some otherwise valid maps from being created.
+Linux 3.9 and later
+.\" commit 0bd14b4fd72afd5df41e9fd59f356740f22fceba
+fix this limitation, allowing any valid set of nonoverlapping maps.
+.IP *
+At least one line must be written to the file.
+.PP
+Writes that violate the above rules fail with the error
+.BR EINVAL .
+
+In order for a process to write to the
+.I /proc/[pid]/uid_map
+.RI ( /proc/[pid]/gid_map )
+file, all of the following requirements must be met:
+.IP 1. 3
+The writing process must have the
+.BR CAP_SETUID
+.RB ( CAP_SETGID )
+capability in the user namespace of the process
+.IR pid .
+.IP 2.
+The writing process must be in either the user namespace of the process
+.I pid
+or inside the parent user namespace of the process
+.IR pid .
+.IP 3.
+The mapped user IDs (group IDs) must in turn have a mapping
+in the parent user namespace.
+.IP 4.
+One of the following is true:
+.RS
+.IP * 3
+The data written to
+.I uid_map
+.RI ( gid_map )
+consists of a single line that maps the writing process's filesystem user ID
+(group ID) in the parent user namespace to a user ID (group ID)
+in the user namespace.
+The usual case here is that this single line provides a mapping for user ID
+of the process that created the namespace.
+.IP * 3
+The opening process has the
+.BR CAP_SETUID
+.RB ( CAP_SETGID )
+capability in the parent user namespace.
+Thus, a privileged process can make mappings to arbitrary user IDs (group IDs)
+in the parent user namespace.
+.RE
+.PP
+Writes that violate the above rules fail with the error
+.BR EPERM .
+.\"
+.\" ============================================================
+.\"
+.SS Unmapped user and group IDs
+.PP
+There are various places where an unmapped user ID (group ID)
+may be exposed to user space.
+For example, the first process in a new user namespace may call
+.BR getuid ()
+before a user ID mapping has been defined for the namespace.
+In most such cases, an unmapped user ID is converted
+.\" from_kuid_munged(), from_kgid_munged()
+to the overflow user ID (group ID);
+the default value for the overflow user ID (group ID) is 65534.
+See the descriptions of
+.IR /proc/sys/kernel/overflowuid
+and
+.IR /proc/sys/kernel/overflowgid
+in
+.BR proc (5).
+
+The cases where unmapped IDs are mapped in this fashion include
+system calls that return user IDs
+.RB ( getuid (2)
+.BR getgid (2),
+and similar),
+credentials passed over a UNIX domain socket,
+.\" also SO_PEERCRED
+credentials returned by
+.BR stat (2),
+.BR waitid (2),
+and the System V IPC "ctl"
+.B IPC_STAT
+operations,
+credentials exposed by
+.IR /proc/PID/status
+and the files in
+.IR /proc/sysvipc/* ,
+credentials returned via the
+.I si_uid
+field in the
+.I siginfo_t
+received with a signal (see
+.BR sigaction (2)),
+credentials written to the process accounting file (see
+.BR acct (5)),
+and credentials returned with POSIX message queue notifications (see
+.BR mq_notify (3)).
+
+There is one notable case where unmapped user and group IDs are
+.I not
+.\" from_kuid(), from_kgid()
+.\" Also F_GETOWNER_UIDS is an exception
+converted to the corresponding overflow ID value.
+When viewing a
+.I uid_map
+or
+.I gid_map
+file in which there is no mapping for the second field,
+that field is displayed as 4294967295 (\-1 as an unsigned integer);
+.\"
+.\" ============================================================
+.\"
+.SS Set-user-ID and set-group-ID programs
+.PP
+When a process inside a user namespace executes
+a set-user-ID (set-group-ID) program,
+the process's effective user (group) ID inside the namespace is changed
+to whatever value is mapped for the user (group) ID of the file.
+However, if either the user
+.I or
+the group ID of the file has no mapping inside the namespace,
+the set-user-ID (set-group-ID) bit is silently ignored:
+the new program is executed,
+but the process's effective user (group) ID is left unchanged.
+(This mirrors the semantics of executing a set-user-ID or set-group-ID
+program that resides on a filesystem that was mounted with the
+.BR MS_NOSUID
+flag, as described in
+.BR mount (2).)
+.\"
+.\" ============================================================
+.\"
+.SS Miscellaneous
+.PP
+When a process's user and group IDs are passed over a UNIX domain socket
+to a process in a different user namespace (see the description of
+.B SCM_CREDENTIALS
+in
+.BR unix (7)),
+they are translated into the corresponding values as per the
+receiving process's user and group ID mappings.
+.\"
+.SH CONFORMING TO
+Namespaces are a Linux-specific feature.
+.\"
+.SH NOTES
+Over the years, there have been a lot of features that have been added
+to the Linux kernel that have been made available only to privileged users
+because of their potential to confuse set-user-ID-root applications.
+In general, it becomes safe to allow the root user in a user namespace to
+use those features because it is impossible, while in a user namespace,
+to gain more privilege than the root user of a user namespace has.
+.\"
+.\" ============================================================
+.\"
+.SS Availability
+Use of user namespaces requires a kernel that is configured with the
+.B CONFIG_USER_NS
+option.
+User namespaces require support in a range of subsystems across
+the kernel.
+When an unsupported subsystem is configured into the kernel,
+it is not possible to configure user namespaces support.
+
+As at Linux 3.8, most relevant subsystems supported user namespaces,
+but a number of filesystems did not have the infrastructure needed
+to map user and group IDs between user namespaces.
+Linux 3.9 added the required infrastructure support for many of
+the remaining unsupported filesystems
+(Plan 9 (9P), Andrew File System (AFS), Ceph, CIFS, CODA, NFS, and OCFS2).
+Linux 3.11 added support the last of the unsupported major filesystems,
+.\" commit d6970d4b726cea6d7a9bc4120814f95c09571fc3
+XFS.
+.\"
+.SH EXAMPLE
+The program below is designed to allow experimenting with
+user namespaces, as well as other types of namespaces.
+It creates namespaces as specified by command-line options and then executes
+a command inside those namespaces.
+The comments and
+.I usage()
+function inside the program provide a full explanation of the program.
+The following shell session demonstrates its use.
+
+First, we look at the run-time environment:
+
+.in +4n
+.nf
+$ \fBuname -rs\fP # Need Linux 3.8 or later
+Linux 3.8.0
+$ \fBid -u\fP # Running as unprivileged user
+1000
+$ \fBid -g\fP
+1000
+.fi
+.in
+
+Now start a new shell in new user
+.RI ( \-U ),
+mount
+.RI ( \-m ),
+and PID
+.RI ( \-p )
+namespaces, with user ID
+.RI ( \-M )
+and group ID
+.RI ( \-G )
+1000 mapped to 0 inside the user namespace:
+
+.in +4n
+.nf
+$ \fB./userns_child_exec -p -m -U -M '0 1000 1' -G '0 1000 1' bash\fP
+.fi
+.in
+
+The shell has PID 1, because it is the first process in the new
+PID namespace:
+
+.in +4n
+.nf
+bash$ \fBecho $$\fP
+1
+.fi
+.in
+
+Inside the user namespace, the shell has user and group ID 0,
+and a full set of permitted and effective capabilities:
+
+.in +4n
+.nf
+bash$ \fBcat /proc/$$/status | egrep '^[UG]id'\fP
+Uid: 0 0 0 0
+Gid: 0 0 0 0
+bash$ \fBcat /proc/$$/status | egrep '^Cap(Prm|Inh|Eff)'\fP
+CapInh: 0000000000000000
+CapPrm: 0000001fffffffff
+CapEff: 0000001fffffffff
+.fi
+.in
+
+Mounting a new
+.I /proc
+filesystem and listing all of the processes visible
+in the new PID namespace shows that the shell can't see
+any processes outside the PID namespace:
+
+.in +4n
+.nf
+bash$ \fBmount -t proc proc /proc\fP
+bash$ \fBps ax\fP
+ PID TTY STAT TIME COMMAND
+ 1 pts/3 S 0:00 bash
+ 22 pts/3 R+ 0:00 ps ax
+.fi
+.in
+.SS Program source
+\&
+.nf
+/* userns_child_exec.c
+
+ Licensed under GNU General Public License v2 or later
+
+ Create a child process that executes a shell command in new
+ namespace(s); allow UID and GID mappings to be specified when
+ creating a user namespace.
+*/
+#define _GNU_SOURCE
+#include <sched.h>
+#include <unistd.h>
+#include <stdlib.h>
+#include <sys/wait.h>
+#include <signal.h>
+#include <fcntl.h>
+#include <stdio.h>
+#include <string.h>
+#include <limits.h>
+#include <errno.h>
+
+/* A simple error\-handling function: print an error message based
+ on the value in \(aqerrno\(aq and terminate the calling process */
+
+#define errExit(msg) do { perror(msg); exit(EXIT_FAILURE); \\
+ } while (0)
+
+struct child_args {
+ char **argv; /* Command to be executed by child, with args */
+ int pipe_fd[2]; /* Pipe used to synchronize parent and child */
+};
+
+static int verbose;
+
+static void
+usage(char *pname)
+{
+ fprintf(stderr, "Usage: %s [options] cmd [arg...]\\n\\n", pname);
+ fprintf(stderr, "Create a child process that executes a shell "
+ "command in a new user namespace,\\n"
+ "and possibly also other new namespace(s).\\n\\n");
+ fprintf(stderr, "Options can be:\\n\\n");
+#define fpe(str) fprintf(stderr, " %s", str);
+ fpe("\-i New IPC namespace\\n");
+ fpe("\-m New mount namespace\\n");
+ fpe("\-n New network namespace\\n");
+ fpe("\-p New PID namespace\\n");
+ fpe("\-u New UTS namespace\\n");
+ fpe("\-U New user namespace\\n");
+ fpe("\-M uid_map Specify UID map for user namespace\\n");
+ fpe("\-G gid_map Specify GID map for user namespace\\n");
+ fpe("\-z Map user\(aqs UID and GID to 0 in user namespace\\n");
+ fpe(" (equivalent to: \-M \(aq0 <uid> 1\(aq \-G \(aq0 <gid> 1\(aq)\\n");
+ fpe("\-v Display verbose messages\\n");
+ fpe("\\n");
+ fpe("If \-z, \-M, or \-G is specified, \-U is required.\\n");
+ fpe("It is not permitted to specify both \-z and either \-M or \-G.\\n");
+ fpe("\\n");
+ fpe("Map strings for \-M and \-G consist of records of the form:\\n");
+ fpe("\\n");
+ fpe(" ID\-inside\-ns ID\-outside\-ns len\\n");
+ fpe("\\n");
+ fpe("A map string can contain multiple records, separated"
+ " by commas;\\n");
+ fpe("the commas are replaced by newlines before writing"
+ " to map files.\\n");
+
+ exit(EXIT_FAILURE);
+}
+
+/* Update the mapping file \(aqmap_file\(aq, with the value provided in
+ \(aqmapping\(aq, a string that defines a UID or GID mapping. A UID or
+ GID mapping consists of one or more newline\-delimited records
+ of the form:
+
+ ID_inside\-ns ID\-outside\-ns length
+
+ Requiring the user to supply a string that contains newlines is
+ of course inconvenient for command\-line use. Thus, we permit the
+ use of commas to delimit records in this string, and replace them
+ with newlines before writing the string to the file. */
+
+static void
+update_map(char *mapping, char *map_file)
+{
+ int fd, j;
+ size_t map_len; /* Length of \(aqmapping\(aq */
+
+ /* Replace commas in mapping string with newlines */
+
+ map_len = strlen(mapping);
+ for (j = 0; j < map_len; j++)
+ if (mapping[j] == \(aq,\(aq)
+ mapping[j] = \(aq\\n\(aq;
+
+ fd = open(map_file, O_RDWR);
+ if (fd == \-1) {
+ fprintf(stderr, "ERROR: open %s: %s\\n", map_file,
+ strerror(errno));
+ exit(EXIT_FAILURE);
+ }
+
+ if (write(fd, mapping, map_len) != map_len) {
+ fprintf(stderr, "ERROR: write %s: %s\\n", map_file,
+ strerror(errno));
+ exit(EXIT_FAILURE);
+ }
+
+ close(fd);
+}
+
+static int /* Start function for cloned child */
+childFunc(void *arg)
+{
+ struct child_args *args = (struct child_args *) arg;
+ char ch;
+
+ /* Wait until the parent has updated the UID and GID mappings.
+ See the comment in main(). We wait for end of file on a
+ pipe that will be closed by the parent process once it has
+ updated the mappings. */
+
+ close(args\->pipe_fd[1]); /* Close our descriptor for the write
+ end of the pipe so that we see EOF
+ when parent closes its descriptor */
+ if (read(args\->pipe_fd[0], &ch, 1) != 0) {
+ fprintf(stderr,
+ "Failure in child: read from pipe returned != 0\\n");
+ exit(EXIT_FAILURE);
+ }
+
+ /* Execute a shell command */
+
+ printf("About to exec %s\\n", args\->argv[0]);
+ execvp(args\->argv[0], args\->argv);
+ errExit("execvp");
+}
+
+#define STACK_SIZE (1024 * 1024)
+
+static char child_stack[STACK_SIZE]; /* Space for child\(aqs stack */
+
+int
+main(int argc, char *argv[])
+{
+ int flags, opt, map_zero;
+ pid_t child_pid;
+ struct child_args args;
+ char *uid_map, *gid_map;
+ const int MAP_BUF_SIZE = 100;
+ char map_buf[MAP_BUF_SIZE];
+ char map_path[PATH_MAX];
+
+ /* Parse command\-line options. The initial \(aq+\(aq character in
+ the final getopt() argument prevents GNU\-style permutation
+ of command\-line options. That\(aqs useful, since sometimes
+ the \(aqcommand\(aq to be executed by this program itself
+ has command\-line options. We don\(aqt want getopt() to treat
+ those as options to this program. */
+
+ flags = 0;
+ verbose = 0;
+ gid_map = NULL;
+ uid_map = NULL;
+ map_zero = 0;
+ while ((opt = getopt(argc, argv, "+imnpuUM:G:zv")) != \-1) {
+ switch (opt) {
+ case \(aqi\(aq: flags |= CLONE_NEWIPC; break;
+ case \(aqm\(aq: flags |= CLONE_NEWNS; break;
+ case \(aqn\(aq: flags |= CLONE_NEWNET; break;
+ case \(aqp\(aq: flags |= CLONE_NEWPID; break;
+ case \(aqu\(aq: flags |= CLONE_NEWUTS; break;
+ case \(aqv\(aq: verbose = 1; break;
+ case \(aqz\(aq: map_zero = 1; break;
+ case \(aqM\(aq: uid_map = optarg; break;
+ case \(aqG\(aq: gid_map = optarg; break;
+ case \(aqU\(aq: flags |= CLONE_NEWUSER; break;
+ default: usage(argv[0]);
+ }
+ }
+
+ /* \-M or \-G without \-U is nonsensical */
+
+ if (((uid_map != NULL || gid_map != NULL || map_zero) &&
+ !(flags & CLONE_NEWUSER)) ||
+ (map_zero && (uid_map != NULL || gid_map != NULL)))
+ usage(argv[0]);
+
+ args.argv = &argv[optind];
+
+ /* We use a pipe to synchronize the parent and child, in order to
+ ensure that the parent sets the UID and GID maps before the child
+ calls execve(). This ensures that the child maintains its
+ capabilities during the execve() in the common case where we
+ want to map the child\(aqs effective user ID to 0 in the new user
+ namespace. Without this synchronization, the child would lose
+ its capabilities if it performed an execve() with nonzero
+ user IDs (see the capabilities(7) man page for details of the
+ transformation of a process\(aqs capabilities during execve()). */
+
+ if (pipe(args.pipe_fd) == \-1)
+ errExit("pipe");
+
+ /* Create the child in new namespace(s) */
+
+ child_pid = clone(childFunc, child_stack + STACK_SIZE,
+ flags | SIGCHLD, &args);
+ if (child_pid == \-1)
+ errExit("clone");
+
+ /* Parent falls through to here */
+
+ if (verbose)
+ printf("%s: PID of child created by clone() is %ld\\n",
+ argv[0], (long) child_pid);
+
+ /* Update the UID and GID maps in the child */
+
+ if (uid_map != NULL || map_zero) {
+ snprintf(map_path, PATH_MAX, "/proc/%ld/uid_map",
+ (long) child_pid);
+ if (map_zero) {
+ snprintf(map_buf, MAP_BUF_SIZE, "0 %ld 1", (long) getuid());
+ uid_map = map_buf;
+ }
+ update_map(uid_map, map_path);
+ }
+ if (gid_map != NULL || map_zero) {
+ snprintf(map_path, PATH_MAX, "/proc/%ld/gid_map",
+ (long) child_pid);
+ if (map_zero) {
+ snprintf(map_buf, MAP_BUF_SIZE, "0 %ld 1", (long) getgid());
+ gid_map = map_buf;
+ }
+ update_map(gid_map, map_path);
+ }
+
+ /* Close the write end of the pipe, to signal to the child that we
+ have updated the UID and GID maps */
+
+ close(args.pipe_fd[1]);
+
+ if (waitpid(child_pid, NULL, 0) == \-1) /* Wait for child */
+ errExit("waitpid");
+
+ if (verbose)
+ printf("%s: terminating\\n", argv[0]);
+
+ exit(EXIT_SUCCESS);
+}
+.fi
+.SH SEE ALSO
+.BR newgidmap (1), \" From the shadow package
+.BR newuidmap (1), \" From the shadow package
+.BR clone (2),
+.BR setns (2),
+.BR unshare (2),
+.BR proc (5),
+.BR subgid (5), \" From the shadow package
+.BR subuid (5), \" From the shadow package
+.BR credentials (7),
+.BR capabilities (7),
+.BR namespaces (7),
+.BR pid_namespaces (7)
+.sp
+The kernel source file
+.IR Documentation/namespaces/resource-control.txt .
+.SH COLOPHON
+This page is part of release 3.75 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.
.\" 2001-05-11 Markus Kuhn <mgk25@cl.cam.ac.uk>
.\" Update
.\"
-.TH UTF-8 7 2014-02-26 "GNU" "Linux Programmer's Manual"
+.TH UTF-8 7 2014-06-13 "GNU" "Linux Programmer's Manual"
.SH NAME
UTF-8 \- an ASCII compatible multibyte Unicode encoding
.SH DESCRIPTION
-The
-.B Unicode 3.0
-character set occupies a 16-bit code space.
+The Unicode 3.0 character set occupies a 16-bit code space.
The most obvious
-Unicode encoding (known as
-.BR UCS-2 )
+Unicode encoding (known as UCS-2)
consists of a sequence of 16-bit words.
Such strings can contain\(emas part of many 16-bit characters\(embytes
such as \(aq\\0\(aq or \(aq/\(aq, which have a
In addition, the majority of UNIX tools expect ASCII files and can't
read 16-bit words as characters without major modifications.
For these reasons,
-.B UCS-2
-is not a suitable external encoding of
-.B Unicode
+UCS-2 is not a suitable external encoding of Unicode
in filenames, text files, environment variables, and so on.
-The
-.BR "ISO 10646 Universal Character Set (UCS)" ,
+The ISO 10646 Universal Character Set (UCS),
a superset of Unicode, occupies an even larger code
space\(em31\ bits\(emand the obvious
-.B UCS-4
-encoding for it (a sequence of 32-bit words) has the same problems.
+UCS-4 encoding for it (a sequence of 32-bit words) has the same problems.
-The
-.B UTF-8
-encoding of
-.B Unicode
-and
-.B UCS
+The UTF-8 encoding of Unicode and UCS
does not have these problems and is the common way in which
-.B Unicode
-is used on UNIX-style operating systems.
+Unicode is used on UNIX-style operating systems.
.SS Properties
-The
-.B UTF-8
-encoding has the following nice properties:
+The UTF-8 encoding has the following nice properties:
.TP 0.2i
*
-.B UCS
-characters 0x00000000 to 0x0000007f (the classic
-.B US-ASCII
+UCS
+characters 0x00000000 to 0x0000007f (the classic US-ASCII
characters) are encoded simply as bytes 0x00 to 0x7f (ASCII
compatibility).
This means that files and strings which contain only
7-bit ASCII characters have the same encoding under both
-.B ASCII
+ASCII
and
-.BR UTF-8 .
+UTF-8 .
.TP
*
-All
-.B UCS
-characters greater than 0x7f are encoded as a multibyte sequence
+All UCS characters greater than 0x7f are encoded as a multibyte sequence
consisting only of bytes in the range 0x80 to 0xfd, so no ASCII
byte can appear as part of another character and there are no
problems with, for example, \(aq\\0\(aq or \(aq/\(aq.
.TP
*
-The lexicographic sorting order of
-.B UCS-4
-strings is preserved.
+The lexicographic sorting order of UCS-4 strings is preserved.
.TP
*
-All possible 2^31 UCS codes can be encoded using
-.BR UTF-8 .
+All possible 2^31 UCS codes can be encoded using UTF-8.
.TP
*
-The bytes 0xc0, 0xc1, 0xfe, and 0xff are never used in the
-.B UTF-8
-encoding.
+The bytes 0xc0, 0xc1, 0xfe, and 0xff are never used in the UTF-8 encoding.
.TP
*
The first byte of a multibyte sequence which represents a single non-ASCII
-.B UCS
-character is always in the range 0xc2 to 0xfd and indicates how long
+UCS character is always in the range 0xc2 to 0xfd and indicates how long
this multibyte sequence is.
All further bytes in a multibyte sequence
are in the range 0x80 to 0xbf.
makes the encoding stateless and robust against missing bytes.
.TP
*
-.B UTF-8
-encoded
-.B UCS
-characters may be up to six bytes long, however the
-.B Unicode
-standard specifies no characters above 0x10ffff, so Unicode characters
+UTF-8 encoded UCS characters may be up to six bytes long, however the
+Unicode standard specifies no characters above 0x10ffff, so Unicode characters
can be only up to four bytes long in
-.BR UTF-8 .
+UTF-8.
.SS Encoding
The following byte sequences are used to represent a character.
The sequence to be used depends on the UCS code number of the character:
Only the shortest possible multibyte sequence
which can represent the code number of the character can be used.
.PP
-The
-.B UCS
-code values 0xd800\(en0xdfff (UTF-16 surrogates) as well as 0xfffe and
-0xffff (UCS noncharacters) should not appear in conforming
-.B UTF-8
-streams.
+The UCS code values 0xd800\(en0xdfff (UTF-16 surrogates) as well as 0xfffe and
+0xffff (UCS noncharacters) should not appear in conforming UTF-8 streams.
.SS Example
-The
-.B Unicode
-character 0xa9 = 1010 1001 (the copyright sign) is encoded
+The Unicode character 0xa9 = 1010 1001 (the copyright sign) is encoded
in UTF-8 as
.PP
.RS
11100010 10001001 10100000 = 0xe2 0x89 0xa0
.RE
.SS Application notes
-Users have to select a
-.B UTF-8
-locale, for example with
+Users have to select a UTF-8 locale, for example with
.PP
.RS
export LANG=en_GB.UTF-8
.RE
.PP
-in order to activate the
-.B UTF-8
-support in applications.
+in order to activate the UTF-8 support in applications.
.PP
Application software that has to be aware of the used character
encoding should always set the locale with for example
strcmp(nl_langinfo(CODESET), "UTF-8") == 0
.RE
.PP
-to determine whether a
-.B UTF-8
-locale has been selected and whether
+to determine whether a UTF-8 locale has been selected and whether
therefore all plaintext standard input and output, terminal
communication, plaintext file content, filenames and environment
-variables are encoded in
-.BR UTF-8 .
+variables are encoded in UTF-8.
.PP
-Programmers accustomed to single-byte encodings such as
-.B US-ASCII
-or
-.B ISO 8859
+Programmers accustomed to single-byte encodings such as US-ASCII or ISO 8859
have to be aware that two assumptions made so far are no longer valid
-in
-.B UTF-8
-locales.
+in UTF-8 locales.
Firstly, a single byte does not necessarily correspond any
more to a single character.
-Secondly, since modern terminal emulators
-in
-.B UTF-8
+Secondly, since modern terminal emulators in UTF-8
mode also support Chinese, Japanese, and Korean
-.B double-width characters
-as well as nonspacing
-.BR "combining characters" ,
+double-width characters as well as nonspacing combining characters,
outputting a single character does not necessarily advance the cursor
-by one position as it did in
-.BR ASCII .
+by one position as it did in ASCII.
Library functions such as
.BR mbsrtowcs (3)
and
.BR wcswidth (3)
should be used today to count characters and cursor positions.
.PP
-The official ESC sequence to switch from an
-.B ISO 2022
+The official ESC sequence to switch from an ISO 2022
encoding scheme (as used for instance by VT100 terminals) to
-.B UTF-8
-is ESC % G
+UTF-8 is ESC % G
("\\x1b%G").
The corresponding return sequence from
-.B UTF-8
-to ISO 2022 is ESC % @ ("\\x1b%@").
+UTF-8 to ISO 2022 is ESC % @ ("\\x1b%@").
Other ISO 2022 sequences (such as
for switching the G0 and G1 sets) are not applicable in UTF-8 mode.
-.PP
-It can be hoped that in the foreseeable future,
-.B UTF-8
-will replace
-.B ASCII
-and
-.B ISO 8859
-at all levels as the common character encoding on POSIX systems,
-leading to a significantly richer environment for handling plain text.
.SS Security
-The
-.BR Unicode " and " UCS
-standards require that producers of
-.B UTF-8
+The Unicode and UCS standards require that producers of UTF-8
shall use the shortest form possible, for example, producing a two-byte
sequence with first byte 0xc0 is nonconforming.
-.B Unicode 3.1
-has added the requirement that conforming programs must not accept
+Unicode 3.1 has added the requirement that conforming programs must not accept
non-shortest forms in their input.
This is for security reasons: if
user input is checked for possible security violations, a program
-might check only for the
-.B ASCII
+might check only for the ASCII
version of "/../" or ";" or NUL and overlook that there are many
-.RB non- ASCII
-ways to represent these things in a non-shortest
-.B UTF-8
+non-ASCII ways to represent these things in a non-shortest UTF-8
encoding.
.SS Standards
ISO/IEC 10646-1:2000, Unicode 3.1, RFC\ 3629, Plan 9.
.\" .SH AUTHOR
.\" Markus Kuhn <mgk25@cl.cam.ac.uk>
.SH SEE ALSO
+.BR locale (1),
.BR nl_langinfo (3),
.BR setlocale (3),
.BR charsets (7),
.BR unicode (7)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" http://www.linuxjournal.com/content/creating-vdso-colonels-other-chicken
.\" http://www.trilithium.com/johan/2005/08/linux-gate/
.\"
-.TH VDSO 7 2014-02-01 "Linux" "Linux Programmer's Manual"
+.TH VDSO 7 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
vDSO \- overview of the virtual ELF dynamic shared object
.SH SYNOPSIS
__kernel_sigreturn LINUX_2.5
__kernel_rt_sigreturn LINUX_2.5
__kernel_vsyscall LINUX_2.5
+.\" Added in 7a59ed415f5b57469e22e41fc4188d5399e0b194 and updated
+.\" in 37c975545ec63320789962bf307f000f08fabd48.
+__vdso_clock_gettime LINUX_2.6 (exported since Linux 3.15)
+__vdso_gettimeofday LINUX_2.6 (exported since Linux 3.15)
+__vdso_time LINUX_2.6 (exported since Linux 3.15)
.TE
.if t \{\
.in
.fi
.in
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.UR ftp://ftp.pspt.fi\:/pub\:/ham\:/linux\:/ax25\:/x25doc.tgz
.UE .
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
--- /dev/null
+'\" t -*- coding: UTF-8 -*-
+.\"
+.\" Copyright (C) 2014 Marko Myllynen <myllynen@redhat.com>
+.\"
+.\" %%%LICENSE_START(GPLv2+_DOC_FULL)
+.\" This is free documentation; you can redistribute it and/or
+.\" modify it under the terms of the GNU General Public License as
+.\" published by the Free Software Foundation; either version 2 of
+.\" the License, or (at your option) any later version.
+.\"
+.\" The GNU General Public License's references to "object code"
+.\" and "executables" are to be interpreted as the output of any
+.\" document formatting or typesetting system, including
+.\" intermediate and printed output.
+.\"
+.\" This manual is distributed in the hope that it will be useful,
+.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
+.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+.\" GNU General Public License for more details.
+.\"
+.\" You should have received a copy of the GNU General Public
+.\" License along with this manual; if not, see
+.\" <http://www.gnu.org/licenses/>.
+.\" %%%LICENSE_END
+.\"
+.TH ICONVCONFIG 8 2014-07-08 "GNU" "Linux System Administration"
+.SH NAME
+iconvconfig \- create iconv module configuration cache
+.SH SYNOPSIS
+.B iconvconfig
+.RI [ options ]
+.RI [ directory ]...
+.SH DESCRIPTION
+The
+.BR iconv (3)
+function internally uses
+.I gconv
+modules to convert to and from a character set.
+A configuration file is used to determine the needed modules
+for a conversion.
+Loading and parsing such a configuration file would slow down
+programs that use
+.BR iconv (3),
+so a caching mechanism is employed.
+
+The
+.B iconvconfig
+program reads iconv module configuration files and writes
+a fast-loading gconv module configuration cache file.
+In addition to the system provided gconv modules, the user can specify
+custom gconv module directories with the environment variable
+.BR GCONV_PATH .
+However, iconv module configuration caching is only used when
+the environment variable
+.BR GCONV_PATH
+is not set.
+.SH OPTIONS
+.TP
+.B "\-\-nostdlib"
+Do not search the system default gconv directory,
+only the directories provided on the command line.
+.TP
+.BI \-o " outputfile" ", \-\-output=" outputfile
+Use
+.I outputfile
+for output instead of the system default cache location.
+.TP
+.BI \-\-prefix= pathname
+Set the prefix to be prepended to the system pathnames.
+See FILES, below.
+By default, the prefix is empty.
+Setting the prefix to
+.IR foo ,
+the gconv module configuration would be read from
+.IR foo/usr/lib/gconv/gconv-modules
+and the cache would be written to
+.IR foo/usr/lib/gconv/gconv-modules.cache .
+.TP
+.BR \-? ", " \-\-help
+Print a usage summary and exit.
+.TP
+.B "\-\-usage"
+Print a short usage summary and exit.
+.TP
+.BR \-V ", " \-\-version
+Print the version number, license, and disclaimer of warranty for
+.BR iconv .
+.SH EXIT STATUS
+Zero on success, non-zero on errors.
+.SH FILES
+.TP
+.I /usr/lib/gconv
+Usual default gconv module path.
+.TP
+.I /usr/lib/gconv/gconv-modules
+Usual system default gconv module configuration file.
+.TP
+.I /usr/lib/gconv/gconv-modules.cache
+Usual system gconv module configuration cache.
+.SH "SEE ALSO"
+.BR iconv (1),
+.BR iconv (3)
+.SH COLOPHON
+This page is part of release 3.75 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.
conditions.
Note that these can be different from page to page!
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" This is in the public domain
.\" %%%LICENSE_END
.\"
-.TH LD.SO 8 2014-01-08 "GNU" "Linux Programmer's Manual"
+.TH LD.SO 8 2014-10-02 "GNU" "Linux Programmer's Manual"
.SH NAME
ld.so, ld-linux.so* \- dynamic linker/loader
.SH SYNOPSIS
Otherwise, both have the same behavior, and use the same
support files and programs
.BR ldd (1),
-.BR ldconfig (8)
+.BR ldconfig (8),
and
.IR /etc/ld.so.conf .
.LP
.TP
.B LD_PROFILE
(glibc since 2.1)
-Shared object to be profiled,
+The name of a (single) shared object to be profiled,
specified either as a pathname or a soname.
-Profiling output is written to the file whose name is:
+Profiling output is appended to the file whose name is:
"\fI$LD_PROFILE_OUTPUT\fP/\fI$LD_PROFILE\fP.profile".
.TP
.B LD_PROFILE_OUTPUT
is ignored for set-user-ID/set-group-ID binaries.
.\" FIXME
.\" Document LD_TRACE_PRELINKING (e.g.: LD_TRACE_PRELINKING=libx1.so ./prog)
-.\" Since glibc 2.3
-.\" Also enables DL_DEBUG_PRELINK
+.\" Available since glibc 2.3
+.\" Also enables DL_DEBUG_PRELINK
.TP
.B LD_USE_LOAD_BIAS
.\" http://sources.redhat.com/ml/libc-hacker/2003-11/msg00127.html
4.4.3 or greater.
ELF functionality is available since Linux 1.1.52 and libc5.
.SH SEE ALSO
+.BR ld (1),
.BR ldd (1),
+.BR pldd (1),
+.BR sprof (1),
+.BR dlopen (3),
.BR getauxval (3),
.BR rtld-audit (7),
.BR ldconfig (8),
.\"
.\" In the above, (libc5) stands for David Engel's ld.so/ld-linux.so.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ldd (1),
.BR ld.so (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.\" .B nscd
.\" was written by Thorsten Kukuk and Ulrich Drepper.
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR ldconfig (8),
.BR ld.so (8)
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR zic (8)
.\" @(#)tzselect.8 1.3
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR zic (8)
.\" @(#)zdump.8 7.3
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
.BR zdump (8)
.\" @(#)zic.8 7.19
.SH COLOPHON
-This page is part of release 3.68 of the Linux
+This page is part of release 3.75 of the Linux
.I man-pages
project.
A description of the project,
-○:LDP man-pages:3.68:2013/03/15:getent:1:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2007/11/15:intro:1:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/07/16:ldd:1:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
-×:LDP man-pages:3.68:2014/05/28:locale:1:::::
-×:LDP man-pages:3.68:2014/05/26:localedef:1:::::
-○:LDP man-pages:3.68:2008/11/14:time:1:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/20:_Exit:2:_exit:2:
-＠:LDP man-pages:3.68:2014/05/28:__clone2:2:clone:2:
-○:LDP man-pages:3.68:2010/09/20:_exit:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2012/07/13:_llseek:2:llseek:2:
-＠:LDP man-pages:3.68:2014/01/31:_newselect:2:select:2:
-○:LDP man-pages:3.68:2007/12/19:_syscall:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2012/12/22:_sysctl:2:sysctl:2:
-○:LDP man-pages:3.68:2010/09/10:accept:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/10:accept4:2:accept:2:
-○:LDP man-pages:3.68:2014/02/21:access:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2008/06/16:acct:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-×:LDP man-pages:3.68:2010/02/25:add_key:2:::::
-○:LDP man-pages:3.68:2014/05/28:adjtimex:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/02/12:afs_syscall:2:unimplemented:2:
-○:LDP man-pages:3.68:2014/02/23:alarm:2:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-○:LDP man-pages:3.68:2007/05/31:alloc_hugepages:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2007/12/26:arch_prctl:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/03:arm_fadvise:2:posix_fadvise:2:
-＠:LDP man-pages:3.68:2014/05/03:arm_fadvise64_64:2:posix_fadvise:2:
-＠:LDP man-pages:3.68:2013/04/01:arm_sync_file_range:2:sync_file_range:2:
-○:LDP man-pages:3.68:2014/04/06:bdflush:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/10:bind:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/02/12:break:2:unimplemented:2:
-○:LDP man-pages:3.68:2010/09/20:brk:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2007/05/26:cacheflush:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/03/11:capget:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/03/11:capset:2:capget:2:
-○:LDP man-pages:3.68:2010/11/25:chdir:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/21:chmod:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/21:chown:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/21:chown32:2:chown:2:
-○:LDP man-pages:3.68:2010/09/20:chroot:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2013/12/28:clock_getres:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/12/28:clock_gettime:2:clock_getres:2:
-○:LDP man-pages:3.68:2013/07/30:clock_nanosleep:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/12/28:clock_settime:2:clock_getres:2:
-○:LDP man-pages:3.68:2014/05/28:clone:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:clone2:2:clone:2:
-○:LDP man-pages:3.68:2013/12/30:close:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/10:connect:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/10:creat:2:open:2:
-☆:LDP man-pages:3.65=>3.68:2014/05/10:create_module:2:2014/04/24::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-☆:LDP man-pages:3.41=>3.68:2014/05/10:delete_module:2:2006/07/30::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/02/14:dup:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2012/02/14:dup2:2:dup:2:
-＠:LDP man-pages:3.68:2012/02/14:dup3:2:dup:2:
-○:LDP man-pages:3.68:2012/04/15:epoll_create:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2012/04/15:epoll_create1:2:epoll_create:2:
-○:LDP man-pages:3.68:2012/04/15:epoll_ctl:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/31:epoll_pwait:2:epoll_wait:2:
-○:LDP man-pages:3.68:2014/01/31:epoll_wait:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/08/30:eventfd:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/08/30:eventfd2:2:eventfd:2:
-○:LDP man-pages:3.68:2014/05/10:execve:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/20:exit:2:_exit:2:
-○:LDP man-pages:3.68:2008/11/27:exit_group:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2014/02/21:faccessat:2:access:2:
-＠:LDP man-pages:3.68:2014/05/03:fadvise64:2:posix_fadvise:2:
-＠:LDP man-pages:3.68:2014/05/03:fadvise64_64:2:posix_fadvise:2:
-☆:LDP man-pages:3.65=>3.68:2014/05/08:fallocate:2:2014/04/27::amotoki@gmail.com:Akihiro MOTOKI:
-×:LDP man-pages:3.68:2014/05/18:fanotify_init:2:::::
-×:LDP man-pages:3.68:2014/04/24:fanotify_mark:2:::::
-＠:LDP man-pages:3.68:2013/02/12:fattach:2:unimplemented:2:
-＠:LDP man-pages:3.68:2010/11/25:fchdir:2:chdir:2:
-＠:LDP man-pages:3.68:2014/02/21:fchmod:2:chmod:2:
-＠:LDP man-pages:3.68:2014/02/21:fchmodat:2:chmod:2:
-＠:LDP man-pages:3.68:2014/05/21:fchown:2:chown:2:
-＠:LDP man-pages:3.68:2014/05/21:fchown32:2:fchown:2:
-＠:LDP man-pages:3.68:2014/05/21:fchownat:2:chown:2:
-○:LDP man-pages:3.68:2014/05/21:fcntl:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/21:fcntl64:2:fcntl:2:
-＠:LDP man-pages:3.68:2014/04/06:fdatasync:2:fsync:2:
-＠:LDP man-pages:3.68:2013/02/12:fdetach:2:unimplemented:2:
-＠:LDP man-pages:3.68:2014/04/06:fgetxattr:2:getxattr:2:
-＠:LDP man-pages:3.68:2014/05/10:finit_module:2:init_module:2:
-＠:LDP man-pages:3.68:2014/02/06:flistxattr:2:listxattr:2:
-○:LDP man-pages:3.68:2014/04/22:flock:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/28:fork:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2007/05/31:free_hugepages:2:alloc_hugepages:2:
-＠:LDP man-pages:3.68:2014/02/06:fremovexattr:2:removexattr:2:
-＠:LDP man-pages:3.68:2014/02/06:fsetxattr:2:setxattr:2:
-＠:LDP man-pages:3.68:2014/05/10:fstat:2:stat:2:
-＠:LDP man-pages:3.68:2014/05/10:fstat64:2:fstat:2:
-＠:LDP man-pages:3.68:2014/05/10:fstatat:2:stat:2:
-＠:LDP man-pages:3.68:2014/05/10:fstatat64:2:fstatat:2:
-＠:LDP man-pages:3.68:2010/11/21:fstatfs:2:statfs:2:
-＠:LDP man-pages:3.68:2010/11/21:fstatfs64:2:fstatfs:2:
-＠:LDP man-pages:3.68:2013/09/26:fstatvfs:2:statvfs:3:
-○:LDP man-pages:3.68:2014/04/06:fsync:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/04/01:ftruncate:2:truncate:2:
-＠:LDP man-pages:3.68:2013/04/01:ftruncate64:2:ftruncate:2:
-○:LDP man-pages:3.68:2014/05/21:futex:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-☆:LDP man-pages:3.54=>3.68:2012/05/10:futimesat:2:2013/03/25::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/10/18:get_kernel_syms:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2008/08/15:get_mempolicy:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-×:LDP man-pages:3.68:2014/05/10:get_robust_list:2:::::
-○:LDP man-pages:3.68:2012/07/13:get_thread_area:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/04/08:getcontext:2:getcontext:3:
-○:LDP man-pages:3.68:2013/04/03:getcpu:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/20:getcwd:2:getcwd:3:
-○:LDP man-pages:3.68:2012/08/03:getdents:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2012/08/03:getdents64:2:getdents:2:
-○:LDP man-pages:3.68:2012/10/25:getdomainname:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:0000/00/00:getdtablesize:2:2007/01/14::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2010/11/22:getegid:2:getgid:2:
-＠:LDP man-pages:3.68:2010/11/22:getegid32:2:getegid:2:
-＠:LDP man-pages:3.68:2010/11/22:geteuid:2:getuid:2:
-＠:LDP man-pages:3.68:2010/11/22:geteuid32:2:geteuid:2:
-○:LDP man-pages:3.68:2010/11/22:getgid:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/11/22:getgid32:2:getgid:2:
-○:LDP man-pages:3.68:2013/10/18:getgroups:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/10/18:getgroups32:2:getgroups:2:
-＠:LDP man-pages:3.68:2010/09/20:gethostid:2:gethostid:3:
-○:LDP man-pages:3.68:2010/09/26:gethostname:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/10/01:getitimer:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/02/12:getmsg:2:unimplemented:2:
-○:LDP man-pages:3.68:2010/11/16:getpagesize:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/02/12:getpeername:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/07:getpgid:2:setpgid:2:
-＠:LDP man-pages:3.68:2014/01/07:getpgrp:2:setpgid:2:
-○:LDP man-pages:3.68:2008/09/23:getpid:2:2014/06/08::suto@av.crl.sony.co.jp:SUTO, Mitsuaki:
-＠:LDP man-pages:3.68:2013/02/12:getpmsg:2:unimplemented:2:
-＠:LDP man-pages:3.68:2008/09/23:getppid:2:getpid:2:
-○:LDP man-pages:3.68:2014/05/10:getpriority:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/11/22:getresgid:2:getresuid:2:
-＠:LDP man-pages:3.68:2010/11/22:getresgid32:2:getresgid:2:
-○:LDP man-pages:3.68:2010/11/22:getresuid:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/11/22:getresuid32:2:getresuid:2:
-○:LDP man-pages:3.68:2014/05/28:getrlimit:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/10:getrusage:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/09/26:getsid:2:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2008/12/03:getsockname:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2014/04/28:getsockopt:2:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2014/02/11:gettid:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/04/26:gettimeofday:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/11/22:getuid:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/11/22:getuid32:2:getuid:2:
-×:LDP man-pages:3.68:2013/02/13:getunwind:2:::::
-○:LDP man-pages:3.68:2014/04/06:getxattr:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/02/12:gtty:2:unimplemented:2:
-○:LDP man-pages:3.68:2012/12/31:idle:2:2014/06/08::argrath@yo.rim.or.jp:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2012/12/31:inb:2:outb:2:
-＠:LDP man-pages:3.68:2012/12/31:inb_p:2:outb:2:
-☆:LDP man-pages:3.41=>3.68:2014/05/10:init_module:2:2006/07/30::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2012/12/31:inl:2:outb:2:
-＠:LDP man-pages:3.68:2012/12/31:inl_p:2:outb:2:
-○:LDP man-pages:3.68:2014/03/28:inotify_add_watch:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/03/28:inotify_init:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/03/28:inotify_init1:2:inotify_init:2:
-○:LDP man-pages:3.68:2010/10/15:inotify_rm_watch:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2012/12/31:insb:2:outb:2:
-＠:LDP man-pages:3.68:2012/12/31:insl:2:outb:2:
-＠:LDP man-pages:3.68:2012/12/31:insw:2:outb:2:
-○:LDP man-pages:3.68:2014/02/20:intro:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2012/12/31:inw:2:outb:2:
-＠:LDP man-pages:3.68:2012/12/31:inw_p:2:outb:2:
-○:LDP man-pages:3.68:2013/04/10:io_cancel:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/04/08:io_destroy:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/04/08:io_getevents:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/06/21:io_setup:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/07/13:io_submit:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/11/08:ioctl:2:2014/06/08::tati@kc5.so-net.ne.jp:TACHIBANA Akira:
-○:LDP man-pages:3.68:2013/09/17:ioctl_list:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/03/12:ioperm:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/03/15:iopl:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/02/12:ioprio_get:2:ioprio_set:2:
-○:LDP man-pages:3.68:2013/02/12:ioprio_set:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/10/16:ipc:2:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-＠:LDP man-pages:3.68:2013/02/12:isastream:2:unimplemented:2:
-○:LDP man-pages:3.68:2013/12/08:kcmp:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/07/13:kexec_load:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-×:LDP man-pages:3.68:2014/01/22:keyctl:2:::::
-○:LDP man-pages:3.68:2013/09/17:kill:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/09/20:killpg:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2014/05/21:lchown:2:chown:2:
-＠:LDP man-pages:3.68:2014/05/21:lchown32:2:lchown:2:
-＠:LDP man-pages:3.68:2014/04/06:lgetxattr:2:getxattr:2:
-☆:LDP man-pages:3.65=>3.68:2014/05/10:link:2:2014/04/24::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2014/05/10:linkat:2:link:2:
-○:LDP man-pages:3.68:2014/05/10:listen:2:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2014/02/06:listxattr:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/02/06:llistxattr:2:listxattr:2:
-○:LDP man-pages:3.68:2012/07/13:llseek:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2013/02/12:lock:2:unimplemented:2:
-○:LDP man-pages:3.68:2004/06/17:lookup_dcookie:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/02/06:lremovexattr:2:removexattr:2:
-○:LDP man-pages:3.68:2014/01/22:lseek:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/02/06:lsetxattr:2:setxattr:2:
-＠:LDP man-pages:3.68:2014/05/10:lstat:2:stat:2:
-＠:LDP man-pages:3.68:2014/05/10:lstat64:2:lstat:2:
-○:LDP man-pages:3.68:2014/04/20:madvise:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/02/12:madvise1:2:unimplemented:2:
-○:LDP man-pages:3.68:2014/05/10:mbind:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/08/01:migrate_pages:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2008/04/22:mincore:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/21:mkdir:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/02/21:mkdirat:2:mkdir:2:
-○:LDP man-pages:3.68:2014/02/21:mknod:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/02/21:mknodat:2:mknod:2:
-○:LDP man-pages:3.68:2014/04/14:mlock:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/04/14:mlockall:2:mlock:2:
-○:LDP man-pages:3.68:2014/04/06:mmap:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/25:mmap2:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/07/13:modify_ldt:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/03/17:mount:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/06/11:move_pages:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/01/05:mprotect:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/02/12:mpx:2:unimplemented:2:
-○:LDP man-pages:3.68:2012/07/13:mq_getsetattr:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/04/06:mq_notify:2:mq_notify:3:
-＠:LDP man-pages:3.68:2009/02/20:mq_open:2:mq_open:3:
-＠:LDP man-pages:3.68:2014/01/18:mq_timedreceive:2:mq_receive:3:
-＠:LDP man-pages:3.68:2014/01/18:mq_timedsend:2:mq_send:3:
-＠:LDP man-pages:3.68:2010/08/29:mq_unlink:2:mq_unlink:3:
-○:LDP man-pages:3.68:2010/06/10:mremap:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/24:msgctl:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/04/30:msgget:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/16:msgop:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/16:msgrcv:2:msgop:2:
-＠:LDP man-pages:3.68:2014/05/16:msgsnd:2:msgop:2:
-○:LDP man-pages:3.68:2014/04/20:msync:2:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2014/04/14:munlock:2:mlock:2:
-＠:LDP man-pages:3.68:2014/04/14:munlockall:2:mlock:2:
-＠:LDP man-pages:3.68:2014/04/06:munmap:2:mmap:2:
-※:LDP man-pages:3.68:2014/05/08:name_to_handle_at:2:open_by_handle_at:2:
-○:LDP man-pages:3.68:2013/07/30:nanosleep:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/09/17:nfsservctl:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/04/28:nice:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/10:oldfstat:2:stat:2:
-＠:LDP man-pages:3.68:2014/05/10:oldlstat:2:stat:2:
-＠:LDP man-pages:3.68:2008/12/03:oldolduname:2:uname:2:
-＠:LDP man-pages:3.68:2014/05/10:oldstat:2:stat:2:
-＠:LDP man-pages:3.68:2008/12/03:olduname:2:uname:2:
-☆:LDP man-pages:3.65=>3.68:2014/05/10:open:2:2014/04/28::amotoki@gmail.com:Akihiro MOTOKI:
-×:LDP man-pages:3.68:2014/05/08:open_by_handle_at:2:::::
-＠:LDP man-pages:3.68:2014/05/10:openat:2:open:2:
-○:LDP man-pages:3.68:2012/12/31:outb:2:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2012/12/31:outb_p:2:outb:2:
-＠:LDP man-pages:3.68:2012/12/31:outl:2:outb:2:
-＠:LDP man-pages:3.68:2012/12/31:outl_p:2:outb:2:
-＠:LDP man-pages:3.68:2012/12/31:outsb:2:outb:2:
-＠:LDP man-pages:3.68:2012/12/31:outsl:2:outb:2:
-＠:LDP man-pages:3.68:2012/12/31:outsw:2:outb:2:
-＠:LDP man-pages:3.68:2012/12/31:outw:2:outb:2:
-＠:LDP man-pages:3.68:2012/12/31:outw_p:2:outb:2:
-○:LDP man-pages:3.68:2008/10/06:pause:2:2014/06/08::suto@av.crl.sony.co.jp:SUTO, Mitsuaki:
-＠:LDP man-pages:3.68:2003/07/14:pciconfig_iobase:2:pciconfig_read:2:
-○:LDP man-pages:3.68:2003/07/14:pciconfig_read:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2003/07/14:pciconfig_write:2:pciconfig_read:2:
-×:LDP man-pages:3.68:2014/04/17:perf_event_open:2:::::
-×:LDP man-pages:3.68:2013/02/13:perfmonctl:2:::::
-○:LDP man-pages:3.68:2014/04/15:personality:2:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2013/02/12:phys:2:unimplemented:2:
-○:LDP man-pages:3.68:2014/02/11:pipe:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/02/11:pipe2:2:pipe:2:
-○:LDP man-pages:3.68:2012/07/13:pivot_root:2:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2014/05/10:poll:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/03:posix_fadvise:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/10:ppoll:2:poll:2:
-☆:LDP man-pages:3.40=>3.68:2014/04/14:prctl:2:2012/05/26::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/06/21:pread:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/06/21:pread64:2:pread:2:
-＠:LDP man-pages:3.68:2010/11/17:preadv:2:readv:2:
-＠:LDP man-pages:3.68:2014/05/28:prlimit:2:getrlimit:2:
-×:LDP man-pages:3.68:2014/05/05:process_vm_readv:2:::::
-※:LDP man-pages:3.68:2014/05/05:process_vm_writev:2:process_vm_readv:2:
-＠:LDP man-pages:3.68:2013/02/12:prof:2:unimplemented:2:
-＠:LDP man-pages:3.68:2014/01/31:pselect:2:select:2:
-＠:LDP man-pages:3.68:2014/01/31:pselect6:2:select:2:
-×:LDP man-pages:3.68:2014/02/20:ptrace:2:::::
-＠:LDP man-pages:3.68:2013/02/12:putmsg:2:unimplemented:2:
-＠:LDP man-pages:3.68:2013/02/12:putpmsg:2:unimplemented:2:
-＠:LDP man-pages:3.68:2013/06/21:pwrite:2:pread:2:
-＠:LDP man-pages:3.68:2013/06/21:pwrite64:2:pwrite:2:
-＠:LDP man-pages:3.68:2010/11/17:pwritev:2:readv:2:
-☆:LDP man-pages:3.65=>3.68:2014/05/10:query_module:2:2014/04/24::amotoki@gmail.com:Akihiro MOTOKI:
-×:LDP man-pages:3.68:2010/06/16:quotactl:2:::::
-☆:LDP man-pages:3.65=>3.68:2014/05/04:read:2:2014/04/24::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/03/15:readahead:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/06/21:readdir:2:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-○:LDP man-pages:3.68:2014/05/10:readlink:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/10:readlinkat:2:readlink:2:
-○:LDP man-pages:3.68:2010/11/17:readv:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/12/28:reboot:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/10:recv:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/10:recvfrom:2:recv:2:
-○:LDP man-pages:3.68:2014/05/21:recvmmsg:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/10:recvmsg:2:recv:2:
-☆:LDP man-pages:3.65=>3.68:2014/05/28:remap_file_pages:2:2014/04/24::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/06:removexattr:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-☆:LDP man-pages:3.65=>3.68:2014/05/08:rename:2:2014/04/24::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/08:renameat:2:rename:2:
-＠:LDP man-pages:3.68:2014/05/08:renameat2:2:rename:2:
-×:LDP man-pages:3.68:2010/02/25:request_key:2:::::
-×:LDP man-pages:3.68:2014/02/11:restart_syscall:2:::::
-○:LDP man-pages:3.68:2008/05/08:rmdir:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/04/27:rt_sigaction:2:sigaction:2:
-＠:LDP man-pages:3.68:2013/12/11:rt_sigpending:2:sigpending:2:
-＠:LDP man-pages:3.68:2013/04/19:rt_sigprocmask:2:sigprocmask:2:
-×:LDP man-pages:3.68:2012/07/13:rt_sigqueueinfo:2:::::
-＠:LDP man-pages:3.68:2013/07/30:rt_sigreturn:2:sigreturn:2:
-＠:LDP man-pages:3.68:2013/04/19:rt_sigsuspend:2:sigsuspend:2:
-＠:LDP man-pages:3.68:2013/09/04:rt_sigtimedwait:2:sigtimedwait:2:
-※:LDP man-pages:3.68:2012/07/13:rt_tgsigqueueinfo:2:rt_sigqueueinfo:2:
-×:LDP man-pages:3.68:2012/12/17:s390_runtime_instr:2:::::
-＠:LDP man-pages:3.68:2010/09/20:sbrk:2:brk:2:
-○:LDP man-pages:3.68:2014/05/12:sched_get_priority_max:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/12:sched_get_priority_min:2:sched_get_priority_max:2:
-＠:LDP man-pages:3.68:2014/05/10:sched_getaffinity:2:sched_setaffinity:2:
-※:LDP man-pages:3.68:2014/05/13:sched_getattr:2:sched_setattr:2:
-＠:LDP man-pages:3.68:2014/05/11:sched_getparam:2:sched_setparam:2:
-＠:LDP man-pages:3.68:2014/05/21:sched_getscheduler:2:sched_setscheduler:2:
-○:LDP man-pages:3.68:2014/04/28:sched_rr_get_interval:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/10:sched_setaffinity:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-×:LDP man-pages:3.68:2014/05/13:sched_setattr:2:::::
-○:LDP man-pages:3.68:2014/05/11:sched_setparam:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-☆:LDP man-pages:3.65=>3.68:2014/05/21:sched_setscheduler:2:2014/04/24::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/04/28:sched_yield:2:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-＠:LDP man-pages:3.68:2013/02/12:security:2:unimplemented:2:
-○:LDP man-pages:3.68:2014/01/31:select:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/12/30:select_tut:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/06/03:semctl:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-☆:LDP man-pages:3.65=>3.68:2014/05/21:semget:2:2014/04/24::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/10:semop:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/10:semtimedop:2:semop:2:
-○:LDP man-pages:3.68:2014/05/10:send:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2011/09/14:sendfile:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2011/09/14:sendfile64:2:sendfile:2:
-○:LDP man-pages:3.68:2012/12/16:sendmmsg:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/10:sendmsg:2:send:2:
-＠:LDP man-pages:3.68:2014/05/10:sendto:2:send:2:
-○:LDP man-pages:3.68:2014/05/28:set_mempolicy:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-※:LDP man-pages:3.68:2014/05/10:set_robust_list:2:get_robust_list:2:
-○:LDP man-pages:3.68:2012/07/13:set_thread_area:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/07/19:set_tid_address:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2014/04/08:setcontext:2:getcontext:3:
-＠:LDP man-pages:3.68:2012/10/25:setdomainname:2:getdomainname:2:
-＠:LDP man-pages:3.68:2012/07/02:setegid:2:seteuid:2:
-○:LDP man-pages:3.68:2012/07/02:seteuid:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/08/08:setfsgid:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/08/08:setfsgid32:2:setfsgid:2:
-○:LDP man-pages:3.68:2013/08/08:setfsuid:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/08/08:setfsuid32:2:setfsuid:2:
-○:LDP man-pages:3.68:2010/11/22:setgid:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/11/22:setgid32:2:setgid:2:
-＠:LDP man-pages:3.68:2013/10/18:setgroups:2:getgroups:2:
-＠:LDP man-pages:3.68:2013/10/18:setgroups32:2:setgroups:2:
-＠:LDP man-pages:3.68:2010/09/20:sethostid:2:gethostid:3:
-＠:LDP man-pages:3.68:2010/09/26:sethostname:2:gethostname:2:
-＠:LDP man-pages:3.68:2012/10/01:setitimer:2:getitimer:2:
-○:LDP man-pages:3.68:2013/01/01:setns:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/01/07:setpgid:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/07:setpgrp:2:setpgid:2:
-＠:LDP man-pages:3.68:2014/05/10:setpriority:2:getpriority:2:
-＠:LDP man-pages:3.68:2013/12/12:setregid:2:setreuid:2:
-＠:LDP man-pages:3.68:2013/12/12:setregid32:2:setregid:2:
-＠:LDP man-pages:3.68:2010/11/22:setresgid:2:setresuid:2:
-＠:LDP man-pages:3.68:2010/11/22:setresgid32:2:setresgid:2:
-○:LDP man-pages:3.68:2010/11/22:setresuid:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/11/22:setresuid32:2:setresuid:2:
-○:LDP man-pages:3.68:2013/12/12:setreuid:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/12/12:setreuid32:2:setreuid:2:
-＠:LDP man-pages:3.68:2014/05/28:setrlimit:2:getrlimit:2:
-○:LDP man-pages:3.68:2013/02/11:setsid:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2014/04/28:setsockopt:2:getsockopt:2:
-＠:LDP man-pages:3.68:2012/04/26:settimeofday:2:gettimeofday:2:
-○:LDP man-pages:3.68:2010/11/22:setuid:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/11/22:setuid32:2:setuid:2:
-○:LDP man-pages:3.68:2008/12/03:setup:2:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2014/02/06:setxattr:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/25:sgetmask:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/04/28:shmat:2:shmop:2:
-○:LDP man-pages:3.68:2014/02/07:shmctl:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/04/28:shmdt:2:shmop:2:
-☆:LDP man-pages:3.65=>3.68:2014/05/21:shmget:2:2014/04/24::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-☆:LDP man-pages:3.65=>3.68:2014/04/28:shmop:2:2014/04/24::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/09/06:shutdown:2:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2014/04/27:sigaction:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/09/26:sigaltstack:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/04/19:signal:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2009/01/13:signalfd:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2009/01/13:signalfd4:2:signalfd:2:
-○:LDP man-pages:3.68:2013/12/11:sigpending:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/04/19:sigprocmask:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/12/16:sigqueue:2:sigqueue:3:
-○:LDP man-pages:3.68:2013/07/30:sigreturn:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/04/19:sigsuspend:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/09/04:sigtimedwait:2:sigwaitinfo:2:
-○:LDP man-pages:3.68:2013/09/04:sigwaitinfo:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/12/31:socket:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/10/16:socketcall:2:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-○:LDP man-pages:3.68:2008/10/11:socketpair:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/05/04:splice:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/08/05:spu_create:2:2014/06/08::amotoki@gmail.com:Akihiro Motoki:
-○:LDP man-pages:3.68:2012/08/05:spu_run:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/02/25:ssetmask:2:sgetmask:2:
-○:LDP man-pages:3.68:2014/05/10:stat:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/10:stat64:2:stat:2:
-○:LDP man-pages:3.68:2010/11/21:statfs:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/11/21:statfs64:2:statfs:2:
-＠:LDP man-pages:3.68:2013/09/26:statvfs:2:statvfs:3:
-○:LDP man-pages:3.68:2014/05/10:stime:2:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2013/02/12:stty:2:unimplemented:2:
-×:LDP man-pages:3.68:2012/07/13:subpage_prot:2:::::
-＠:LDP man-pages:3.68:2014/05/28:swapoff:2:swapon:2:
-○:LDP man-pages:3.68:2014/05/28:swapon:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-☆:LDP man-pages:3.65=>3.68:2014/05/05:symlink:2:2014/04/24::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2014/05/05:symlinkat:2:symlink:2:
-○:LDP man-pages:3.68:2014/04/06:sync:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/04/01:sync_file_range:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/04/01:sync_file_range2:2:sync_file_range:2:
-＠:LDP man-pages:3.68:2014/04/06:syncfs:2:sync:2:
-○:LDP man-pages:3.68:2014/05/10:syscall:2:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2014/05/08:syscalls:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/12/22:sysctl:2:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-○:LDP man-pages:3.68:2010/06/27:sysfs:2:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2012/05/05:sysinfo:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/11/29:syslog:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/05/04:tee:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2012/07/13:tgkill:2:tkill:2:
-○:LDP man-pages:3.68:2011/09/09:time:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-×:LDP man-pages:3.68:2014/01/20:timer_create:2:::::
-○:LDP man-pages:3.68:2009/02/20:timer_delete:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-×:LDP man-pages:3.68:2009/02/20:timer_getoverrun:2:::::
-※:LDP man-pages:3.68:2012/10/15:timer_gettime:2:timer_settime:2:
-×:LDP man-pages:3.68:2012/10/15:timer_settime:2:::::
-○:LDP man-pages:3.68:2011/09/14:timerfd_create:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2011/09/14:timerfd_gettime:2:timerfd_create:2:
-＠:LDP man-pages:3.68:2011/09/14:timerfd_settime:2:timerfd_create:2:
-○:LDP man-pages:3.68:2012/10/22:times:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/07/13:tkill:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/04/01:truncate:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/04/01:truncate64:2:truncate:2:
-＠:LDP man-pages:3.68:2013/02/12:tuxcall:2:unimplemented:2:
-＠:LDP man-pages:3.68:2014/05/28:ugetrlimit:2:getrlimit:2:
-○:LDP man-pages:3.68:2008/01/09:umask:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/26:umount:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/02/26:umount2:2:umount:2:
-○:LDP man-pages:3.68:2008/12/03:uname:2:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2013/02/12:unimplemented:2:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-○:LDP man-pages:3.68:2014/02/21:unlink:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/02/21:unlinkat:2:unlink:2:
-○:LDP man-pages:3.68:2013/04/17:unshare:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2005/01/09:uselib:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2003/08/04:ustat:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2014/02/21:utime:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-×:LDP man-pages:3.68:2014/01/24:utimensat:2:::::
-＠:LDP man-pages:3.68:2014/02/21:utimes:2:utime:2:
-○:LDP man-pages:3.68:2012/08/05:vfork:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2007/07/26:vhangup:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2009/02/20:vm86:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2009/02/20:vm86old:2:vm86:2:
-○:LDP man-pages:3.68:2012/05/04:vmsplice:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/02/12:vserver:2:unimplemented:2:
-○:LDP man-pages:3.68:2013/09/04:wait:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2012/09/23:wait3:2:wait4:2:
-○:LDP man-pages:3.68:2012/09/23:wait4:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/09/04:waitid:2:wait:2:
-＠:LDP man-pages:3.68:2013/09/04:waitpid:2:wait:2:
-☆:LDP man-pages:3.65=>3.68:2014/05/04:write:2:2014/04/24::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/11/17:writev:2:readv:2:
-＠:LDP man-pages:3.68:2007/12/28:CIRCLEQ_ENTRY:3:queue:3:
-＠:LDP man-pages:3.68:2007/12/28:CIRCLEQ_HEAD:3:queue:3:
-＠:LDP man-pages:3.68:2007/12/28:CIRCLEQ_INIT:3:queue:3:
-＠:LDP man-pages:3.68:2007/12/28:CIRCLEQ_INSERT_AFTER:3:queue:3:
-＠:LDP man-pages:3.68:2007/12/28:CIRCLEQ_INSERT_BEFORE:3:queue:3:
-＠:LDP man-pages:3.68:2007/12/28:CIRCLEQ_INSERT_HEAD:3:queue:3:
-＠:LDP man-pages:3.68:2007/12/28:CIRCLEQ_INSERT_TAIL:3:queue:3:
-＠:LDP man-pages:3.68:2007/12/28:CIRCLEQ_REMOVE:3:queue:3:
-＠:LDP man-pages:3.68:2008/11/20:CMSG_ALIGN:3:cmsg:3:
-＠:LDP man-pages:3.68:2008/11/20:CMSG_FIRSTHDR:3:cmsg:3:
-＠:LDP man-pages:3.68:2008/11/20:CMSG_NXTHDR:3:cmsg:3:
-＠:LDP man-pages:3.68:2008/11/20:CMSG_SPACE:3:cmsg:3:
-＠:LDP man-pages:3.68:2012/03/15:CPU_ALLOC:3:CPU_SET:3:
-＠:LDP man-pages:3.68:2012/03/15:CPU_ALLOC_SIZE:3:CPU_SET:3:
-＠:LDP man-pages:3.68:2012/03/15:CPU_AND:3:CPU_SET:3:
-＠:LDP man-pages:3.68:2012/03/15:CPU_AND_S:3:CPU_SET:3:
-＠:LDP man-pages:3.68:2012/03/15:CPU_CLR:3:CPU_SET:3:
-＠:LDP man-pages:3.68:2012/03/15:CPU_CLR_S:3:CPU_SET:3:
-＠:LDP man-pages:3.68:2012/03/15:CPU_COUNT:3:CPU_SET:3:
-＠:LDP man-pages:3.68:2012/03/15:CPU_COUNT_S:3:CPU_SET:3:
-＠:LDP man-pages:3.68:2012/03/15:CPU_EQUAL:3:CPU_SET:3:
-＠:LDP man-pages:3.68:2012/03/15:CPU_EQUAL_S:3:CPU_SET:3:
-＠:LDP man-pages:3.68:2012/03/15:CPU_FREE:3:CPU_SET:3:
-＠:LDP man-pages:3.68:2012/03/15:CPU_ISSET:3:CPU_SET:3:
-＠:LDP man-pages:3.68:2012/03/15:CPU_ISSET_S:3:CPU_SET:3:
-＠:LDP man-pages:3.68:2012/03/15:CPU_OR:3:CPU_SET:3:
-＠:LDP man-pages:3.68:2012/03/15:CPU_OR_S:3:CPU_SET:3:
-○:LDP man-pages:3.68:2012/03/15:CPU_SET:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2012/03/15:CPU_SET_S:3:CPU_SET:3:
-＠:LDP man-pages:3.68:2012/03/15:CPU_XOR:3:CPU_SET:3:
-＠:LDP man-pages:3.68:2012/03/15:CPU_XOR_S:3:CPU_SET:3:
-＠:LDP man-pages:3.68:2012/03/15:CPU_ZERO:3:CPU_SET:3:
-＠:LDP man-pages:3.68:2012/03/15:CPU_ZERO_S:3:CPU_SET:3:
-＠:LDP man-pages:3.68:2013/09/18:DES_FAILED:3:des_crypt:3:
-＠:LDP man-pages:3.68:2014/01/31:FD_CLR:3:select:2:
-＠:LDP man-pages:3.68:2014/01/31:FD_ISSET:3:select:2:
-＠:LDP man-pages:3.68:2014/01/31:FD_SET:3:select:2:
-＠:LDP man-pages:3.68:2014/01/31:FD_ZERO:3:select:2:
-＠:LDP man-pages:3.68:2007/07/26:HUGE_VAL:3:INFINITY:3:
-＠:LDP man-pages:3.68:2007/07/26:HUGE_VALF:3:INFINITY:3:
-＠:LDP man-pages:3.68:2007/07/26:HUGE_VALL:3:INFINITY:3:
-○:LDP man-pages:3.68:2007/07/26:INFINITY:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2007/12/28:LIST_ENTRY:3:queue:3:
-＠:LDP man-pages:3.68:2007/12/28:LIST_HEAD:3:queue:3:
-＠:LDP man-pages:3.68:2007/12/28:LIST_INIT:3:queue:3:
-＠:LDP man-pages:3.68:2007/12/28:LIST_INSERT_AFTER:3:queue:3:
-＠:LDP man-pages:3.68:2007/12/28:LIST_INSERT_HEAD:3:queue:3:
-＠:LDP man-pages:3.68:2007/12/28:LIST_REMOVE:3:queue:3:
-○:LDP man-pages:3.68:1999/07/04:MB_CUR_MAX:3:2014/06/08::cz8cb01@linux.or.jp:HAYAKAWA Hitoshi:
-○:LDP man-pages:3.68:1999/07/04:MB_LEN_MAX:3:2014/06/08::cz8cb01@linux.or.jp:HAYAKAWA Hitoshi:
-＠:LDP man-pages:3.68:2007/07/26:NAN:3:INFINITY:3:
-＠:LDP man-pages:3.68:2007/12/28:TAILQ_ENTRY:3:queue:3:
-＠:LDP man-pages:3.68:2007/12/28:TAILQ_HEAD:3:queue:3:
-＠:LDP man-pages:3.68:2007/12/28:TAILQ_INIT:3:queue:3:
-＠:LDP man-pages:3.68:2007/12/28:TAILQ_INSERT_AFTER:3:queue:3:
-＠:LDP man-pages:3.68:2007/12/28:TAILQ_INSERT_HEAD:3:queue:3:
-＠:LDP man-pages:3.68:2007/12/28:TAILQ_INSERT_TAIL:3:queue:3:
-＠:LDP man-pages:3.68:2007/12/28:TAILQ_REMOVE:3:queue:3:
-＠:LDP man-pages:3.68:2010/10/13:__after_morecore_hook:3:malloc_hook:3:
-＠:LDP man-pages:3.68:2013/06/21:__fbufsize:3:stdio_ext:3:
-＠:LDP man-pages:3.68:2013/06/21:__flbf:3:stdio_ext:3:
-＠:LDP man-pages:3.68:2013/06/21:__fpending:3:stdio_ext:3:
-＠:LDP man-pages:3.68:2001/12/15:__fpurge:3:fpurge:3:
-＠:LDP man-pages:3.68:2013/06/21:__freadable:3:stdio_ext:3:
-＠:LDP man-pages:3.68:2013/06/21:__freading:3:stdio_ext:3:
-＠:LDP man-pages:3.68:2010/10/13:__free_hook:3:malloc_hook:3:
-＠:LDP man-pages:3.68:2013/06/21:__fsetlocking:3:stdio_ext:3:
-＠:LDP man-pages:3.68:2013/06/21:__fwritable:3:stdio_ext:3:
-＠:LDP man-pages:3.68:2013/06/21:__fwriting:3:stdio_ext:3:
-＠:LDP man-pages:3.68:2010/10/13:__malloc_hook:3:malloc_hook:3:
-＠:LDP man-pages:3.68:2010/10/13:__malloc_initialize_hook:3:malloc_hook:3:
-＠:LDP man-pages:3.68:2010/10/13:__memalign_hook:3:malloc_hook:3:
-＠:LDP man-pages:3.68:2010/10/13:__realloc_hook:3:malloc_hook:3:
-○:LDP man-pages:3.68:2012/12/31:__setfpucw:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-＠:LDP man-pages:3.68:2013/06/21:_flushlbf:3:stdio_ext:3:
-○:LDP man-pages:3.68:2014/05/28:a64l:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2014/03/25:abort:3:2014/06/08::tyoshino@eng.toyo.ac.jp:Takashi Yoshino:
-○:LDP man-pages:3.68:2013/06/21:abs:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/09/20:acos:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/20:acosf:3:acos:3:
-○:LDP man-pages:3.68:2010/09/20:acosh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/20:acoshf:3:acosh:3:
-＠:LDP man-pages:3.68:2010/09/20:acoshl:3:acosh:3:
-＠:LDP man-pages:3.68:2010/09/20:acosl:3:acos:3:
-＠:LDP man-pages:3.68:2009/09/15:addmntent:3:getmntent:3:
-○:LDP man-pages:3.68:2008/06/14:addseverity:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2014/05/28:adjtime:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/05/08:aio_cancel:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/07/04:aio_error:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/05/08:aio_fsync:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/04/26:aio_init:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/05/08:aio_read:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/07/04:aio_return:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/05/08:aio_suspend:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/05/08:aio_write:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/09/02:aligned_alloc:3:posix_memalign:3:
-○:LDP man-pages:3.68:2013/10/07:alloca:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2014/05/28:alphasort:3:scandir:3:
-＠:LDP man-pages:3.68:2014/05/28:argz:3:argz_add:3:
-○:LDP man-pages:3.68:2014/05/28:argz_add:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:argz_add_sep:3:argz_add:3:
-＠:LDP man-pages:3.68:2014/05/28:argz_append:3:argz_add:3:
-＠:LDP man-pages:3.68:2014/05/28:argz_count:3:argz_add:3:
-＠:LDP man-pages:3.68:2014/05/28:argz_create:3:argz_add:3:
-＠:LDP man-pages:3.68:2014/05/28:argz_create_sep:3:argz_add:3:
-＠:LDP man-pages:3.68:2014/05/28:argz_delete:3:argz_add:3:
-＠:LDP man-pages:3.68:2014/05/28:argz_extract:3:argz_add:3:
-＠:LDP man-pages:3.68:2014/05/28:argz_insert:3:argz_add:3:
-＠:LDP man-pages:3.68:2014/05/28:argz_next:3:argz_add:3:
-＠:LDP man-pages:3.68:2014/05/28:argz_replace:3:argz_add:3:
-＠:LDP man-pages:3.68:2014/05/28:argz_stringify:3:argz_add:3:
-＠:LDP man-pages:3.68:2013/12/30:asctime:3:ctime:3:
-＠:LDP man-pages:3.68:2013/12/30:asctime_r:3:ctime:3:
-○:LDP man-pages:3.68:2010/09/20:asin:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/20:asinf:3:asin:3:
-○:LDP man-pages:3.68:2013/10/14:asinh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/10/14:asinhf:3:asinh:3:
-＠:LDP man-pages:3.68:2013/10/14:asinhl:3:asinh:3:
-＠:LDP man-pages:3.68:2010/09/20:asinl:3:asin:3:
-○:LDP man-pages:3.68:2013/06/21:asprintf:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2013/09/26:assert:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2013/09/26:assert_perror:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/10/07:atan:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/09/20:atan2:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/20:atan2f:3:atan2:3:
-＠:LDP man-pages:3.68:2010/09/20:atan2l:3:atan2:3:
-＠:LDP man-pages:3.68:2013/10/07:atanf:3:atan:3:
-○:LDP man-pages:3.68:2010/09/11:atanh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/11:atanhf:3:atanh:3:
-＠:LDP man-pages:3.68:2010/09/11:atanhl:3:atanh:3:
-＠:LDP man-pages:3.68:2013/10/07:atanl:3:atan:3:
-○:LDP man-pages:3.68:2008/12/05:atexit:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/01/22:atof:3:2014/06/08::tyoshino@eng.toyo.ac.jp:Takashi Yoshino:
-○:LDP man-pages:3.68:2014/01/22:atoi:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2014/01/22:atol:3:atoi:3:
-＠:LDP man-pages:3.68:2014/01/22:atoll:3:atoi:3:
-＠:LDP man-pages:3.68:2014/01/22:atoq:3:atoi:3:
-＠:LDP man-pages:3.68:2013/09/26:auth_destroy:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:authnone_create:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:authunix_create:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:authunix_create_default:3:rpc:3:
-○:LDP man-pages:3.68:2008/06/14:backtrace:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/06/14:backtrace_symbols:3:backtrace:3:
-＠:LDP man-pages:3.68:2008/06/14:backtrace_symbols_fd:3:backtrace:3:
-○:LDP man-pages:3.68:2009/03/30:basename:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/10/21:bcmp:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2013/10/22:bcopy:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2010/09/10:be16toh:3:endian:3:
-＠:LDP man-pages:3.68:2010/09/10:be32toh:3:endian:3:
-＠:LDP man-pages:3.68:2010/09/10:be64toh:3:endian:3:
-○:LDP man-pages:3.68:2013/06/21:bindresvport:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/10/22:bsd_signal:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2003/11/01:bsearch:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/28:bstring:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2011/09/22:btowc:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/04/23:btree:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/04/08:byteorder:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/10/22:bzero:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2008/08/11:cabs:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/08/11:cabsf:3:cabs:3:
-＠:LDP man-pages:3.68:2008/08/11:cabsl:3:cabs:3:
-○:LDP man-pages:3.68:2011/09/15:cacos:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2011/09/15:cacosf:3:cacos:3:
-○:LDP man-pages:3.68:2011/09/15:cacosh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2011/09/15:cacoshf:3:cacosh:3:
-＠:LDP man-pages:3.68:2011/09/15:cacoshl:3:cacosh:3:
-＠:LDP man-pages:3.68:2011/09/15:cacosl:3:cacos:3:
-＠:LDP man-pages:3.68:2014/05/21:calloc:3:malloc:3:
-＠:LDP man-pages:3.68:2013/09/26:callrpc:3:rpc:3:
-○:LDP man-pages:3.68:2013/05/11:canonicalize_file_name:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2008/08/11:carg:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/08/11:cargf:3:carg:3:
-＠:LDP man-pages:3.68:2008/08/11:cargl:3:carg:3:
-○:LDP man-pages:3.68:2008/08/11:casin:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/08/11:casinf:3:casin:3:
-○:LDP man-pages:3.68:2008/08/11:casinh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/08/11:casinhf:3:casinh:3:
-＠:LDP man-pages:3.68:2008/08/11:casinhl:3:casinh:3:
-＠:LDP man-pages:3.68:2008/08/11:casinl:3:casin:3:
-○:LDP man-pages:3.68:2011/09/15:catan:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2011/09/15:catanf:3:catan:3:
-○:LDP man-pages:3.68:2011/09/15:catanh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2011/09/15:catanhf:3:catanh:3:
-＠:LDP man-pages:3.68:2011/09/15:catanhl:3:catanh:3:
-＠:LDP man-pages:3.68:2011/09/15:catanl:3:catan:3:
-＠:LDP man-pages:3.68:2001/12/14:catclose:3:catopen:3:
-○:LDP man-pages:3.68:2013/06/21:catgets:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2001/12/14:catopen:3:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2013/09/18:cbc_crypt:3:des_crypt:3:
-○:LDP man-pages:3.68:2013/09/18:cbrt:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/09/18:cbrtf:3:cbrt:3:
-＠:LDP man-pages:3.68:2013/09/18:cbrtl:3:cbrt:3:
-○:LDP man-pages:3.68:2008/08/11:ccos:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/08/11:ccosf:3:ccos:3:
-○:LDP man-pages:3.68:2008/08/11:ccosh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/08/11:ccoshf:3:ccosh:3:
-＠:LDP man-pages:3.68:2008/08/11:ccoshl:3:ccosh:3:
-＠:LDP man-pages:3.68:2008/08/11:ccosl:3:ccos:3:
-○:LDP man-pages:3.68:2013/06/21:ceil:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/06/21:ceilf:3:ceil:3:
-＠:LDP man-pages:3.68:2013/06/21:ceill:3:ceil:3:
-○:LDP man-pages:3.68:2010/09/12:cerf:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/12:cerfc:3:cerf:3:
-＠:LDP man-pages:3.68:2010/09/12:cerfcf:3:cerf:3:
-＠:LDP man-pages:3.68:2010/09/12:cerfcl:3:cerf:3:
-＠:LDP man-pages:3.68:2010/09/12:cerff:3:cerf:3:
-＠:LDP man-pages:3.68:2010/09/12:cerfl:3:cerf:3:
-○:LDP man-pages:3.68:2008/08/11:cexp:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/02/27:cexp2:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/02/27:cexp2f:3:cexp2:3:
-＠:LDP man-pages:3.68:2013/02/27:cexp2l:3:cexp2:3:
-＠:LDP man-pages:3.68:2008/08/11:cexpf:3:cexp:3:
-＠:LDP man-pages:3.68:2008/08/11:cexpl:3:cexp:3:
-＠:LDP man-pages:3.68:2014/05/08:cfgetispeed:3:termios:3:
-＠:LDP man-pages:3.68:2014/05/08:cfgetospeed:3:termios:3:
-＠:LDP man-pages:3.68:2014/05/08:cfmakeraw:3:termios:3:
-○:LDP man-pages:3.68:2007/07/26:cfree:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2014/05/08:cfsetispeed:3:termios:3:
-＠:LDP man-pages:3.68:2014/05/08:cfsetospeed:3:termios:3:
-＠:LDP man-pages:3.68:2014/05/08:cfsetspeed:3:termios:3:
-○:LDP man-pages:3.68:2013/06/21:cimag:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/06/21:cimagf:3:cimag:3:
-＠:LDP man-pages:3.68:2013/06/21:cimagl:3:cimag:3:
-○:LDP man-pages:3.68:2010/10/04:clearenv:3:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2014/01/15:clearerr:3:ferror:3:
-＠:LDP man-pages:3.68:2008/08/29:clearerr_unlocked:3:unlocked_stdio:3:
-＠:LDP man-pages:3.68:2013/09/26:clnt_broadcast:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:clnt_call:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:clnt_control:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:clnt_create:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:clnt_destroy:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:clnt_freeres:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:clnt_geterr:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:clnt_pcreateerror:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:clnt_perrno:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:clnt_perror:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:clnt_spcreateerror:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:clnt_sperrno:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:clnt_sperror:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:clntraw_create:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:clnttcp_create:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:clntudp_bufcreate:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:clntudp_create:3:rpc:3:
-○:LDP man-pages:3.68:2013/08/19:clock:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/07/04:clock_getcpuclockid:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/12/28:clock_getres:3:clock_getres:2:
-＠:LDP man-pages:3.68:2013/12/28:clock_gettime:3:clock_getres:2:
-＠:LDP man-pages:3.68:2013/12/28:clock_settime:3:clock_getres:2:
-○:LDP man-pages:3.68:2008/08/11:clog:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2008/08/11:clog10:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/08/11:clog10f:3:clog10:3:
-＠:LDP man-pages:3.68:2008/08/11:clog10l:3:clog10:3:
-○:LDP man-pages:3.68:2013/07/23:clog2:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/07/23:clog2f:3:clog2:3:
-＠:LDP man-pages:3.68:2013/07/23:clog2l:3:clog2:3:
-＠:LDP man-pages:3.68:2008/08/11:clogf:3:clog:3:
-＠:LDP man-pages:3.68:2008/08/11:clogl:3:clog:3:
-○:LDP man-pages:3.68:2008/09/23:closedir:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2012/08/17:closelog:3:syslog:3:
-○:LDP man-pages:3.68:2008/11/20:cmsg:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2014/03/20:confstr:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/06/21:conj:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/06/21:conjf:3:conj:3:
-＠:LDP man-pages:3.68:2013/06/21:conjl:3:conj:3:
-○:LDP man-pages:3.68:2013/10/14:copysign:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/10/14:copysignf:3:copysign:3:
-＠:LDP man-pages:3.68:2013/10/14:copysignl:3:copysign:3:
-○:LDP man-pages:3.68:2013/10/14:cos:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/10/14:cosf:3:cos:3:
-○:LDP man-pages:3.68:2010/09/20:cosh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/20:coshf:3:cosh:3:
-＠:LDP man-pages:3.68:2010/09/20:coshl:3:cosh:3:
-＠:LDP man-pages:3.68:2013/10/14:cosl:3:cos:3:
-○:LDP man-pages:3.68:2008/08/11:cpow:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/08/11:cpowf:3:cpow:3:
-＠:LDP man-pages:3.68:2008/08/11:cpowl:3:cpow:3:
-○:LDP man-pages:3.68:2013/09/18:cproj:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/09/18:cprojf:3:cproj:3:
-＠:LDP man-pages:3.68:2013/09/18:cprojl:3:cproj:3:
-○:LDP man-pages:3.68:2013/09/18:creal:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/09/18:crealf:3:creal:3:
-＠:LDP man-pages:3.68:2013/09/18:creall:3:creal:3:
-○:LDP man-pages:3.68:2014/02/26:crypt:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2014/02/26:crypt_r:3:crypt:3:
-○:LDP man-pages:3.68:2008/08/11:csin:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/08/11:csinf:3:csin:3:
-○:LDP man-pages:3.68:2008/08/11:csinh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/08/11:csinhf:3:csinh:3:
-＠:LDP man-pages:3.68:2008/08/11:csinhl:3:csinh:3:
-＠:LDP man-pages:3.68:2008/08/11:csinl:3:csin:3:
-○:LDP man-pages:3.68:2008/08/11:csqrt:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/08/11:csqrtf:3:csqrt:3:
-＠:LDP man-pages:3.68:2008/08/11:csqrtl:3:csqrt:3:
-○:LDP man-pages:3.68:2008/08/11:ctan:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/08/11:ctanf:3:ctan:3:
-○:LDP man-pages:3.68:2008/08/11:ctanh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/08/11:ctanhf:3:ctanh:3:
-＠:LDP man-pages:3.68:2008/08/11:ctanhl:3:ctanh:3:
-＠:LDP man-pages:3.68:2008/08/11:ctanl:3:ctan:3:
-○:LDP man-pages:3.68:2013/07/04:ctermid:3:2014/06/08::nagoya@cc.hit-u.ac.jp:NAGOYA Hiroaki:
-○:LDP man-pages:3.68:2013/12/30:ctime:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/12/30:ctime_r:3:ctime:3:
-＠:LDP man-pages:3.68:2013/04/19:cuserid:3:getlogin:3:
-○:LDP man-pages:3.68:2013/10/28:daemon:3:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2012/03/25:daylight:3:tzset:3:
-＠:LDP man-pages:3.68:2012/05/04:db:3:dbopen:3:
-○:LDP man-pages:3.68:2012/05/04:dbopen:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/09/18:des_crypt:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2013/09/18:des_setparity:3:des_crypt:3:
-○:LDP man-pages:3.68:2013/10/28:difftime:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/07/05:dirfd:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2009/03/30:dirname:3:basename:3:
-○:LDP man-pages:3.68:2013/07/05:div:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2007/05/18:dl_iterate_phdr:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2014/01/08:dladdr:3:dlopen:3:
-＠:LDP man-pages:3.68:2014/01/08:dlclose:3:dlopen:3:
-＠:LDP man-pages:3.68:2014/01/08:dlerror:3:dlopen:3:
-○:LDP man-pages:3.68:2014/01/08:dlopen:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/08:dlsym:3:dlopen:3:
-＠:LDP man-pages:3.68:2014/01/08:dlvsym:3:dlopen:3:
-＠:LDP man-pages:3.68:2014/05/28:dn_comp:3:resolver:3:
-＠:LDP man-pages:3.68:2014/05/28:dn_expand:3:resolver:3:
-○:LDP man-pages:3.68:2010/09/15:dprintf:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2013/06/21:drand48:3:2014/06/08::tyoshino@eng.toyo.ac.jp:YOSHINO Takashi:
-○:LDP man-pages:3.68:2013/09/09:drand48_r:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2010/09/20:drem:3:remainder:3:
-＠:LDP man-pages:3.68:2010/09/20:dremf:3:remainder:3:
-＠:LDP man-pages:3.68:2010/09/20:dreml:3:remainder:3:
-○:LDP man-pages:3.68:2014/03/12:duplocale:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/09/25:dysize:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-＠:LDP man-pages:3.68:2013/09/25:eaccess:3:euidaccess:3:
-＠:LDP man-pages:3.68:2013/09/18:ecb_crypt:3:des_crypt:3:
-○:LDP man-pages:3.68:2013/07/04:ecvt:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2007/07/26:ecvt_r:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/07/17:edata:3:end:3:
-○:LDP man-pages:3.68:2013/07/22:encrypt:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2013/07/22:encrypt_r:3:encrypt:3:
-○:LDP man-pages:3.68:2008/07/17:end:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2003/09/09:endaliasent:3:setaliasent:3:
-＠:LDP man-pages:3.68:2002/02/28:endfsent:3:getfsent:3:
-＠:LDP man-pages:3.68:2013/06/21:endgrent:3:getgrent:3:
-＠:LDP man-pages:3.68:2014/03/11:endhostent:3:gethostbyname:3:
-○:LDP man-pages:3.68:2010/09/10:endian:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2009/09/15:endmntent:3:getmntent:3:
-＠:LDP man-pages:3.68:2008/08/19:endnetent:3:getnetent:3:
-＠:LDP man-pages:3.68:2014/05/28:endnetgrent:3:setnetgrent:3:
-＠:LDP man-pages:3.68:2008/08/19:endprotoent:3:getprotoent:3:
-＠:LDP man-pages:3.68:2013/06/21:endpwent:3:getpwent:3:
-＠:LDP man-pages:3.68:2014/05/28:endrpcent:3:getrpcent:3:
-＠:LDP man-pages:3.68:2008/08/19:endservent:3:getservent:3:
-＠:LDP man-pages:3.68:2014/05/28:endspent:3:getspnam:3:
-＠:LDP man-pages:3.68:2013/07/22:endttyent:3:getttyent:3:
-＠:LDP man-pages:3.68:2013/06/21:endusershell:3:getusershell:3:
-＠:LDP man-pages:3.68:2014/05/28:endutent:3:getutent:3:
-＠:LDP man-pages:3.68:2014/05/28:endutxent:3:getutent:3:
-＠:LDP man-pages:3.68:2014/05/28:envz:3:envz_add:3:
-○:LDP man-pages:3.68:2014/05/28:envz_add:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:envz_entry:3:envz_add:3:
-＠:LDP man-pages:3.68:2014/05/28:envz_get:3:envz_add:3:
-＠:LDP man-pages:3.68:2014/05/28:envz_merge:3:envz_add:3:
-＠:LDP man-pages:3.68:2014/05/28:envz_remove:3:envz_add:3:
-＠:LDP man-pages:3.68:2014/05/28:envz_strip:3:envz_add:3:
-＠:LDP man-pages:3.68:2013/06/21:erand48:3:drand48:3:
-＠:LDP man-pages:3.68:2013/09/09:erand48_r:3:drand48_r:3:
-○:LDP man-pages:3.68:2013/10/29:erf:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/10/29:erfc:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/10/29:erfcf:3:erfc:3:
-＠:LDP man-pages:3.68:2013/10/29:erfcl:3:erfc:3:
-＠:LDP man-pages:3.68:2013/10/29:erff:3:erf:3:
-＠:LDP man-pages:3.68:2013/10/29:erfl:3:erf:3:
-○:LDP man-pages:3.68:2013/12/30:err:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2008/07/09:errno:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/08/29:error:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/08/29:error_at_line:3:error:3:
-＠:LDP man-pages:3.68:2010/08/29:error_message_count:3:error:3:
-＠:LDP man-pages:3.68:2010/08/29:error_one_per_line:3:error:3:
-＠:LDP man-pages:3.68:2010/08/29:error_print_progname:3:error:3:
-＠:LDP man-pages:3.68:2013/12/30:errx:3:err:3:
-＠:LDP man-pages:3.68:2008/07/17:etext:3:end:3:
-○:LDP man-pages:3.68:2013/07/04:ether_aton:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/07/04:ether_aton_r:3:ether_aton:3:
-＠:LDP man-pages:3.68:2013/07/04:ether_hostton:3:ether_aton:3:
-＠:LDP man-pages:3.68:2013/07/04:ether_line:3:ether_aton:3:
-＠:LDP man-pages:3.68:2013/07/04:ether_ntoa:3:ether_aton:3:
-＠:LDP man-pages:3.68:2013/07/04:ether_ntoa_r:3:ether_aton:3:
-＠:LDP man-pages:3.68:2013/07/04:ether_ntohost:3:ether_aton:3:
-○:LDP man-pages:3.68:2013/09/25:euidaccess:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/08/30:eventfd_read:3:eventfd:2:
-＠:LDP man-pages:3.68:2010/08/30:eventfd_write:3:eventfd:2:
-○:LDP man-pages:3.68:2010/09/25:exec:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/25:execl:3:exec:3:
-＠:LDP man-pages:3.68:2010/09/25:execle:3:exec:3:
-＠:LDP man-pages:3.68:2010/09/25:execlp:3:exec:3:
-＠:LDP man-pages:3.68:2010/09/25:execv:3:exec:3:
-＠:LDP man-pages:3.68:2010/09/25:execvp:3:exec:3:
-＠:LDP man-pages:3.68:2010/09/25:execvpe:3:exec:3:
-○:LDP man-pages:3.68:2014/03/25:exit:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/09/20:exp:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2008/08/11:exp10:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/08/11:exp10f:3:exp10:3:
-＠:LDP man-pages:3.68:2008/08/11:exp10l:3:exp10:3:
-○:LDP man-pages:3.68:2010/09/20:exp2:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/20:exp2f:3:exp2:3:
-＠:LDP man-pages:3.68:2010/09/20:exp2l:3:exp2:3:
-＠:LDP man-pages:3.68:2010/09/20:expf:3:exp:3:
-＠:LDP man-pages:3.68:2010/09/20:expl:3:exp:3:
-○:LDP man-pages:3.68:2013/10/14:expm1:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/10/14:expm1f:3:expm1:3:
-＠:LDP man-pages:3.68:2013/10/14:expm1l:3:expm1:3:
-○:LDP man-pages:3.68:2013/07/10:fabs:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/07/10:fabsf:3:fabs:3:
-＠:LDP man-pages:3.68:2013/07/10:fabsl:3:fabs:3:
-○:LDP man-pages:3.68:2009/02/23:fclose:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/06/21:fcloseall:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/07/04:fcvt:3:ecvt:3:
-＠:LDP man-pages:3.68:2007/07/26:fcvt_r:3:ecvt_r:3:
-○:LDP man-pages:3.68:2013/07/15:fdim:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/07/15:fdimf:3:fdim:3:
-＠:LDP man-pages:3.68:2013/07/15:fdiml:3:fdim:3:
-＠:LDP man-pages:3.68:2012/04/22:fdopen:3:fopen:3:
-＠:LDP man-pages:3.68:2010/06/20:fdopendir:3:opendir:3:
-＠:LDP man-pages:3.68:2014/04/01:feclearexcept:3:fenv:3:
-＠:LDP man-pages:3.68:2014/04/01:fedisableexcept:3:fenv:3:
-＠:LDP man-pages:3.68:2014/04/01:feenableexcept:3:fenv:3:
-＠:LDP man-pages:3.68:2014/04/01:fegetenv:3:fenv:3:
-＠:LDP man-pages:3.68:2014/04/01:fegetexcept:3:fenv:3:
-＠:LDP man-pages:3.68:2014/04/01:fegetexceptflag:3:fenv:3:
-＠:LDP man-pages:3.68:2014/04/01:fegetround:3:fenv:3:
-＠:LDP man-pages:3.68:2014/04/01:feholdexcept:3:fenv:3:
-○:LDP man-pages:3.68:2014/04/01:fenv:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/15:feof:3:ferror:3:
-＠:LDP man-pages:3.68:2008/08/29:feof_unlocked:3:unlocked_stdio:3:
-＠:LDP man-pages:3.68:2014/04/01:feraiseexcept:3:fenv:3:
-○:LDP man-pages:3.68:2014/01/15:ferror:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2008/08/29:ferror_unlocked:3:unlocked_stdio:3:
-＠:LDP man-pages:3.68:2014/04/01:fesetenv:3:fenv:3:
-＠:LDP man-pages:3.68:2014/04/01:fesetexceptflag:3:fenv:3:
-＠:LDP man-pages:3.68:2014/04/01:fesetround:3:fenv:3:
-＠:LDP man-pages:3.68:2014/04/01:fetestexcept:3:fenv:3:
-＠:LDP man-pages:3.68:2014/04/01:feupdateenv:3:fenv:3:
-○:LDP man-pages:3.68:2014/04/20:fexecve:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/07/15:fflush:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2008/08/29:fflush_unlocked:3:unlocked_stdio:3:
-○:LDP man-pages:3.68:2014/04/14:ffs:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2014/04/14:ffsl:3:ffs:3:
-＠:LDP man-pages:3.68:2014/04/14:ffsll:3:ffs:3:
-○:LDP man-pages:3.68:2013/12/31:fgetc:3:2014/06/08::amotoki@gmail.com:Akihiro Motoki:
-＠:LDP man-pages:3.68:2008/08/29:fgetc_unlocked:3:unlocked_stdio:3:
-○:LDP man-pages:3.68:2013/04/19:fgetgrent:3:2014/06/08::nishi@rpts.cl.nec.co.jp:HIROFUMI Nishizuka:
-＠:LDP man-pages:3.68:2010/10/21:fgetgrent_r:3:getgrent_r:3:
-＠:LDP man-pages:3.68:2014/05/28:fgetpos:3:fseek:3:
-○:LDP man-pages:3.68:2013/04/19:fgetpwent:3:2014/06/08::nishi@rpts.cl.nec.co.jp:HIROFUMI Nishizuka:
-＠:LDP man-pages:3.68:2010/10/21:fgetpwent_r:3:getpwent_r:3:
-＠:LDP man-pages:3.68:2013/12/31:fgets:3:fgetc:3:
-＠:LDP man-pages:3.68:2008/08/29:fgets_unlocked:3:unlocked_stdio:3:
-＠:LDP man-pages:3.68:2014/05/28:fgetspent:3:getspnam:3:
-＠:LDP man-pages:3.68:2014/05/28:fgetspent_r:3:getspnam:3:
-○:LDP man-pages:3.68:2013/04/19:fgetwc:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2008/08/29:fgetwc_unlocked:3:unlocked_stdio:3:
-○:LDP man-pages:3.68:2011/09/28:fgetws:3:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2008/08/29:fgetws_unlocked:3:unlocked_stdio:3:
-＠:LDP man-pages:3.68:2014/01/15:fileno:3:ferror:3:
-＠:LDP man-pages:3.68:2008/08/29:fileno_unlocked:3:unlocked_stdio:3:
-○:LDP man-pages:3.68:2013/07/22:finite:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/07/22:finitef:3:finite:3:
-＠:LDP man-pages:3.68:2013/07/22:finitel:3:finite:3:
-○:LDP man-pages:3.68:2013/07/23:flockfile:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/07/23:floor:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/07/23:floorf:3:floor:3:
-＠:LDP man-pages:3.68:2013/07/23:floorl:3:floor:3:
-○:LDP man-pages:3.68:2013/09/17:fma:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/09/17:fmaf:3:fma:3:
-＠:LDP man-pages:3.68:2013/09/17:fmal:3:fma:3:
-○:LDP man-pages:3.68:2013/09/17:fmax:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/09/17:fmaxf:3:fmax:3:
-＠:LDP man-pages:3.68:2013/09/17:fmaxl:3:fmax:3:
-○:LDP man-pages:3.68:2014/04/06:fmemopen:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/09/17:fmin:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/09/17:fminf:3:fmin:3:
-＠:LDP man-pages:3.68:2013/09/17:fminl:3:fmin:3:
-○:LDP man-pages:3.68:2012/03/15:fmod:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2012/03/15:fmodf:3:fmod:3:
-＠:LDP man-pages:3.68:2012/03/15:fmodl:3:fmod:3:
-○:LDP man-pages:3.68:2013/06/21:fmtmsg:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2000/10/15:fnmatch:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/04/22:fopen:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-×:LDP man-pages:3.68:2013/03/17:fopencookie:3:::::
-＠:LDP man-pages:3.68:2010/06/13:forkpty:3:openpty:3:
-○:LDP man-pages:3.68:2014/05/28:fpathconf:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2013/08/06:fpclassify:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/12/30:fprintf:3:printf:3:
-○:LDP man-pages:3.68:2001/12/15:fpurge:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-＠:LDP man-pages:3.68:2014/01/11:fputc:3:puts:3:
-＠:LDP man-pages:3.68:2008/08/29:fputc_unlocked:3:unlocked_stdio:3:
-＠:LDP man-pages:3.68:2014/01/11:fputs:3:puts:3:
-＠:LDP man-pages:3.68:2008/08/29:fputs_unlocked:3:unlocked_stdio:3:
-○:LDP man-pages:3.68:2013/04/19:fputwc:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2008/08/29:fputwc_unlocked:3:unlocked_stdio:3:
-○:LDP man-pages:3.68:2011/09/28:fputws:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2008/08/29:fputws_unlocked:3:unlocked_stdio:3:
-○:LDP man-pages:3.68:2012/03/30:fread:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/08/29:fread_unlocked:3:unlocked_stdio:3:
-＠:LDP man-pages:3.68:2014/05/21:free:3:malloc:3:
-＠:LDP man-pages:3.68:2014/04/06:freeaddrinfo:3:getaddrinfo:3:
-＠:LDP man-pages:3.68:2010/09/04:freehostent:3:getipnodebyname:3:
-＠:LDP man-pages:3.68:2014/02/26:freeifaddrs:3:getifaddrs:3:
-※:LDP man-pages:3.68:2014/05/28:freelocale:3:newlocale:3:
-＠:LDP man-pages:3.68:2012/04/22:freopen:3:fopen:3:
-○:LDP man-pages:3.68:2013/08/06:frexp:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/08/06:frexpf:3:frexp:3:
-＠:LDP man-pages:3.68:2013/08/06:frexpl:3:frexp:3:
-＠:LDP man-pages:3.68:2014/01/11:fscanf:3:scanf:3:
-○:LDP man-pages:3.68:2014/05/28:fseek:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2014/03/20:fseeko:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:fsetpos:3:fseek:3:
-＠:LDP man-pages:3.68:2013/09/26:fstatvfs:3:statvfs:3:
-＠:LDP man-pages:3.68:2014/05/28:ftell:3:fseek:3:
-＠:LDP man-pages:3.68:2014/03/20:ftello:3:fseeko:3:
-○:LDP man-pages:3.68:2013/09/26:ftime:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2013/10/07:ftok:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-＠:LDP man-pages:3.68:2013/07/23:ftrylockfile:3:flockfile:3:
-○:LDP man-pages:3.68:2014/03/18:fts:3:2014/06/08::sato@complex.eng.hokudai.ac.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2014/03/18:fts_children:3:fts:3:
-＠:LDP man-pages:3.68:2014/03/18:fts_close:3:fts:3:
-＠:LDP man-pages:3.68:2014/03/18:fts_open:3:fts:3:
-＠:LDP man-pages:3.68:2014/03/18:fts_read:3:fts:3:
-＠:LDP man-pages:3.68:2014/03/18:fts_set:3:fts:3:
-○:LDP man-pages:3.68:2014/01/11:ftw:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/07/23:funlockfile:3:flockfile:3:
-※:LDP man-pages:3.68:2014/01/24:futimens:3:utimensat:2:
-○:LDP man-pages:3.68:2013/10/29:futimes:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/03/19:fwide:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-＠:LDP man-pages:3.68:2014/03/19:fwprintf:3:wprintf:3:
-＠:LDP man-pages:3.68:2012/03/30:fwrite:3:fread:3:
-＠:LDP man-pages:3.68:2008/08/29:fwrite_unlocked:3:unlocked_stdio:3:
-※:LDP man-pages:3.68:2014/05/28:gai_cancel:3:getaddrinfo_a:3:
-※:LDP man-pages:3.68:2014/05/28:gai_error:3:getaddrinfo_a:3:
-＠:LDP man-pages:3.68:2014/04/06:gai_strerror:3:getaddrinfo:3:
-※:LDP man-pages:3.68:2014/05/28:gai_suspend:3:getaddrinfo_a:3:
-○:LDP man-pages:3.68:2008/08/05:gamma:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/08/05:gammaf:3:gamma:3:
-＠:LDP man-pages:3.68:2008/08/05:gammal:3:gamma:3:
-○:LDP man-pages:3.68:2014/05/28:gcvt:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/20:get_current_dir_name:3:getcwd:3:
-＠:LDP man-pages:3.68:2013/09/26:get_myaddress:3:rpc:3:
-＠:LDP man-pages:3.68:2012/03/20:get_nprocs:3:get_nprocs_conf:3:
-○:LDP man-pages:3.68:2012/03/20:get_nprocs_conf:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/04/06:getaddrinfo:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-×:LDP man-pages:3.68:2014/05/28:getaddrinfo_a:3:::::
-＠:LDP man-pages:3.68:2003/09/09:getaliasbyname:3:setaliasent:3:
-＠:LDP man-pages:3.68:2003/09/09:getaliasbyname_r:3:setaliasent:3:
-＠:LDP man-pages:3.68:2003/09/09:getaliasent:3:setaliasent:3:
-＠:LDP man-pages:3.68:2003/09/09:getaliasent_r:3:setaliasent:3:
-×:LDP man-pages:3.68:2014/05/28:getauxval:3:::::
-＠:LDP man-pages:3.68:2013/12/31:getc:3:fgetc:3:
-＠:LDP man-pages:3.68:2008/08/29:getc_unlocked:3:unlocked_stdio:3:
-＠:LDP man-pages:3.68:2013/12/31:getchar:3:fgetc:3:
-＠:LDP man-pages:3.68:2008/08/29:getchar_unlocked:3:unlocked_stdio:3:
-○:LDP man-pages:3.68:2014/04/08:getcontext:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/09/20:getcwd:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2014/01/17:getdate:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/17:getdate_err:3:getdate:3:
-＠:LDP man-pages:3.68:2014/01/17:getdate_r:3:getdate:3:
-＠:LDP man-pages:3.68:2014/04/06:getdelim:3:getline:3:
-○:LDP man-pages:3.68:2007/07/26:getdirentries:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2013/02/05:getdtablesize:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/08/14:getenv:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2002/02/28:getfsent:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-＠:LDP man-pages:3.68:2002/02/28:getfsfile:3:getfsent:3:
-＠:LDP man-pages:3.68:2002/02/28:getfsspec:3:getfsent:3:
-○:LDP man-pages:3.68:2013/06/21:getgrent:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/10/21:getgrent_r:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2013/07/22:getgrgid:3:getgrnam:3:
-＠:LDP man-pages:3.68:2013/07/22:getgrgid_r:3:getgrnam:3:
-○:LDP man-pages:3.68:2013/07/22:getgrnam:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/07/22:getgrnam_r:3:getgrnam:3:
-○:LDP man-pages:3.68:2008/07/03:getgrouplist:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/03/11:gethostbyaddr:3:gethostbyname:3:
-＠:LDP man-pages:3.68:2014/03/11:gethostbyaddr_r:3:gethostbyname:3:
-○:LDP man-pages:3.68:2014/03/11:gethostbyname:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/03/11:gethostbyname2:3:gethostbyname:3:
-＠:LDP man-pages:3.68:2014/03/11:gethostbyname2_r:3:gethostbyname:3:
-＠:LDP man-pages:3.68:2014/03/11:gethostbyname_r:3:gethostbyname:3:
-＠:LDP man-pages:3.68:2014/03/11:gethostent:3:gethostbyname:3:
-＠:LDP man-pages:3.68:2014/03/11:gethostent_r:3:gethostbyname:3:
-○:LDP man-pages:3.68:2010/09/20:gethostid:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/26:getifaddrs:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/04:getipnodebyaddr:3:getipnodebyname:3:
-○:LDP man-pages:3.68:2010/09/04:getipnodebyname:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2014/04/06:getline:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/04/01:getloadavg:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2013/04/19:getlogin:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/04/19:getlogin_r:3:getlogin:3:
-○:LDP man-pages:3.68:2009/09/15:getmntent:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2009/09/15:getmntent_r:3:getmntent:3:
-☆:LDP man-pages:3.67=>3.68:2014/05/28:getnameinfo:3:2014/06/04::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/08/19:getnetbyaddr:3:getnetent:3:
-＠:LDP man-pages:3.68:2010/09/10:getnetbyaddr_r:3:getnetent_r:3:
-＠:LDP man-pages:3.68:2008/08/19:getnetbyname:3:getnetent:3:
-＠:LDP man-pages:3.68:2010/09/10:getnetbyname_r:3:getnetent_r:3:
-○:LDP man-pages:3.68:2008/08/19:getnetent:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/09/10:getnetent_r:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:getnetgrent:3:setnetgrent:3:
-＠:LDP man-pages:3.68:2014/05/28:getnetgrent_r:3:setnetgrent:3:
-○:LDP man-pages:3.68:2014/05/09:getopt:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/09:getopt_long:3:getopt:3:
-＠:LDP man-pages:3.68:2014/05/09:getopt_long_only:3:getopt:3:
-○:LDP man-pages:3.68:2013/06/21:getpass:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-＠:LDP man-pages:3.68:2008/08/19:getprotobyname:3:getprotoent:3:
-＠:LDP man-pages:3.68:2010/09/10:getprotobyname_r:3:getprotoent_r:3:
-＠:LDP man-pages:3.68:2008/08/19:getprotobynumber:3:getprotoent:3:
-＠:LDP man-pages:3.68:2010/09/10:getprotobynumber_r:3:getprotoent_r:3:
-○:LDP man-pages:3.68:2008/08/19:getprotoent:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/09/10:getprotoent_r:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/04/01:getpt:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/10/21:getpw:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2013/06/21:getpwent:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/10/21:getpwent_r:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/07/22:getpwnam:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/07/22:getpwnam_r:3:getpwnam:3:
-＠:LDP man-pages:3.68:2013/07/22:getpwuid:3:getpwnam:3:
-＠:LDP man-pages:3.68:2013/07/22:getpwuid_r:3:getpwnam:3:
-＠:LDP man-pages:3.68:2014/05/28:getrpcbyname:3:getrpcent:3:
-＠:LDP man-pages:3.68:2010/09/10:getrpcbyname_r:3:getrpcent_r:3:
-＠:LDP man-pages:3.68:2014/05/28:getrpcbynumber:3:getrpcent:3:
-＠:LDP man-pages:3.68:2010/09/10:getrpcbynumber_r:3:getrpcent_r:3:
-○:LDP man-pages:3.68:2014/05/28:getrpcent:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/09/10:getrpcent_r:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/28:getrpcport:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-○:LDP man-pages:3.68:2014/01/24:gets:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/08/19:getservbyname:3:getservent:3:
-＠:LDP man-pages:3.68:2010/09/10:getservbyname_r:3:getservent_r:3:
-＠:LDP man-pages:3.68:2008/08/19:getservbyport:3:getservent:3:
-＠:LDP man-pages:3.68:2010/09/10:getservbyport_r:3:getservent_r:3:
-○:LDP man-pages:3.68:2008/08/19:getservent:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/09/10:getservent_r:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:getspent:3:getspnam:3:
-＠:LDP man-pages:3.68:2014/05/28:getspent_r:3:getspnam:3:
-○:LDP man-pages:3.68:2014/05/28:getspnam:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:getspnam_r:3:getspnam:3:
-○:LDP man-pages:3.68:2014/04/08:getsubopt:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/07/22:getttyent:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2013/07/22:getttynam:3:getttyent:3:
-○:LDP man-pages:3.68:2010/09/10:getumask:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/06/21:getusershell:3:2014/06/08::ishioka@dad.eec.toshiba.co.jp:ISHIOKA Takashi:
-○:LDP man-pages:3.68:2014/05/28:getutent:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:getutent_r:3:getutent:3:
-＠:LDP man-pages:3.68:2014/05/28:getutid:3:getutent:3:
-＠:LDP man-pages:3.68:2014/05/28:getutid_r:3:getutent:3:
-＠:LDP man-pages:3.68:2014/05/28:getutline:3:getutent:3:
-＠:LDP man-pages:3.68:2014/05/28:getutline_r:3:getutent:3:
-○:LDP man-pages:3.68:2014/04/08:getutmp:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/04/08:getutmpx:3:getutmp:3:
-＠:LDP man-pages:3.68:2014/05/28:getutxent:3:getutent:3:
-＠:LDP man-pages:3.68:2014/05/28:getutxid:3:getutent:3:
-＠:LDP man-pages:3.68:2014/05/28:getutxline:3:getutent:3:
-○:LDP man-pages:3.68:2010/09/26:getw:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2013/04/19:getwc:3:fgetwc:3:
-＠:LDP man-pages:3.68:2008/08/29:getwc_unlocked:3:unlocked_stdio:3:
-○:LDP man-pages:3.68:1999/07/25:getwchar:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2008/08/29:getwchar_unlocked:3:unlocked_stdio:3:
-＠:LDP man-pages:3.68:2010/09/20:getwd:3:getcwd:3:
-○:LDP man-pages:3.68:2007/10/10:glob:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2007/10/10:globfree:3:glob:3:
-＠:LDP man-pages:3.68:2013/12/30:gmtime:3:ctime:3:
-＠:LDP man-pages:3.68:2013/12/30:gmtime_r:3:ctime:3:
-＠:LDP man-pages:3.68:2014/05/28:gnu_dev_major:3:makedev:3:
-＠:LDP man-pages:3.68:2014/05/28:gnu_dev_makedev:3:makedev:3:
-＠:LDP man-pages:3.68:2014/05/28:gnu_dev_minor:3:makedev:3:
-＠:LDP man-pages:3.68:2012/08/26:gnu_get_libc_release:3:gnu_get_libc_version:3:
-○:LDP man-pages:3.68:2012/08/26:gnu_get_libc_version:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2008/06/14:grantpt:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2007/07/26:gsignal:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/03/11:h_errno:3:gethostbyname:3:
-○:LDP man-pages:3.68:2012/04/23:hash:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2009/09/15:hasmntopt:3:getmntent:3:
-＠:LDP man-pages:3.68:2014/01/05:hcreate:3:hsearch:3:
-＠:LDP man-pages:3.68:2014/01/05:hcreate_r:3:hsearch:3:
-＠:LDP man-pages:3.68:2014/01/05:hdestroy:3:hsearch:3:
-＠:LDP man-pages:3.68:2014/01/05:hdestroy_r:3:hsearch:3:
-＠:LDP man-pages:3.68:2014/03/11:herror:3:gethostbyname:3:
-○:LDP man-pages:3.68:2014/01/05:hsearch:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/05:hsearch_r:3:hsearch:3:
-＠:LDP man-pages:3.68:2014/03/11:hstrerror:3:gethostbyname:3:
-＠:LDP man-pages:3.68:2010/09/10:htobe16:3:endian:3:
-＠:LDP man-pages:3.68:2010/09/10:htobe32:3:endian:3:
-＠:LDP man-pages:3.68:2010/09/10:htobe64:3:endian:3:
-＠:LDP man-pages:3.68:2010/09/10:htole16:3:endian:3:
-＠:LDP man-pages:3.68:2010/09/10:htole32:3:endian:3:
-＠:LDP man-pages:3.68:2010/09/10:htole64:3:endian:3:
-＠:LDP man-pages:3.68:2014/04/08:htonl:3:byteorder:3:
-＠:LDP man-pages:3.68:2014/04/08:htons:3:byteorder:3:
-○:LDP man-pages:3.68:2010/09/20:hypot:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/20:hypotf:3:hypot:3:
-＠:LDP man-pages:3.68:2010/09/20:hypotl:3:hypot:3:
-○:LDP man-pages:3.68:2012/05/10:iconv:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2008/08/11:iconv_close:3:2014/06/08::sato@complex.eng.hokudai.ac.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2008/08/11:iconv_open:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2012/11/21:if_freenameindex:3:if_nameindex:3:
-＠:LDP man-pages:3.68:2014/04/01:if_indextoname:3:if_nametoindex:3:
-○:LDP man-pages:3.68:2012/11/21:if_nameindex:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/04/01:if_nametoindex:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/08/06:ilogb:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/08/06:ilogbf:3:ilogb:3:
-＠:LDP man-pages:3.68:2013/08/06:ilogbl:3:ilogb:3:
-＠:LDP man-pages:3.68:2013/06/21:imaxabs:3:abs:3:
-＠:LDP man-pages:3.68:2013/07/05:imaxdiv:3:div:3:
-○:LDP man-pages:3.68:2014/04/01:index:3:2014/06/08::nishi@rpts.cl.nec.co.jp:HIROFUMI Nishizuka:
-○:LDP man-pages:3.68:2014/05/28:inet:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:inet_addr:3:inet:3:
-＠:LDP man-pages:3.68:2014/05/28:inet_aton:3:inet:3:
-＠:LDP man-pages:3.68:2014/05/28:inet_lnaof:3:inet:3:
-＠:LDP man-pages:3.68:2014/04/19:inet_makeaddr:3:inet_addr:3:
-※:LDP man-pages:3.68:2014/05/28:inet_net_ntop:3:inet_net_pton:3:
-×:LDP man-pages:3.68:2014/05/28:inet_net_pton:3:::::
-＠:LDP man-pages:3.68:2014/05/28:inet_netof:3:inet:3:
-＠:LDP man-pages:3.68:2014/05/28:inet_network:3:inet:3:
-＠:LDP man-pages:3.68:2014/05/28:inet_ntoa:3:inet:3:
-○:LDP man-pages:3.68:2008/11/11:inet_ntop:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2008/06/18:inet_pton:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:1993/06/02:infnan:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2007/07/26:initgroups:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/03/25:initstate:3:random:3:
-＠:LDP man-pages:3.68:2014/03/25:initstate_r:3:random_r:3:
-＠:LDP man-pages:3.68:2014/05/28:innetgr:3:setnetgrent:3:
-○:LDP man-pages:3.68:2010/09/09:insque:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/11/11:intro:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:iruserok:3:rcmd:3:
-＠:LDP man-pages:3.68:2014/05/28:iruserok_af:3:rcmd:3:
-＠:LDP man-pages:3.68:2014/03/18:isalnum:3:isalpha:3:
-＠:LDP man-pages:3.68:2014/03/18:isalnum_l:3:isalpha:3:
-○:LDP man-pages:3.68:2014/03/18:isalpha:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/03/18:isascii:3:isalpha:3:
-＠:LDP man-pages:3.68:2014/03/18:isascii_l:3:isalpha:3:
-○:LDP man-pages:3.68:2014/01/27:isatty:3:2014/06/08::nagoya@cc.hit-u.ac.jp:NAGOYA Hiroaki:
-＠:LDP man-pages:3.68:2014/03/18:isblank:3:isalpha:3:
-＠:LDP man-pages:3.68:2014/03/18:isblank_l:3:isalpha:3:
-＠:LDP man-pages:3.68:2014/03/18:iscntrl:3:isalpha:3:
-＠:LDP man-pages:3.68:2014/03/18:iscntrl_l:3:isalpha:3:
-＠:LDP man-pages:3.68:2014/03/18:isdigit:3:isalpha:3:
-＠:LDP man-pages:3.68:2014/03/18:isdigit_l:3:isalpha:3:
-＠:LDP man-pages:3.68:2013/08/06:isfinite:3:fpclassify:3:
-＠:LDP man-pages:3.68:2014/03/18:isgraph:3:isalpha:3:
-＠:LDP man-pages:3.68:2014/03/18:isgraph_l:3:isalpha:3:
-○:LDP man-pages:3.68:2014/01/27:isgreater:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/27:isgreaterequal:3:isgreater:3:
-＠:LDP man-pages:3.68:2013/08/06:isinf:3:fpclassify:3:
-＠:LDP man-pages:3.68:2013/07/22:isinff:3:finite:3:
-＠:LDP man-pages:3.68:2013/07/22:isinfl:3:finite:3:
-＠:LDP man-pages:3.68:2014/01/27:isless:3:isgreater:3:
-＠:LDP man-pages:3.68:2014/01/27:islessequal:3:isgreater:3:
-＠:LDP man-pages:3.68:2014/01/27:islessgreater:3:isgreater:3:
-＠:LDP man-pages:3.68:2014/03/18:islower:3:isalpha:3:
-＠:LDP man-pages:3.68:2014/03/18:islower_l:3:isalpha:3:
-＠:LDP man-pages:3.68:2013/08/06:isnan:3:fpclassify:3:
-＠:LDP man-pages:3.68:2013/07/22:isnanf:3:finite:3:
-＠:LDP man-pages:3.68:2013/07/22:isnanl:3:finite:3:
-＠:LDP man-pages:3.68:2013/08/06:isnormal:3:fpclassify:3:
-＠:LDP man-pages:3.68:2014/03/18:isprint:3:isalpha:3:
-＠:LDP man-pages:3.68:2014/03/18:isprint_l:3:isalpha:3:
-＠:LDP man-pages:3.68:2014/03/18:ispunct:3:isalpha:3:
-＠:LDP man-pages:3.68:2014/03/18:ispunct_l:3:isalpha:3:
-＠:LDP man-pages:3.68:2014/03/18:isspace:3:isalpha:3:
-＠:LDP man-pages:3.68:2014/03/18:isspace_l:3:isalpha:3:
-＠:LDP man-pages:3.68:2014/01/27:isunordered:3:isgreater:3:
-＠:LDP man-pages:3.68:2014/03/18:isupper:3:isalpha:3:
-＠:LDP man-pages:3.68:2014/03/18:isupper_l:3:isalpha:3:
-○:LDP man-pages:3.68:2014/01/28:iswalnum:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2014/01/28:iswalpha:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2014/02/10:iswblank:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2014/02/10:iswcntrl:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2014/02/26:iswctype:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:1999/07/25:iswdigit:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:1999/07/25:iswgraph:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:1999/07/25:iswlower:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:1999/07/25:iswprint:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:1999/07/25:iswpunct:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:1999/07/25:iswspace:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:1999/07/25:iswupper:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:1999/07/25:iswxdigit:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2014/03/18:isxdigit:3:isalpha:3:
-＠:LDP man-pages:3.68:2014/03/18:isxdigit_l:3:isalpha:3:
-○:LDP man-pages:3.68:2014/01/18:j0:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/18:j0f:3:j0:3:
-＠:LDP man-pages:3.68:2014/01/18:j0l:3:j0:3:
-＠:LDP man-pages:3.68:2014/01/18:j1:3:j0:3:
-＠:LDP man-pages:3.68:2014/01/18:j1f:3:j0:3:
-＠:LDP man-pages:3.68:2014/01/18:j1l:3:j0:3:
-＠:LDP man-pages:3.68:2014/01/18:jn:3:j0:3:
-＠:LDP man-pages:3.68:2014/01/18:jnf:3:j0:3:
-＠:LDP man-pages:3.68:2014/01/18:jnl:3:j0:3:
-＠:LDP man-pages:3.68:2013/06/21:jrand48:3:drand48:3:
-＠:LDP man-pages:3.68:2013/09/09:jrand48_r:3:drand48_r:3:
-＠:LDP man-pages:3.68:2014/05/28:key_decryptsession:3:key_setsecret:3:
-＠:LDP man-pages:3.68:2014/05/28:key_encryptsession:3:key_setsecret:3:
-＠:LDP man-pages:3.68:2014/05/28:key_gendes:3:key_setsecret:3:
-＠:LDP man-pages:3.68:2014/05/28:key_secretkey_is_set:3:key_setsecret:3:
-○:LDP man-pages:3.68:2014/05/28:key_setsecret:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2012/11/29:klogctl:3:syslog:2:
-＠:LDP man-pages:3.68:2014/05/28:l64a:3:a64l:3:
-＠:LDP man-pages:3.68:2013/06/21:labs:3:abs:3:
-＠:LDP man-pages:3.68:2014/05/28:lckpwdf:3:getspnam:3:
-＠:LDP man-pages:3.68:2013/06/21:lcong48:3:drand48:3:
-＠:LDP man-pages:3.68:2013/09/09:lcong48_r:3:drand48_r:3:
-○:LDP man-pages:3.68:2013/08/19:ldexp:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/08/19:ldexpf:3:ldexp:3:
-＠:LDP man-pages:3.68:2013/08/19:ldexpl:3:ldexp:3:
-＠:LDP man-pages:3.68:2013/07/05:ldiv:3:div:3:
-＠:LDP man-pages:3.68:2010/09/10:le16toh:3:endian:3:
-＠:LDP man-pages:3.68:2010/09/10:le32toh:3:endian:3:
-＠:LDP man-pages:3.68:2010/09/10:le64toh:3:endian:3:
-＠:LDP man-pages:3.68:1999/09/27:lfind:3:lsearch:3:
-○:LDP man-pages:3.68:2014/01/18:lgamma:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/18:lgamma_r:3:lgamma:3:
-＠:LDP man-pages:3.68:2014/01/18:lgammaf:3:lgamma:3:
-＠:LDP man-pages:3.68:2014/01/18:lgammaf_r:3:lgamma:3:
-＠:LDP man-pages:3.68:2014/01/18:lgammal:3:lgamma:3:
-＠:LDP man-pages:3.68:2014/01/18:lgammal_r:3:lgamma:3:
-○:LDP man-pages:3.68:2012/05/08:lio_listio:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/06/21:llabs:3:abs:3:
-＠:LDP man-pages:3.68:2013/07/05:lldiv:3:div:3:
-＠:LDP man-pages:3.68:2014/01/18:llrint:3:lrint:3:
-＠:LDP man-pages:3.68:2014/01/18:llrintf:3:lrint:3:
-＠:LDP man-pages:3.68:2014/01/18:llrintl:3:lrint:3:
-＠:LDP man-pages:3.68:2013/08/26:llround:3:lround:3:
-＠:LDP man-pages:3.68:2013/08/26:llroundf:3:lround:3:
-＠:LDP man-pages:3.68:2013/08/26:llroundl:3:lround:3:
-○:LDP man-pages:3.68:2013/06/21:localeconv:3:2014/06/08::tyoshino@eng.toyo.ac.jp:Takashi Yoshino:
-＠:LDP man-pages:3.68:2013/12/30:localtime:3:ctime:3:
-＠:LDP man-pages:3.68:2013/12/30:localtime_r:3:ctime:3:
-○:LDP man-pages:3.68:2014/02/11:lockf:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/09/20:log:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/09/20:log10:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/20:log10f:3:log10:3:
-＠:LDP man-pages:3.68:2010/09/20:log10l:3:log10:3:
-○:LDP man-pages:3.68:2014/02/28:log1p:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/02/28:log1pf:3:log1p:3:
-＠:LDP man-pages:3.68:2014/02/28:log1pl:3:log1p:3:
-○:LDP man-pages:3.68:2010/09/12:log2:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/12:log2f:3:log2:3:
-＠:LDP man-pages:3.68:2010/09/12:log2l:3:log2:3:
-○:LDP man-pages:3.68:2014/02/28:logb:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/02/28:logbf:3:logb:3:
-＠:LDP man-pages:3.68:2014/02/28:logbl:3:logb:3:
-＠:LDP man-pages:3.68:2010/09/20:logf:3:log:3:
-○:LDP man-pages:3.68:2004/05/06:login:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2010/06/13:login_tty:3:openpty:3:
-＠:LDP man-pages:3.68:2010/09/20:logl:3:log:3:
-＠:LDP man-pages:3.68:2004/05/06:logout:3:login:3:
-＠:LDP man-pages:3.68:2008/07/02:logwtmp:3:updwtmp:3:
-○:LDP man-pages:3.68:2009/01/13:longjmp:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/06/21:lrand48:3:drand48:3:
-＠:LDP man-pages:3.68:2013/09/09:lrand48_r:3:drand48_r:3:
-○:LDP man-pages:3.68:2014/01/18:lrint:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/18:lrintf:3:lrint:3:
-＠:LDP man-pages:3.68:2014/01/18:lrintl:3:lrint:3:
-○:LDP man-pages:3.68:2013/08/26:lround:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/08/26:lroundf:3:lround:3:
-＠:LDP man-pages:3.68:2013/08/26:lroundl:3:lround:3:
-○:LDP man-pages:3.68:1999/09/27:lsearch:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/08/19:lseek64:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2013/10/29:lutimes:3:futimes:3:
-＠:LDP man-pages:3.68:2014/05/28:major:3:makedev:3:
-○:LDP man-pages:3.68:2014/05/28:makecontext:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/28:makedev:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-×:LDP man-pages:3.68:2012/05/06:mallinfo:3:::::
-○:LDP man-pages:3.68:2014/05/21:malloc:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-×:LDP man-pages:3.68:2012/05/04:malloc_get_state:3:::::
-○:LDP man-pages:3.68:2010/10/13:malloc_hook:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/04/19:malloc_info:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-※:LDP man-pages:3.68:2012/05/04:malloc_set_state:3:malloc_get_state:3:
-○:LDP man-pages:3.68:2012/05/06:malloc_stats:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-×:LDP man-pages:3.68:2014/05/28:malloc_trim:3:::::
-×:LDP man-pages:3.68:2012/03/29:malloc_usable_size:3:::::
-×:LDP man-pages:3.68:2012/04/30:mallopt:3:::::
-○:LDP man-pages:3.68:2010/09/10:matherr:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/06/21:mblen:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-○:LDP man-pages:3.68:2013/06/21:mbrlen:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-○:LDP man-pages:3.68:2014/03/18:mbrtowc:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2014/03/18:mbsinit:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-○:LDP man-pages:3.68:2014/03/18:mbsnrtowcs:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-○:LDP man-pages:3.68:2014/03/18:mbsrtowcs:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-○:LDP man-pages:3.68:2014/03/18:mbstowcs:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-○:LDP man-pages:3.68:2014/03/18:mbtowc:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-×:LDP man-pages:3.68:2014/01/11:mcheck:3:::::
-※:LDP man-pages:3.68:2014/01/11:mcheck_check_all:3:mcheck:3:
-※:LDP man-pages:3.68:2014/01/11:mcheck_pedantic:3:mcheck:3:
-＠:LDP man-pages:3.68:2013/09/02:memalign:3:posix_memalign:3:
-○:LDP man-pages:3.68:2014/03/10:memccpy:3:2014/06/08::tyoshino@eng.toyo.ac.jp:Takashi Yoshino:
-○:LDP man-pages:3.68:2014/03/10:memchr:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/03/14:memcmp:3:2014/06/08::nishi@rpts.cl.nec.co.jp:HIROFUMI Nishizuka:
-○:LDP man-pages:3.68:2014/03/17:memcpy:3:2014/06/08::tyoshino@eng.toyo.ac.jp:Takashi Yoshino:
-○:LDP man-pages:3.68:2014/03/17:memfrob:3:2014/06/08::ishikawa@linux.or.jp:ISHIKAWA Mutsumi:
-○:LDP man-pages:3.68:2014/03/17:memmem:3:2014/06/08::tyoshino@eng.toyo.ac.jp:Takashi Yoshino:
-○:LDP man-pages:3.68:2014/03/17:memmove:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/03/18:mempcpy:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2014/03/10:memrchr:3:memchr:3:
-○:LDP man-pages:3.68:2014/03/18:memset:3:2014/06/08::tyoshino@eng.toyo.ac.jp:Takashi Yoshino:
-＠:LDP man-pages:3.68:2014/05/28:minor:3:makedev:3:
-○:LDP man-pages:3.68:2010/09/26:mkdtemp:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/03/24:mkfifo:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2014/03/24:mkfifoat:3:mkfifo:3:
-＠:LDP man-pages:3.68:2013/12/28:mkostemp:3:mkstemp:3:
-＠:LDP man-pages:3.68:2013/12/28:mkostemps:3:mkstemp:3:
-○:LDP man-pages:3.68:2013/12/28:mkstemp:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/12/28:mkstemps:3:mkstemp:3:
-○:LDP man-pages:3.68:2014/02/27:mktemp:3:2014/06/08::tanisako@osa.dec.com:Kazuyuki Tanisako:
-＠:LDP man-pages:3.68:2013/12/30:mktime:3:ctime:3:
-＠:LDP man-pages:3.68:2014/04/06:mmap64:3:mmap:2:
-○:LDP man-pages:3.68:2013/06/21:modf:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/06/21:modff:3:modf:3:
-＠:LDP man-pages:3.68:2013/06/21:modfl:3:modf:3:
-○:LDP man-pages:3.68:2012/04/26:mpool:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-※:LDP man-pages:3.68:2014/01/11:mprobe:3:mcheck:3:
-○:LDP man-pages:3.68:2010/08/29:mq_close:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/28:mq_getattr:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/04/06:mq_notify:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2009/02/20:mq_open:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/01/18:mq_receive:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/01/18:mq_send:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:mq_setattr:3:mq_getattr:3:
-＠:LDP man-pages:3.68:2014/01/18:mq_timedreceive:3:mq_receive:3:
-＠:LDP man-pages:3.68:2014/01/18:mq_timedsend:3:mq_send:3:
-○:LDP man-pages:3.68:2010/08/29:mq_unlink:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/06/21:mrand48:3:drand48:3:
-＠:LDP man-pages:3.68:2013/09/09:mrand48_r:3:drand48_r:3:
-×:LDP man-pages:3.68:2012/04/18:mtrace:3:::::
-※:LDP man-pages:3.68:2012/04/18:muntrace:3:mtrace:3:
-○:LDP man-pages:3.68:2010/09/20:nan:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/20:nanf:3:nan:3:
-＠:LDP man-pages:3.68:2010/09/20:nanl:3:nan:3:
-＠:LDP man-pages:3.68:2013/08/26:nearbyint:3:rint:3:
-＠:LDP man-pages:3.68:2013/08/26:nearbyintf:3:rint:3:
-＠:LDP man-pages:3.68:2013/08/26:nearbyintl:3:rint:3:
-○:LDP man-pages:3.68:2014/03/20:netlink:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-×:LDP man-pages:3.68:2014/05/28:newlocale:3:::::
-○:LDP man-pages:3.68:2013/09/02:nextafter:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/09/02:nextafterf:3:nextafter:3:
-＠:LDP man-pages:3.68:2013/09/02:nextafterl:3:nextafter:3:
-＠:LDP man-pages:3.68:2013/09/02:nexttoward:3:nextafter:3:
-＠:LDP man-pages:3.68:2013/09/02:nexttowardf:3:nextafter:3:
-＠:LDP man-pages:3.68:2013/09/02:nexttowardl:3:nextafter:3:
-＠:LDP man-pages:3.68:2014/01/11:nftw:3:ftw:3:
-○:LDP man-pages:3.68:2014/05/28:nl_langinfo:3:2014/06/08::KY4N-UCD@asahi-net.or.jp:UCHIDA Norihiro:
-＠:LDP man-pages:3.68:2013/06/21:nrand48:3:drand48:3:
-＠:LDP man-pages:3.68:2013/09/09:nrand48_r:3:drand48_r:3:
-＠:LDP man-pages:3.68:2014/04/08:ntohl:3:byteorder:3:
-＠:LDP man-pages:3.68:2014/04/08:ntohs:3:byteorder:3:
-○:LDP man-pages:3.68:2014/04/06:offsetof:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2008/12/05:on_exit:3:2014/06/08:o:amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/04/06:open_memstream:3:fmemopen:3:
-＠:LDP man-pages:3.68:2014/04/06:open_wmemstream:3:fmemopen:3:
-○:LDP man-pages:3.68:2010/06/20:opendir:3:2014/06/08:o:amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2012/08/17:openlog:3:syslog:3:
-○:LDP man-pages:3.68:2010/06/13:openpty:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/09:optarg:3:getopt:3:
-＠:LDP man-pages:3.68:2014/05/09:opterr:3:getopt:3:
-＠:LDP man-pages:3.68:2014/05/09:optind:3:getopt:3:
-＠:LDP man-pages:3.68:2014/05/09:optopt:3:getopt:3:
-＠:LDP man-pages:3.68:2003/04/04:passwd2des:3:xcrypt:3:
-＠:LDP man-pages:3.68:2014/05/28:pathconf:3:fpathconf:3:
-＠:LDP man-pages:3.68:2013/04/19:pclose:3:popen:3:
-☆:LDP man-pages:3.67=>3.68:2014/05/28:perror:3:2014/06/04::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/09/26:pmap_getmaps:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:pmap_getport:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:pmap_rmtcall:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:pmap_set:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:pmap_unset:3:rpc:3:
-○:LDP man-pages:3.68:2013/04/19:popen:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/02/12:posix_fallocate:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2013/09/02:posix_memalign:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/04/20:posix_openpt:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/09/12:pow:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2008/08/11:pow10:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2008/08/11:pow10f:3:pow10:3:
-＠:LDP man-pages:3.68:2008/08/11:pow10l:3:pow10:3:
-＠:LDP man-pages:3.68:2010/09/12:powf:3:pow:3:
-＠:LDP man-pages:3.68:2010/09/12:powl:3:pow:3:
-○:LDP man-pages:3.68:2013/12/30:printf:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2007/07/26:profil:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2006/04/29:program_invocation_name:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2006/04/29:program_invocation_short_name:3:program_invocation_name:3:
-＠:LDP man-pages:3.68:2010/10/06:psiginfo:3:psignal:3:
-○:LDP man-pages:3.68:2010/10/06:psignal:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/11/11:pthread_attr_destroy:3:pthread_attr_init:3:
-＠:LDP man-pages:3.68:2014/05/28:pthread_attr_getaffinity_np:3:pthread_attr_setaffinity_np:3:
-＠:LDP man-pages:3.68:2014/05/28:pthread_attr_getdetachstate:3:pthread_attr_setdetachstate:3:
-＠:LDP man-pages:3.68:2014/05/28:pthread_attr_getguardsize:3:pthread_attr_setguardsize:3:
-＠:LDP man-pages:3.68:2014/05/21:pthread_attr_getinheritsched:3:pthread_attr_setinheritsched:3:
-＠:LDP man-pages:3.68:2014/05/21:pthread_attr_getschedparam:3:pthread_attr_setschedparam:3:
-＠:LDP man-pages:3.68:2014/05/21:pthread_attr_getschedpolicy:3:pthread_attr_setschedpolicy:3:
-＠:LDP man-pages:3.68:2014/05/28:pthread_attr_getscope:3:pthread_attr_setscope:3:
-＠:LDP man-pages:3.68:2014/05/28:pthread_attr_getstack:3:pthread_attr_setstack:3:
-＠:LDP man-pages:3.68:2014/05/28:pthread_attr_getstackaddr:3:pthread_attr_setstackaddr:3:
-＠:LDP man-pages:3.68:2014/05/28:pthread_attr_getstacksize:3:pthread_attr_setstacksize:3:
-○:LDP man-pages:3.68:2008/11/11:pthread_attr_init:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/28:pthread_attr_setaffinity_np:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/28:pthread_attr_setdetachstate:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/28:pthread_attr_setguardsize:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/21:pthread_attr_setinheritsched:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/21:pthread_attr_setschedparam:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/21:pthread_attr_setschedpolicy:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/28:pthread_attr_setscope:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/28:pthread_attr_setstack:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/28:pthread_attr_setstackaddr:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/28:pthread_attr_setstacksize:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2008/11/17:pthread_cancel:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/11/24:pthread_cleanup_pop:3:pthread_cleanup_push:3:
-＠:LDP man-pages:3.68:2014/05/28:pthread_cleanup_pop_restore_np:3:pthread_cleanup_push_defer_np:3:
-○:LDP man-pages:3.68:2008/11/24:pthread_cleanup_push:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/28:pthread_cleanup_push_defer_np:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/28:pthread_create:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2008/11/27:pthread_detach:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/23:pthread_equal:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/23:pthread_exit:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/23:pthread_getaffinity_np:3:pthread_setaffinity_np:3:
-○:LDP man-pages:3.68:2010/09/10:pthread_getattr_np:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/23:pthread_getconcurrency:3:pthread_setconcurrency:3:
-○:LDP man-pages:3.68:2014/05/23:pthread_getcpuclockid:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:pthread_getname_np:3:pthread_setname_np:3:
-＠:LDP man-pages:3.68:2014/05/28:pthread_getschedparam:3:pthread_setschedparam:3:
-○:LDP man-pages:3.68:2008/11/27:pthread_join:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/13:pthread_kill:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/13:pthread_kill_other_threads_np:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/13:pthread_self:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/23:pthread_setaffinity_np:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/13:pthread_setcancelstate:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/13:pthread_setcanceltype:3:pthread_setcancelstate:3:
-○:LDP man-pages:3.68:2014/05/23:pthread_setconcurrency:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/28:pthread_setname_np:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/28:pthread_setschedparam:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/28:pthread_setschedprio:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/19:pthread_sigmask:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/28:pthread_sigqueue:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/19:pthread_testcancel:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/10:pthread_timedjoin_np:3:pthread_tryjoin_np:3:
-○:LDP man-pages:3.68:2010/09/10:pthread_tryjoin_np:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/13:pthread_yield:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/06/21:ptsname:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/06/21:ptsname_r:3:ptsname:3:
-＠:LDP man-pages:3.68:2014/01/11:putc:3:puts:3:
-＠:LDP man-pages:3.68:2008/08/29:putc_unlocked:3:unlocked_stdio:3:
-＠:LDP man-pages:3.68:2014/01/11:putchar:3:puts:3:
-＠:LDP man-pages:3.68:2008/08/29:putchar_unlocked:3:unlocked_stdio:3:
-○:LDP man-pages:3.68:2013/04/19:putenv:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2003/09/09:putgrent:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2013/04/19:putpwent:3:2014/06/08::nishi@rpts.cl.nec.co.jp:HIROFUMI Nishizuka:
-○:LDP man-pages:3.68:2014/01/11:puts:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2014/05/28:putspent:3:getspnam:3:
-＠:LDP man-pages:3.68:2014/05/28:pututline:3:getutent:3:
-＠:LDP man-pages:3.68:2014/05/28:pututxline:3:getutent:3:
-＠:LDP man-pages:3.68:2010/09/26:putw:3:getw:3:
-＠:LDP man-pages:3.68:2013/04/19:putwc:3:fputwc:3:
-＠:LDP man-pages:3.68:2008/08/29:putwc_unlocked:3:unlocked_stdio:3:
-○:LDP man-pages:3.68:1999/07/25:putwchar:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2008/08/29:putwchar_unlocked:3:unlocked_stdio:3:
-＠:LDP man-pages:3.68:2013/09/02:pvalloc:3:posix_memalign:3:
-○:LDP man-pages:3.68:2014/03/11:qecvt:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2007/07/26:qecvt_r:3:ecvt_r:3:
-＠:LDP man-pages:3.68:2014/03/11:qfcvt:3:qecvt:3:
-＠:LDP man-pages:3.68:2007/07/26:qfcvt_r:3:ecvt_r:3:
-＠:LDP man-pages:3.68:2014/03/11:qgcvt:3:qecvt:3:
-○:LDP man-pages:3.68:2012/03/08:qsort:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2012/03/08:qsort_r:3:qsort:3:
-○:LDP man-pages:3.68:2007/12/28:queue:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/03/10:raise:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/01/18:rand:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/18:rand_r:3:rand:3:
-○:LDP man-pages:3.68:2014/03/25:random:3:2014/06/08::tyoshino@eng.toyo.ac.jp:YOSHINO Takashi:
-○:LDP man-pages:3.68:2014/03/25:random_r:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/03/10:rawmemchr:3:memchr:3:
-○:LDP man-pages:3.68:2014/05/28:rcmd:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:rcmd_af:3:rcmd:3:
-○:LDP man-pages:3.68:2014/05/28:re_comp:3:2014/06/08::nishi@rpts.cl.nec.co.jp:HIROFUMI Nishizuka:
-＠:LDP man-pages:3.68:2014/05/28:re_exec:3:re_comp:3:
-○:LDP man-pages:3.68:2013/06/21:readdir:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/06/21:readdir_r:3:readdir:3:
-＠:LDP man-pages:3.68:2014/05/21:realloc:3:malloc:3:
-○:LDP man-pages:3.68:2013/03/15:realpath:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/04/23:recno:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/02/11:regcomp:3:regex:3:
-＠:LDP man-pages:3.68:2013/02/11:regerror:3:regex:3:
-○:LDP man-pages:3.68:2013/02/11:regex:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/02/11:regexec:3:regex:3:
-＠:LDP man-pages:3.68:2013/02/11:regfree:3:regex:3:
-＠:LDP man-pages:3.68:2013/09/26:registerrpc:3:rpc:3:
-○:LDP man-pages:3.68:2010/09/20:remainder:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/20:remainderf:3:remainder:3:
-＠:LDP man-pages:3.68:2010/09/20:remainderl:3:remainder:3:
-○:LDP man-pages:3.68:2014/03/10:remove:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2010/09/09:remque:3:insque:3:
-○:LDP man-pages:3.68:2014/05/10:remquo:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/10:remquof:3:remquo:3:
-＠:LDP man-pages:3.68:2014/05/10:remquol:3:remquo:3:
-＠:LDP man-pages:3.68:2014/05/28:res_init:3:resolver:3:
-＠:LDP man-pages:3.68:2014/05/28:res_mkquery:3:resolver:3:
-＠:LDP man-pages:3.68:2014/05/28:res_query:3:resolver:3:
-＠:LDP man-pages:3.68:2014/05/28:res_querydomain:3:resolver:3:
-＠:LDP man-pages:3.68:2014/05/28:res_search:3:resolver:3:
-＠:LDP man-pages:3.68:2014/05/28:res_send:3:resolver:3:
-○:LDP man-pages:3.68:2014/05/28:resolver:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:rewind:3:fseek:3:
-○:LDP man-pages:3.68:2013/09/02:rewinddir:3:2014/06/08::nishi@rpts.cl.nec.co.jp:HIROFUMI Nishizuka:
-○:LDP man-pages:3.68:2014/05/28:rexec:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:rexec_af:3:rexec:3:
-＠:LDP man-pages:3.68:2014/04/01:rindex:3:index:3:
-○:LDP man-pages:3.68:2013/08/26:rint:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/08/26:rintf:3:rint:3:
-＠:LDP man-pages:3.68:2013/08/26:rintl:3:rint:3:
-○:LDP man-pages:3.68:2013/06/21:round:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/06/21:roundf:3:round:3:
-＠:LDP man-pages:3.68:2013/06/21:roundl:3:round:3:
-○:LDP man-pages:3.68:2013/09/26:rpc:3:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2007/07/26:rpmatch:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:rresvport:3:rcmd:3:
-＠:LDP man-pages:3.68:2014/05/28:rresvport_af:3:rcmd:3:
-○:LDP man-pages:3.68:2014/05/28:rtime:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2012/03/24:rtnetlink:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:ruserok:3:rcmd:3:
-＠:LDP man-pages:3.68:2014/05/28:ruserok_af:3:rcmd:3:
-○:LDP man-pages:3.68:2013/03/23:scalb:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/03/23:scalbf:3:scalb:3:
-＠:LDP man-pages:3.68:2013/03/23:scalbl:3:scalb:3:
-○:LDP man-pages:3.68:2013/06/21:scalbln:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/06/21:scalblnf:3:scalbln:3:
-＠:LDP man-pages:3.68:2013/06/21:scalblnl:3:scalbln:3:
-＠:LDP man-pages:3.68:2013/06/21:scalbn:3:scalbln:3:
-＠:LDP man-pages:3.68:2013/06/21:scalbnf:3:scalbln:3:
-＠:LDP man-pages:3.68:2013/06/21:scalbnl:3:scalbln:3:
-○:LDP man-pages:3.68:2014/05/28:scandir:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:scandirat:3:scandir:3:
-○:LDP man-pages:3.68:2014/01/11:scanf:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/10:sched_getcpu:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2012/08/14:secure_getenv:3:getenv:3:
-＠:LDP man-pages:3.68:2013/06/21:seed48:3:drand48:3:
-＠:LDP man-pages:3.68:2013/09/09:seed48_r:3:drand48_r:3:
-○:LDP man-pages:3.68:2013/09/09:seekdir:3:2014/06/08::nishi@rpts.cl.nec.co.jp:HIROFUMI Nishizuka:
-○:LDP man-pages:3.68:2012/05/13:sem_close:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/03/03:sem_destroy:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/03/03:sem_getvalue:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/03/10:sem_init:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/05/13:sem_open:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/26:sem_post:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/02/26:sem_timedwait:3:sem_wait:3:
-＠:LDP man-pages:3.68:2014/02/26:sem_trywait:3:sem_wait:3:
-○:LDP man-pages:3.68:2014/02/26:sem_unlink:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/26:sem_wait:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2003/09/09:setaliasent:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2014/02/18:setbuf:3:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2014/02/18:setbuffer:3:setbuf:3:
-＠:LDP man-pages:3.68:2014/04/08:setcontext:3:getcontext:3:
-○:LDP man-pages:3.68:2013/10/11:setenv:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2002/02/28:setfsent:3:getfsent:3:
-＠:LDP man-pages:3.68:2013/06/21:setgrent:3:getgrent:3:
-＠:LDP man-pages:3.68:2014/03/11:sethostent:3:gethostbyname:3:
-＠:LDP man-pages:3.68:2010/09/20:sethostid:3:gethostid:3:
-○:LDP man-pages:3.68:2014/01/07:setjmp:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2013/07/22:setkey:3:encrypt:3:
-＠:LDP man-pages:3.68:2013/07/22:setkey_r:3:encrypt:3:
-＠:LDP man-pages:3.68:2014/02/18:setlinebuf:3:setbuf:3:
-☆:LDP man-pages:3.67=>3.68:2014/05/28:setlocale:3:2014/06/04::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2001/10/05:setlogmask:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2009/09/15:setmntent:3:getmntent:3:
-＠:LDP man-pages:3.68:2008/08/19:setnetent:3:getnetent:3:
-○:LDP man-pages:3.68:2014/05/28:setnetgrent:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/08/19:setprotoent:3:getprotoent:3:
-＠:LDP man-pages:3.68:2013/06/21:setpwent:3:getpwent:3:
-＠:LDP man-pages:3.68:2014/05/28:setrpcent:3:getrpcent:3:
-＠:LDP man-pages:3.68:2008/08/19:setservent:3:getservent:3:
-＠:LDP man-pages:3.68:2014/05/28:setspent:3:getspnam:3:
-＠:LDP man-pages:3.68:2014/03/25:setstate:3:random:3:
-＠:LDP man-pages:3.68:2014/03/25:setstate_r:3:random_r:3:
-＠:LDP man-pages:3.68:2013/07/22:setttyent:3:getttyent:3:
-＠:LDP man-pages:3.68:2013/06/21:setusershell:3:getusershell:3:
-＠:LDP man-pages:3.68:2014/05/28:setutent:3:getutent:3:
-＠:LDP man-pages:3.68:2014/05/28:setutxent:3:getutent:3:
-＠:LDP man-pages:3.68:2014/02/18:setvbuf:3:setbuf:3:
-＠:LDP man-pages:3.68:2014/05/28:sgetspent:3:getspnam:3:
-＠:LDP man-pages:3.68:2014/05/28:sgetspent_r:3:getspnam:3:
-○:LDP man-pages:3.68:2009/02/25:shm_open:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2009/02/25:shm_unlink:3:shm_open:3:
-＠:LDP man-pages:3.68:2014/04/14:sigaddset:3:sigsetops:3:
-＠:LDP man-pages:3.68:2014/04/14:sigandset:3:sigsetops:3:
-＠:LDP man-pages:3.68:2014/05/28:sigblock:3:sigvec:3:
-＠:LDP man-pages:3.68:2014/04/14:sigdelset:3:sigsetops:3:
-＠:LDP man-pages:3.68:2014/04/14:sigemptyset:3:sigsetops:3:
-＠:LDP man-pages:3.68:2014/04/14:sigfillset:3:sigsetops:3:
-＠:LDP man-pages:3.68:2014/05/28:siggetmask:3:sigvec:3:
-＠:LDP man-pages:3.68:2010/09/20:sighold:3:sigset:3:
-＠:LDP man-pages:3.68:2010/09/20:sigignore:3:sigset:3:
-○:LDP man-pages:3.68:2013/04/19:siginterrupt:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-＠:LDP man-pages:3.68:2014/04/14:sigisemptyset:3:sigsetops:3:
-＠:LDP man-pages:3.68:2014/04/14:sigismember:3:sigsetops:3:
-＠:LDP man-pages:3.68:2009/01/13:siglongjmp:3:longjmp:3:
-＠:LDP man-pages:3.68:2014/05/28:sigmask:3:sigvec:3:
-○:LDP man-pages:3.68:2013/07/04:signbit:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/18:signgam:3:lgamma:3:
-○:LDP man-pages:3.68:2009/02/04:significand:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2009/02/04:significandf:3:significand:3:
-＠:LDP man-pages:3.68:2009/02/04:significandl:3:significand:3:
-＠:LDP man-pages:3.68:2014/04/14:sigorset:3:sigsetops:3:
-○:LDP man-pages:3.68:2014/01/07:sigpause:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/12/16:sigqueue:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/20:sigrelse:3:sigset:3:
-○:LDP man-pages:3.68:2010/09/20:sigset:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/07:sigsetjmp:3:setjmp:3:
-＠:LDP man-pages:3.68:2014/05/28:sigsetmask:3:sigvec:3:
-○:LDP man-pages:3.68:2014/04/14:sigsetops:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/26:sigstack:3:sigaltstack:2:
-○:LDP man-pages:3.68:2014/05/28:sigvec:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/12/16:sigwait:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/12/16:sin:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/12/23:sincos:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/12/23:sincosf:3:sincos:3:
-＠:LDP man-pages:3.68:2013/12/23:sincosl:3:sincos:3:
-＠:LDP man-pages:3.68:2013/12/16:sinf:3:sin:3:
-○:LDP man-pages:3.68:2010/09/20:sinh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/20:sinhf:3:sinh:3:
-＠:LDP man-pages:3.68:2010/09/20:sinhl:3:sinh:3:
-＠:LDP man-pages:3.68:2013/12/16:sinl:3:sin:3:
-○:LDP man-pages:3.68:2010/02/03:sleep:3:2014/06/08::tyoshino@eng.toyo.ac.jp:YOSHINO Takashi:
-＠:LDP man-pages:3.68:2013/12/30:snprintf:3:printf:3:
-○:LDP man-pages:3.68:2014/02/28:sockatmark:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2013/12/30:sprintf:3:printf:3:
-○:LDP man-pages:3.68:2010/09/20:sqrt:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/20:sqrtf:3:sqrt:3:
-＠:LDP man-pages:3.68:2010/09/20:sqrtl:3:sqrt:3:
-＠:LDP man-pages:3.68:2014/01/18:srand:3:rand:3:
-＠:LDP man-pages:3.68:2013/06/21:srand48:3:drand48:3:
-＠:LDP man-pages:3.68:2013/09/09:srand48_r:3:drand48_r:3:
-＠:LDP man-pages:3.68:2014/03/25:srandom:3:random:3:
-＠:LDP man-pages:3.68:2014/03/25:srandom_r:3:random_r:3:
-＠:LDP man-pages:3.68:2014/01/11:sscanf:3:scanf:3:
-＠:LDP man-pages:3.68:2007/07/26:ssignal:3:gsignal:3:
-○:LDP man-pages:3.68:2013/09/26:statvfs:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2013/12/10:stdarg:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2008/07/14:stderr:3:stdin:3:
-○:LDP man-pages:3.68:2008/07/14:stdin:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2001/12/26:stdio:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2013/06/21:stdio_ext:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2008/07/14:stdout:3:stdin:3:
-○:LDP man-pages:3.68:2014/05/10:stpcpy:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/10:stpncpy:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-○:LDP man-pages:3.68:2014/05/10:strcasecmp:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/22:strcasestr:3:strstr:3:
-○:LDP man-pages:3.68:2014/01/20:strcat:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/01/20:strchr:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/20:strchrnul:3:strchr:3:
-○:LDP man-pages:3.68:2014/01/20:strcmp:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/09/20:strcoll:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/21:strcpy:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/02/28:strcspn:3:strspn:3:
-○:LDP man-pages:3.68:2013/04/19:strdup:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/04/19:strdupa:3:strdup:3:
-○:LDP man-pages:3.68:2014/03/18:strerror:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/03/18:strerror_r:3:strerror:3:
-○:LDP man-pages:3.68:2000/12/05:strfmon:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2010/09/20:strfry:3:2014/06/08::motoki@hal.t.u-tokyo.ac.jp:Akihiro Motoki:
-○:LDP man-pages:3.68:2014/03/18:strftime:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/01/04:string:3:2014/06/08::yoshino@civil.jcn.nihon-u.ac.jp:YOSHINO Takashi:
-○:LDP man-pages:3.68:2014/02/25:strlen:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/10:strncasecmp:3:strcasecmp:3:
-＠:LDP man-pages:3.68:2014/01/20:strncat:3:strcat:3:
-＠:LDP man-pages:3.68:2014/01/20:strncmp:3:strcmp:3:
-＠:LDP man-pages:3.68:2014/05/21:strncpy:3:strcpy:3:
-＠:LDP man-pages:3.68:2013/04/19:strndup:3:strdup:3:
-＠:LDP man-pages:3.68:2013/04/19:strndupa:3:strdup:3:
-○:LDP man-pages:3.68:2014/02/25:strnlen:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/25:strpbrk:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/01/17:strptime:3:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2014/01/20:strrchr:3:strchr:3:
-○:LDP man-pages:3.68:2014/02/25:strsep:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2010/09/15:strsignal:3:2014/06/08::argrath@yo.rim.or.jp:Kentaro Shirakata:
-○:LDP man-pages:3.68:2014/02/28:strspn:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/01/22:strstr:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2014/01/22:strtod:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/22:strtof:3:strtod:3:
-○:LDP man-pages:3.68:2014/01/22:strtoimax:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2013/05/19:strtok:3:2014/06/08:o:amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/05/19:strtok_r:3:strtok:3:
-○:LDP man-pages:3.68:2014/03/18:strtol:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/22:strtold:3:strtod:3:
-＠:LDP man-pages:3.68:2014/03/18:strtoll:3:strtol:3:
-＠:LDP man-pages:3.68:2014/03/18:strtoq:3:strtol:3:
-○:LDP man-pages:3.68:2014/03/18:strtoul:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/03/18:strtoull:3:strtoul:3:
-＠:LDP man-pages:3.68:2014/01/22:strtoumax:3:strtoimax:3:
-＠:LDP man-pages:3.68:2014/03/18:strtouq:3:strtoul:3:
-○:LDP man-pages:3.68:2001/12/19:strverscmp:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/05/10:strxfrm:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/09/26:svc_destroy:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:svc_freeargs:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:svc_getargs:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:svc_getcaller:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:svc_getreq:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:svc_getreqset:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:svc_register:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:svc_run:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:svc_sendreply:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:svc_unregister:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:svcerr_auth:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:svcerr_decode:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:svcerr_noproc:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:svcerr_noprog:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:svcerr_progvers:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:svcerr_systemerr:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:svcerr_weakauth:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:svcfd_create:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:svcraw_create:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:svctcp_create:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:svcudp_bufcreate:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:svcudp_create:3:rpc:3:
-○:LDP man-pages:3.68:2014/02/25:swab:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2014/05/28:swapcontext:3:makecontext:3:
-＠:LDP man-pages:3.68:2014/03/19:swprintf:3:wprintf:3:
-＠:LDP man-pages:3.68:2014/05/28:sys_errlist:3:perror:3:
-＠:LDP man-pages:3.68:2014/05/28:sys_nerr:3:perror:3:
-○:LDP man-pages:3.68:2014/03/20:sysconf:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/08/17:syslog:3:2014/06/08:o:amotoki@gmail.com:Akihiro MOTOKI:
-☆:LDP man-pages:3.65=>3.68:2014/05/10:system:3:2014/04/24:o:amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/01/06:sysv_signal:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/01/06:tan:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/06:tanf:3:tan:3:
-○:LDP man-pages:3.68:2014/01/07:tanh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/07:tanhf:3:tanh:3:
-＠:LDP man-pages:3.68:2014/01/07:tanhl:3:tanh:3:
-＠:LDP man-pages:3.68:2014/01/06:tanl:3:tan:3:
-＠:LDP man-pages:3.68:2014/05/08:tcdrain:3:termios:3:
-＠:LDP man-pages:3.68:2014/05/08:tcflow:3:termios:3:
-＠:LDP man-pages:3.68:2014/05/08:tcflush:3:termios:3:
-＠:LDP man-pages:3.68:2014/05/08:tcgetattr:3:termios:3:
-○:LDP man-pages:3.68:2014/01/13:tcgetpgrp:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/01/13:tcgetsid:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/08:tcsendbreak:3:termios:3:
-＠:LDP man-pages:3.68:2014/05/08:tcsetattr:3:termios:3:
-＠:LDP man-pages:3.68:2014/01/13:tcsetpgrp:3:tcgetpgrp:3:
-＠:LDP man-pages:3.68:2014/05/28:tdelete:3:tsearch:3:
-＠:LDP man-pages:3.68:2014/05/28:tdestroy:3:tsearch:3:
-○:LDP man-pages:3.68:2013/09/02:telldir:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/27:tempnam:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/08:termios:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:tfind:3:tsearch:3:
-○:LDP man-pages:3.68:2010/09/20:tgamma:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/09/20:tgammaf:3:tgamma:3:
-＠:LDP man-pages:3.68:2010/09/20:tgammal:3:tgamma:3:
-○:LDP man-pages:3.68:2013/07/04:timegm:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-＠:LDP man-pages:3.68:2013/07/04:timelocal:3:timegm:3:
-○:LDP man-pages:3.68:2010/02/25:timeradd:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2010/02/25:timerclear:3:timeradd:3:
-＠:LDP man-pages:3.68:2010/02/25:timercmp:3:timeradd:3:
-＠:LDP man-pages:3.68:2010/02/25:timerisset:3:timeradd:3:
-＠:LDP man-pages:3.68:2010/02/25:timersub:3:timeradd:3:
-＠:LDP man-pages:3.68:2012/03/25:timezone:3:tzset:3:
-○:LDP man-pages:3.68:2008/07/14:tmpfile:3:2014/06/08:o:ysato@h4.dion.ne.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2014/02/27:tmpnam:3:2014/06/08:o:amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/02/27:tmpnam_r:3:tmpnam:3:
-○:LDP man-pages:3.68:2013/12/23:toascii:3:2014/06/08::nishi@rpts.cl.nec.co.jp:HIROFUMI Nishizuka:
-＠:LDP man-pages:3.68:2014/03/18:tolower:3:toupper:3:
-＠:LDP man-pages:3.68:2014/03/18:tolower_l:3:toupper:3:
-○:LDP man-pages:3.68:2014/03/18:toupper:3:2014/06/08::rui@linux.or.jp:Ueyama Rui:
-＠:LDP man-pages:3.68:2014/03/18:toupper_l:3:toupper:3:
-○:LDP man-pages:3.68:2013/12/24:towctrans:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2014/03/18:towlower:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-＠:LDP man-pages:3.68:2014/03/18:towlower_l:3:towlower:3:
-○:LDP man-pages:3.68:2014/03/18:towupper:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-＠:LDP man-pages:3.68:2014/03/18:towupper_l:3:towupper:3:
-○:LDP man-pages:3.68:2013/06/21:trunc:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/06/21:truncf:3:trunc:3:
-＠:LDP man-pages:3.68:2013/06/21:truncl:3:trunc:3:
-○:LDP man-pages:3.68:2014/05/28:tsearch:3:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2013/06/21:ttyname:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2013/06/21:ttyname_r:3:ttyname:3:
-○:LDP man-pages:3.68:2013/07/22:ttyslot:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2014/05/28:twalk:3:tsearch:3:
-＠:LDP man-pages:3.68:2012/03/25:tzname:3:tzset:3:
-○:LDP man-pages:3.68:2012/03/25:tzset:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/12/23:ualarm:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:ulckpwdf:3:getspnam:3:
-○:LDP man-pages:3.68:2008/08/06:ulimit:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2012/12/21:undocumented:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/12/31:ungetc:3:fgetc:3:
-○:LDP man-pages:3.68:2013/12/09:ungetwc:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-○:LDP man-pages:3.68:2008/08/29:unlocked_stdio:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/12/09:unlockpt:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/10/11:unsetenv:3:setenv:3:
-○:LDP man-pages:3.68:2008/07/02:updwtmp:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-＠:LDP man-pages:3.68:2008/07/02:updwtmpx:3:updwtmp:3:
-×:LDP man-pages:3.68:2014/03/10:uselocale:3:::::
-○:LDP man-pages:3.68:2013/12/10:usleep:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:utmpname:3:getutent:3:
-＠:LDP man-pages:3.68:2014/05/28:utmpxname:3:getutent:3:
-＠:LDP man-pages:3.68:2013/12/10:va_arg:3:stdarg:3:
-＠:LDP man-pages:3.68:2013/12/10:va_copy:3:stdarg:3:
-＠:LDP man-pages:3.68:2013/12/10:va_end:3:stdarg:3:
-＠:LDP man-pages:3.68:2013/12/10:va_start:3:stdarg:3:
-＠:LDP man-pages:3.68:2013/09/02:valloc:3:posix_memalign:3:
-＠:LDP man-pages:3.68:2013/06/21:vasprintf:3:asprintf:3:
-＠:LDP man-pages:3.68:2010/09/15:vdprintf:3:dprintf:3:
-＠:LDP man-pages:3.68:2013/12/30:verr:3:err:3:
-＠:LDP man-pages:3.68:2013/12/30:verrx:3:err:3:
-＠:LDP man-pages:3.68:2014/05/28:versionsort:3:scandir:3:
-＠:LDP man-pages:3.68:2013/12/30:vfprintf:3:printf:3:
-＠:LDP man-pages:3.68:2014/01/11:vfscanf:3:scanf:3:
-＠:LDP man-pages:3.68:2014/03/19:vfwprintf:3:wprintf:3:
-＠:LDP man-pages:3.68:2014/05/28:vlimit:3:getrlimit:2:
-＠:LDP man-pages:3.68:2013/12/30:vprintf:3:printf:3:
-＠:LDP man-pages:3.68:2014/01/11:vscanf:3:scanf:3:
-＠:LDP man-pages:3.68:2013/12/30:vsnprintf:3:printf:3:
-＠:LDP man-pages:3.68:2013/12/30:vsprintf:3:printf:3:
-＠:LDP man-pages:3.68:2014/01/11:vsscanf:3:scanf:3:
-＠:LDP man-pages:3.68:2014/03/19:vswprintf:3:wprintf:3:
-＠:LDP man-pages:3.68:2012/08/17:vsyslog:3:syslog:3:
-＠:LDP man-pages:3.68:2014/05/10:vtimes:3:getrusage:2:
-＠:LDP man-pages:3.68:2013/12/30:vwarn:3:err:3:
-＠:LDP man-pages:3.68:2013/12/30:vwarnx:3:err:3:
-＠:LDP man-pages:3.68:2014/03/19:vwprintf:3:wprintf:3:
-＠:LDP man-pages:3.68:2013/12/30:warn:3:err:3:
-＠:LDP man-pages:3.68:2013/12/30:warnx:3:err:3:
-○:LDP man-pages:3.68:2013/12/10:wcpcpy:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/12/16:wcpncpy:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2014/03/18:wcrtomb:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/01/22:wcscasecmp:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2013/12/02:wcscat:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2013/12/02:wcschr:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2013/12/02:wcscmp:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2013/12/02:wcscpy:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2013/12/02:wcscspn:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2013/04/19:wcsdup:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2013/11/21:wcslen:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/01/22:wcsncasecmp:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2013/11/25:wcsncat:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2013/11/25:wcsncmp:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/11/25:wcsncpy:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2013/11/25:wcsnlen:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2014/03/18:wcsnrtombs:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/11/18:wcspbrk:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2013/11/19:wcsrchr:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2014/03/18:wcsrtombs:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/11/11:wcsspn:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2013/11/12:wcsstr:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2014/01/22:wcstoimax:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2013/11/18:wcstok:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2014/03/18:wcstombs:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/22:wcstoumax:3:wcstoimax:3:
-○:LDP man-pages:3.68:2014/01/22:wcswidth:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2011/09/22:wctob:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2014/03/18:wctomb:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-○:LDP man-pages:3.68:2014/01/22:wctrans:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2014/01/22:wctype:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2014/01/22:wcwidth:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/11/05:wmemchr:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2013/11/05:wmemcmp:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2013/11/11:wmemcpy:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2013/11/11:wmemmove:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-＠:LDP man-pages:3.68:2014/03/18:wmempcpy:3:mempcpy:3:
-○:LDP man-pages:3.68:2013/11/11:wmemset:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
-○:LDP man-pages:3.68:2008/07/14:wordexp:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2008/07/14:wordfree:3:wordexp:3:
-○:LDP man-pages:3.68:2014/03/19:wprintf:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-○:LDP man-pages:3.68:2003/04/04:xcrypt:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2003/04/04:xdecrypt:3:xcrypt:3:
-○:LDP man-pages:3.68:2007/12/30:xdr:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-＠:LDP man-pages:3.68:2013/09/26:xdr_accepted_reply:3:rpc:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_array:3:xdr:3:
-＠:LDP man-pages:3.68:2013/09/26:xdr_authunix_parms:3:rpc:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_bool:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_bytes:3:xdr:3:
-＠:LDP man-pages:3.68:2013/09/26:xdr_callhdr:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:xdr_callmsg:3:rpc:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_char:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_destroy:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_double:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_enum:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_float:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_free:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_getpos:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_inline:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_int:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_long:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_opaque:3:xdr:3:
-＠:LDP man-pages:3.68:2013/09/26:xdr_opaque_auth:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:xdr_pmap:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:xdr_pmaplist:3:rpc:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_pointer:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_reference:3:xdr:3:
-＠:LDP man-pages:3.68:2013/09/26:xdr_rejected_reply:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:xdr_replymsg:3:rpc:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_setpos:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_short:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_string:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_u_char:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_u_int:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_u_long:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_u_short:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_union:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_vector:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_void:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdr_wrapstring:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdrmem_create:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdrrec_create:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdrrec_endofrecord:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdrrec_eof:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdrrec_skiprecord:3:xdr:3:
-＠:LDP man-pages:3.68:2007/12/30:xdrstdio_create:3:xdr:3:
-＠:LDP man-pages:3.68:2003/04/04:xencrypt:3:xcrypt:3:
-＠:LDP man-pages:3.68:2013/09/26:xprt_register:3:rpc:3:
-＠:LDP man-pages:3.68:2013/09/26:xprt_unregister:3:rpc:3:
-○:LDP man-pages:3.68:2014/01/18:y0:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/18:y0f:3:y0:3:
-＠:LDP man-pages:3.68:2014/01/18:y0l:3:y0:3:
-＠:LDP man-pages:3.68:2014/01/18:y1:3:y0:3:
-＠:LDP man-pages:3.68:2014/01/18:y1f:3:y0:3:
-＠:LDP man-pages:3.68:2014/01/18:y1l:3:y0:3:
-＠:LDP man-pages:3.68:2014/01/18:yn:3:y0:3:
-＠:LDP man-pages:3.68:2014/01/18:ynf:3:y0:3:
-＠:LDP man-pages:3.68:2014/01/18:ynl:3:y0:3:
-×:LDP man-pages:3.68:2012/08/05:cciss:4:::::
-○:LDP man-pages:3.68:1994/10/31:console:4:2014/06/08:o:argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2012/08/05:console_codes:4:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2009/02/28:console_ioctl:4:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-×:LDP man-pages:3.68:2009/03/31:cpuid:4:::::
-○:LDP man-pages:3.68:2012/08/05:dsp56k:4:2014/06/08::sato@complex.eng.hokudai.ac.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2014/05/10:fd:4:2014/06/08:o:ishikawa@linux.or.jp:ISHIKAWA Mutsumi:
-○:LDP man-pages:3.68:2007/11/24:full:4:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:1992/12/17:hd:4:2014/06/08:o:ishikawa@linux.or.jp:ISHIKAWA Mutsumi:
-×:LDP man-pages:3.68:2012/08/05:hpsa:4:::::
-○:LDP man-pages:3.68:2010/09/04:initrd:4:2014/06/08:o:amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2007/10/23:intro:4:2014/06/08:o:ishikawa@linux.or.jp:ISHIKAWA Mutsumi:
-＠:LDP man-pages:3.68:1992/11/21:kmem:4:mem:4:
-○:LDP man-pages:3.68:1995/01/15:lp:4:2014/06/08:o:ishikawa@linux.or.jp:ISHIKAWA Mutsumi:
-○:LDP man-pages:3.68:1992/11/21:mem:4:2014/06/08:o:ishikawa@linux.or.jp:ISHIKAWA Mutsumi:
-○:LDP man-pages:3.68:1996/02/10:mouse:4:2014/06/08:o:ss236rx@ymg.urban.ne.jp:Shouichi Saito:
-○:LDP man-pages:3.68:2009/03/31:msr:4:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2009/02/23:null:4:2014/06/08:o:ishikawa@linux.or.jp:ISHIKAWA Mutsumi:
-＠:LDP man-pages:3.68:1992/11/21:port:4:mem:4:
-＠:LDP man-pages:3.68:2002/10/09:ptmx:4:pts:4:
-○:LDP man-pages:3.68:2002/10/09:pts:4:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:1992/11/21:ram:4:2014/06/08:o:ishikawa@linux.or.jp:ISHIKAWA Mutsumi:
-○:LDP man-pages:3.68:2013/03/15:random:4:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/02/25:rtc:4:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2012/05/03:sd:4:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/08/05:sk98lin:4:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/09/04:st:4:2014/06/08::nakano@st.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2003/04/07:tty:4:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:1992/12/19:ttyS:4:2014/06/08::ishikawa@linux.or.jp:ISHIKAWA Mutsumi:
-○:LDP man-pages:3.68:2013/11/12:tty_ioctl:4:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/03/15:urandom:4:random:4:
-○:LDP man-pages:3.68:2007/12/17:vcs:4:2014/06/08::sato@complex.eng.hokudai.ac.jp:Yuichi SATO:
-＠:LDP man-pages:3.68:2007/12/17:vcsa:4:vcs:4:
-○:LDP man-pages:3.68:2013/09/04:wavelan:4:2014/06/08::ishikawa@linux.or.jp:ISHIKAWA Mutsumi:
-＠:LDP man-pages:3.68:2009/02/23:zero:4:null:4:
-○:LDP man-pages:3.68:2008/06/15:acct:5:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:1994/11/28:charmap:5:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2014/05/28:core:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/08/09:dir_colors:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/04/17:elf:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/01/15:filesystems:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/15:fs:5:filesystems:5:
-○:LDP man-pages:3.68:2000/08/27:ftpusers:5:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2013/02/13:gai.conf:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/10/21:group:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2003/08/23:host.conf:5:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2002/06/16:hosts:5:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2003/08/24:hosts.equiv:5:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2007/10/23:intro:5:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-＠:LDP man-pages:3.68:2013/02/12:ipc:5:svipc:7:
-○:LDP man-pages:3.68:1993/07/24:issue:5:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-☆:LDP man-pages:3.54=>3.68:2014/05/23:locale:5:2013/03/25::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:1992/12/29:motd:5:2014/06/08::nagoya@cc.hit-u.ac.jp:Hiroaki Nagoya:
-○:LDP man-pages:3.68:2008/09/04:networks:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/04/16:nologin:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/07:nscd.conf:5:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-×:LDP man-pages:3.68:2013/02/13:nss:5:::::
-○:LDP man-pages:3.68:2013/02/12:nsswitch.conf:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2012/08/05:numa_maps:5:numa:7:
-○:LDP man-pages:3.68:2014/02/11:passwd:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-☆:LDP man-pages:3.50=>3.68:2014/05/28:proc:5:2013/03/25::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/05/28:procfs:5:proc:5:
-○:LDP man-pages:3.68:2012/08/05:protocols:5:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:2014/02/22:resolv.conf:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/02/22:resolver:5:resolv.conf:5:
-○:LDP man-pages:3.68:1985/09/26:rpc:5:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
-○:LDP man-pages:3.68:1992/12/29:securetty:5:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/05/22:services:5:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro Motoki:
-○:LDP man-pages:3.68:2012/12/31:shells:5:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2007/09/30:slabinfo:5:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:1996/10/21:termcap:5:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2012/12/31:ttytype:5:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2012/05/04:tzfile:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/02/11:utmp:5:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2013/02/11:utmpx:5:utmp:5:
-＠:LDP man-pages:3.68:2013/02/11:wtmp:5:utmp:5:
-○:LDP man-pages:3.68:2007/10/23:intro:6:2014/06/08::pessi@kmc.kyoto-u.ac.jp:II Ryouta:
-○:LDP man-pages:3.68:2014/04/06:aio:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/16:armscii-8:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2008/11/25:arp:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/26:ascii:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/09/19:boot:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/08/01:bootparam:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-☆:LDP man-pages:3.67=>3.68:2014/05/21:capabilities:7:2014/06/04::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/05/28:charsets:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2011/09/16:complex:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/16:cp1251:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-×:LDP man-pages:3.68:2014/05/21:cpuset:7:::::
-○:LDP man-pages:3.68:2014/05/21:credentials:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2008/11/20:ddp:7:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2014/01/18:environ:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/04/17:epoll:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-×:LDP man-pages:3.68:2014/05/21:fanotify:7:::::
-○:LDP man-pages:3.68:2014/03/20:feature_test_macros:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2008/12/03:fifo:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/08/05:futex:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/04/20:glibc:7:libc:7:
-○:LDP man-pages:3.68:2012/07/28:glob:7:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2012/08/05:hier:7:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2010/11/07:hostname:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/05/10:icmp:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-☆:LDP man-pages:3.67=>3.68:2014/05/23:inotify:7:2014/06/04::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2007/10/23:intro:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-☆:LDP man-pages:3.65=>3.68:2014/05/10:ip:7:2014/04/24::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/12/16:ipv6:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/02/16:iso-8859-1:7:iso_8859-1:7:
-＠:LDP man-pages:3.68:2014/02/16:iso-8859-10:7:iso_8859-10:7:
-＠:LDP man-pages:3.68:2014/02/16:iso-8859-11:7:iso_8859-11:7:
-＠:LDP man-pages:3.68:2014/02/16:iso-8859-13:7:iso_8859-13:7:
-＠:LDP man-pages:3.68:2014/02/16:iso-8859-14:7:iso_8859-14:7:
-＠:LDP man-pages:3.68:2014/02/16:iso-8859-15:7:iso_8859-15:7:
-＠:LDP man-pages:3.68:2014/02/16:iso-8859-16:7:iso_8859-16:7:
-＠:LDP man-pages:3.68:2014/02/16:iso-8859-2:7:iso_8859-2:7:
-＠:LDP man-pages:3.68:2014/02/16:iso-8859-3:7:iso_8859-3:7:
-＠:LDP man-pages:3.68:2014/02/16:iso-8859-4:7:iso_8859-4:7:
-＠:LDP man-pages:3.68:2014/02/16:iso-8859-5:7:iso_8859-5:7:
-＠:LDP man-pages:3.68:2014/02/16:iso-8859-6:7:iso_8859-6:7:
-＠:LDP man-pages:3.68:2014/02/16:iso-8859-7:7:iso_8859-7:7:
-＠:LDP man-pages:3.68:2014/02/16:iso-8859-8:7:iso_8859-8:7:
-＠:LDP man-pages:3.68:2014/02/16:iso-8859-9:7:iso_8859-9:7:
-○:LDP man-pages:3.68:2014/02/16:iso_8859-1:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/16:iso_8859-10:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/16:iso_8859-11:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/16:iso_8859-13:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/16:iso_8859-14:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/16:iso_8859-15:7:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-○:LDP man-pages:3.68:2014/02/16:iso_8859-16:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/16:iso_8859-2:7:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-○:LDP man-pages:3.68:2014/02/16:iso_8859-3:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/16:iso_8859-4:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/16:iso_8859-5:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/16:iso_8859-6:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/16:iso_8859-7:7:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
-○:LDP man-pages:3.68:2014/02/16:iso_8859-8:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/16:iso_8859-9:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/02/16:iso_8859_1:7:iso_8859-1:7:
-＠:LDP man-pages:3.68:2014/02/16:iso_8859_10:7:iso_8859-10:7:
-＠:LDP man-pages:3.68:2014/02/16:iso_8859_11:7:iso_8859-11:7:
-＠:LDP man-pages:3.68:2014/02/16:iso_8859_13:7:iso_8859-13:7:
-＠:LDP man-pages:3.68:2014/02/16:iso_8859_14:7:iso_8859-14:7:
-＠:LDP man-pages:3.68:2014/02/16:iso_8859_15:7:iso_8859-15:7:
-＠:LDP man-pages:3.68:2014/02/16:iso_8859_16:7:iso_8859-16:7:
-＠:LDP man-pages:3.68:2014/02/16:iso_8859_2:7:iso_8859-2:7:
-＠:LDP man-pages:3.68:2014/02/16:iso_8859_3:7:iso_8859-3:7:
-＠:LDP man-pages:3.68:2014/02/16:iso_8859_4:7:iso_8859-4:7:
-＠:LDP man-pages:3.68:2014/02/16:iso_8859_5:7:iso_8859-5:7:
-＠:LDP man-pages:3.68:2014/02/16:iso_8859_6:7:iso_8859-6:7:
-＠:LDP man-pages:3.68:2014/02/16:iso_8859_7:7:iso_8859-7:7:
-＠:LDP man-pages:3.68:2014/02/16:iso_8859_8:7:iso_8859-8:7:
-＠:LDP man-pages:3.68:2014/02/16:iso_8859_9:7:iso_8859-9:7:
-○:LDP man-pages:3.68:2014/02/16:koi8-r:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/03/18:koi8-u:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/02/16:latin1:7:iso_8859-1:7:
-＠:LDP man-pages:3.68:2014/02/16:latin10:7:iso_8859-16:7:
-＠:LDP man-pages:3.68:2014/02/16:latin2:7:iso_8859-2:7:
-＠:LDP man-pages:3.68:2014/02/16:latin3:7:iso_8859-3:7:
-＠:LDP man-pages:3.68:2014/02/16:latin4:7:iso_8859-4:7:
-＠:LDP man-pages:3.68:2014/02/16:latin5:7:iso_8859-9:7:
-＠:LDP man-pages:3.68:2014/02/16:latin6:7:iso_8859-10:7:
-＠:LDP man-pages:3.68:2014/02/16:latin7:7:iso_8859-13:7:
-＠:LDP man-pages:3.68:2014/02/16:latin8:7:iso_8859-14:7:
-＠:LDP man-pages:3.68:2014/02/16:latin9:7:iso_8859-15:7:
-○:LDP man-pages:3.68:2014/04/20:libc:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-☆:LDP man-pages:3.67=>3.68:2014/05/28:locale:7:2014/06/04::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2004/09/15:mailaddr:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/08/05:man:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/03/16:man-pages:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2008/08/11:math_error:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:0000/00/00:mdoc:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:0000/00/00:mdoc.samples:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2009/09/27:mq_overview:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/01/24:netdevice:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/03/15:netlink:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/08/05:numa:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2011/09/09:operator:7:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-☆:LDP man-pages:3.65=>3.68:2014/04/28:packet:7:2014/04/27::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2009/12/05:path_resolution:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2005/12/08:pipe:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2007/12/21:posixoptions:7:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2014/05/21:pthreads:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2005/10/10:pty:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/05/10:raw:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2009/01/12:regex:7:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-×:LDP man-pages:3.68:2012/07/07:rtld-audit:7:::::
-○:LDP man-pages:3.68:2013/03/05:rtnetlink:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-×:LDP man-pages:3.68:2014/05/13:sched:7:::::
-○:LDP man-pages:3.68:2012/05/13:sem_overview:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2010/09/10:shm_overview:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2011/09/09:sigevent:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/07/30:signal:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/02/21:socket:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-×:LDP man-pages:3.68:2007/12/20:spufs:7:::::
-○:LDP man-pages:3.68:2014/01/15:standards:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2000/11/16:suffixes:7:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
-○:LDP man-pages:3.68:2013/02/12:svipc:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-×:LDP man-pages:3.68:2014/04/06:symlink:7:::::
-○:LDP man-pages:3.68:2014/03/31:tcp:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/02/12:termio:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/10/28:time:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/02/16:tis-620:7:iso_8859-11:7:
-○:LDP man-pages:3.68:2013/07/31:udp:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2008/12/03:udplite:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/08/05:unicode:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/08/05:units:7:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2012/05/10:unix:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2014/03/18:uri:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/03/18:url:7:uri:7:
-＠:LDP man-pages:3.68:2014/03/18:urn:7:uri:7:
-○:LDP man-pages:3.68:2014/02/26:utf-8:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/02/26:utf8:7:utf-8:7:
-×:LDP man-pages:3.68:2014/02/01:vdso:7:::::
-○:LDP man-pages:3.68:2012/08/05:x25:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2007/10/23:intro:8:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
-＠:LDP man-pages:3.68:2014/01/08:ld-linux:8:ld.so:8:
-＠:LDP man-pages:3.68:2014/01/08:ld-linux.so:8:ld.so:8:
-○:LDP man-pages:3.68:2014/01/08:ld.so:8:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/05/10:ldconfig:8:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2012/05/10:nscd:8:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2013/02/10:sln:8:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
-○:LDP man-pages:3.68:2007/05/18:tzselect:8:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
-☆:LDP man-pages:3.50=>3.68:2013/02/12:zdump:8:2013/03/26::nakano@apm.seikei.ac.jp:NAKANO Takeo:
-○:LDP man-pages:3.68:2010/02/25:zic:8:2014/06/08::sato@complex.eng.hokudai.ac.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2013/03/15:getent:1:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2014/07/08:iconv:1:::::
+☆:LDP man-pages:3.68=>3.75:2007/11/15:intro:1:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:ldd:1:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
+×:LDP man-pages:3.75:2014/05/28:locale:1:::::
+×:LDP man-pages:3.75:2014/06/13:localedef:1:::::
+×:LDP man-pages:3.75:2014/09/06:memusage:1:::::
+×:LDP man-pages:3.75:2014/09/06:memusagestat:1:::::
+×:LDP man-pages:3.75:2014/09/01:mtrace:1:::::
+×:LDP man-pages:3.75:2014/09/27:pldd:1:::::
+×:LDP man-pages:3.75:2014/06/24:sprof:1:::::
+☆:LDP man-pages:3.68=>3.75:2008/11/14:time:1:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/20:_Exit:2:_exit:2:
+＠:LDP man-pages:3.75:2014/09/21:__clone2:2:clone:2:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:_exit:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2012/07/13:_llseek:2:llseek:2:
+＠:LDP man-pages:3.75:2014/08/19:_newselect:2:select:2:
+☆:LDP man-pages:3.68=>3.75:2007/12/19:_syscall:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2012/12/22:_sysctl:2:sysctl:2:
+☆:LDP man-pages:3.68=>3.75:2010/09/10:accept:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/10:accept4:2:accept:2:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:access:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2008/06/16:acct:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+×:LDP man-pages:3.75:2010/02/25:add_key:2:::::
+☆:LDP man-pages:3.68=>3.75:2014/05/28:adjtimex:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/02/12:afs_syscall:2:unimplemented:2:
+☆:LDP man-pages:3.68=>3.75:2014/02/23:alarm:2:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+☆:LDP man-pages:3.68=>3.75:2007/05/31:alloc_hugepages:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2007/12/26:arch_prctl:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/03:arm_fadvise:2:posix_fadvise:2:
+＠:LDP man-pages:3.75:2014/05/03:arm_fadvise64_64:2:posix_fadvise:2:
+＠:LDP man-pages:3.75:2014/08/19:arm_sync_file_range:2:sync_file_range:2:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:bdflush:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:bind:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/02/12:break:2:unimplemented:2:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:brk:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2007/05/26:cacheflush:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/03/11:capget:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/03/11:capset:2:capget:2:
+☆:LDP man-pages:3.68=>3.75:2010/11/25:chdir:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:chmod:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:chown:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:chown32:2:chown:2:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:chroot:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2013/12/28:clock_getres:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/12/28:clock_gettime:2:clock_getres:2:
+☆:LDP man-pages:3.68=>3.75:2013/07/30:clock_nanosleep:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/12/28:clock_settime:2:clock_getres:2:
+☆:LDP man-pages:3.68=>3.75:2014/09/21:clone:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/09/21:clone2:2:clone:2:
+☆:LDP man-pages:3.68=>3.75:2013/12/30:close:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/09/06:connect:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/10/02:creat:2:open:2:
+☆:LDP man-pages:3.65=>3.75:2014/05/10:create_module:2:2014/04/24::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.41=>3.75:2014/05/10:delete_module:2:2006/07/30::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/07/08:dup:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/07/08:dup2:2:dup:2:
+＠:LDP man-pages:3.75:2014/07/08:dup3:2:dup:2:
+☆:LDP man-pages:3.68=>3.75:2012/04/15:epoll_create:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2012/04/15:epoll_create1:2:epoll_create:2:
+☆:LDP man-pages:3.68=>3.75:2014/07/08:epoll_ctl:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:epoll_pwait:2:epoll_wait:2:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:epoll_wait:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/07/08:eventfd:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/07/08:eventfd2:2:eventfd:2:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:execve:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/20:exit:2:_exit:2:
+☆:LDP man-pages:3.68=>3.75:2008/11/27:exit_group:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/08/19:faccessat:2:access:2:
+＠:LDP man-pages:3.75:2014/05/03:fadvise64:2:posix_fadvise:2:
+＠:LDP man-pages:3.75:2014/05/03:fadvise64_64:2:posix_fadvise:2:
+☆:LDP man-pages:3.65=>3.75:2014/07/08:fallocate:2:2014/04/27::amotoki@gmail.com:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2014/10/02:fanotify_init:2:::::
+×:LDP man-pages:3.75:2014/10/02:fanotify_mark:2:::::
+＠:LDP man-pages:3.75:2013/02/12:fattach:2:unimplemented:2:
+＠:LDP man-pages:3.75:2010/11/25:fchdir:2:chdir:2:
+＠:LDP man-pages:3.75:2014/08/19:fchmod:2:chmod:2:
+＠:LDP man-pages:3.75:2014/08/19:fchmodat:2:chmod:2:
+＠:LDP man-pages:3.75:2014/08/19:fchown:2:chown:2:
+＠:LDP man-pages:3.75:2014/05/21:fchown32:2:fchown:2:
+＠:LDP man-pages:3.75:2014/08/19:fchownat:2:chown:2:
+☆:LDP man-pages:3.68=>3.75:2014/09/06:fcntl:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/09/06:fcntl64:2:fcntl:2:
+＠:LDP man-pages:3.75:2014/08/19:fdatasync:2:fsync:2:
+＠:LDP man-pages:3.75:2013/02/12:fdetach:2:unimplemented:2:
+＠:LDP man-pages:3.75:2014/04/06:fgetxattr:2:getxattr:2:
+＠:LDP man-pages:3.75:2014/05/10:finit_module:2:init_module:2:
+＠:LDP man-pages:3.75:2014/02/06:flistxattr:2:listxattr:2:
+☆:LDP man-pages:3.68=>3.75:2014/09/21:flock:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:fork:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2007/05/31:free_hugepages:2:alloc_hugepages:2:
+＠:LDP man-pages:3.75:2014/02/06:fremovexattr:2:removexattr:2:
+＠:LDP man-pages:3.75:2014/02/06:fsetxattr:2:setxattr:2:
+＠:LDP man-pages:3.75:2014/08/19:fstat:2:stat:2:
+＠:LDP man-pages:3.75:2014/08/19:fstat64:2:fstat:2:
+＠:LDP man-pages:3.75:2014/08/19:fstatat:2:stat:2:
+＠:LDP man-pages:3.75:2014/08/19:fstatat64:2:fstatat:2:
+＠:LDP man-pages:3.75:2014/06/13:fstatfs:2:statfs:2:
+＠:LDP man-pages:3.75:2014/06/13:fstatfs64:2:fstatfs:2:
+＠:LDP man-pages:3.75:2013/09/26:fstatvfs:2:statvfs:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:fsync:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/04/01:ftruncate:2:truncate:2:
+＠:LDP man-pages:3.75:2013/04/01:ftruncate64:2:ftruncate:2:
+☆:LDP man-pages:3.68=>3.75:2014/05/21:futex:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.54=>3.75:2012/05/10:futimesat:2:2013/03/25::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/10/18:get_kernel_syms:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2008/08/15:get_mempolicy:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2014/05/10:get_robust_list:2:::::
+☆:LDP man-pages:3.68=>3.75:2012/07/13:get_thread_area:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/04/08:getcontext:2:getcontext:3:
+☆:LDP man-pages:3.68=>3.75:2013/04/03:getcpu:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:getcwd:2:getcwd:3:
+☆:LDP man-pages:3.68=>3.75:2012/08/03:getdents:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2012/08/03:getdents64:2:getdents:2:
+☆:LDP man-pages:3.68=>3.75:2012/10/25:getdomainname:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+○:LDP man-pages:3.75:0000/00/00:getdtablesize:2:2007/01/14::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2010/11/22:getegid:2:getgid:2:
+＠:LDP man-pages:3.75:2010/11/22:getegid32:2:getegid:2:
+＠:LDP man-pages:3.75:2010/11/22:geteuid:2:getuid:2:
+＠:LDP man-pages:3.75:2010/11/22:geteuid32:2:geteuid:2:
+☆:LDP man-pages:3.68=>3.75:2010/11/22:getgid:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/11/22:getgid32:2:getgid:2:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:getgroups:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:getgroups32:2:getgroups:2:
+＠:LDP man-pages:3.75:2010/09/20:gethostid:2:gethostid:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:gethostname:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/07/08:getitimer:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/02/12:getmsg:2:unimplemented:2:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:getpagesize:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/02/12:getpeername:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/01/07:getpgid:2:setpgid:2:
+＠:LDP man-pages:3.75:2014/01/07:getpgrp:2:setpgid:2:
+☆:LDP man-pages:3.68=>3.75:2014/09/21:getpid:2:2014/06/08::suto@av.crl.sony.co.jp:SUTO, Mitsuaki:
+＠:LDP man-pages:3.75:2013/02/12:getpmsg:2:unimplemented:2:
+＠:LDP man-pages:3.75:2014/09/21:getppid:2:getpid:2:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:getpriority:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/11/22:getresgid:2:getresuid:2:
+＠:LDP man-pages:3.75:2010/11/22:getresgid32:2:getresgid:2:
+☆:LDP man-pages:3.68=>3.75:2010/11/22:getresuid:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/11/22:getresuid32:2:getresuid:2:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:getrlimit:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/10:getrusage:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/09/26:getsid:2:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2008/12/03:getsockname:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2014/04/28:getsockopt:2:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2014/02/11:gettid:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/04/26:gettimeofday:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/11/22:getuid:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/11/22:getuid32:2:getuid:2:
+×:LDP man-pages:3.75:2014/09/21:getunwind:2:::::
+☆:LDP man-pages:3.68=>3.75:2014/04/06:getxattr:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/02/12:gtty:2:unimplemented:2:
+☆:LDP man-pages:3.68=>3.75:2012/12/31:idle:2:2014/06/08::argrath@yo.rim.or.jp:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2012/12/31:inb:2:outb:2:
+＠:LDP man-pages:3.75:2012/12/31:inb_p:2:outb:2:
+☆:LDP man-pages:3.41=>3.75:2014/05/10:init_module:2:2006/07/30::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2012/12/31:inl:2:outb:2:
+＠:LDP man-pages:3.75:2012/12/31:inl_p:2:outb:2:
+☆:LDP man-pages:3.68=>3.75:2014/07/08:inotify_add_watch:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/03/28:inotify_init:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/03/28:inotify_init1:2:inotify_init:2:
+☆:LDP man-pages:3.68=>3.75:2010/10/15:inotify_rm_watch:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2012/12/31:insb:2:outb:2:
+＠:LDP man-pages:3.75:2012/12/31:insl:2:outb:2:
+＠:LDP man-pages:3.75:2012/12/31:insw:2:outb:2:
+☆:LDP man-pages:3.68=>3.75:2014/02/20:intro:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2012/12/31:inw:2:outb:2:
+＠:LDP man-pages:3.75:2012/12/31:inw_p:2:outb:2:
+☆:LDP man-pages:3.68=>3.75:2013/04/10:io_cancel:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/04/08:io_destroy:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/04/08:io_getevents:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:io_setup:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/07/13:io_submit:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/11/08:ioctl:2:2014/06/08::tati@kc5.so-net.ne.jp:TACHIBANA Akira:
+☆:LDP man-pages:3.68=>3.75:2013/09/17:ioctl_list:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:ioperm:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/03/15:iopl:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/02/12:ioprio_get:2:ioprio_set:2:
+☆:LDP man-pages:3.68=>3.75:2013/02/12:ioprio_set:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/10/16:ipc:2:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+＠:LDP man-pages:3.75:2013/02/12:isastream:2:unimplemented:2:
+☆:LDP man-pages:3.68=>3.75:2013/12/08:kcmp:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:kexec_load:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2014/01/22:keyctl:2:::::
+☆:LDP man-pages:3.68=>3.75:2013/09/17:kill:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:killpg:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/08/19:lchown:2:chown:2:
+＠:LDP man-pages:3.75:2014/08/19:lchown32:2:lchown:2:
+＠:LDP man-pages:3.75:2014/04/06:lgetxattr:2:getxattr:2:
+☆:LDP man-pages:3.65=>3.75:2014/08/19:link:2:2014/04/24::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/08/19:linkat:2:link:2:
+☆:LDP man-pages:3.68=>3.75:2014/05/10:listen:2:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2014/02/06:listxattr:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/02/06:llistxattr:2:listxattr:2:
+☆:LDP man-pages:3.68=>3.75:2012/07/13:llseek:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2013/02/12:lock:2:unimplemented:2:
+☆:LDP man-pages:3.68=>3.75:2004/06/17:lookup_dcookie:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/02/06:lremovexattr:2:removexattr:2:
+☆:LDP man-pages:3.68=>3.75:2014/06/13:lseek:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/02/06:lsetxattr:2:setxattr:2:
+＠:LDP man-pages:3.75:2014/08/19:lstat:2:stat:2:
+＠:LDP man-pages:3.75:2014/05/10:lstat64:2:lstat:2:
+☆:LDP man-pages:3.68=>3.75:2014/04/20:madvise:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/02/12:madvise1:2:unimplemented:2:
+☆:LDP man-pages:3.68=>3.75:2014/05/10:mbind:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/08/01:migrate_pages:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2008/04/22:mincore:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:mkdir:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:mkdirat:2:mkdir:2:
+☆:LDP man-pages:3.68=>3.75:2014/02/21:mknod:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/02/21:mknodat:2:mknod:2:
+☆:LDP man-pages:3.68=>3.75:2014/04/14:mlock:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/04/14:mlockall:2:mlock:2:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:mmap:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/02/25:mmap2:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/07/13:modify_ldt:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/09/21:mount:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/06/11:move_pages:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/01/05:mprotect:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/02/12:mpx:2:unimplemented:2:
+☆:LDP man-pages:3.68=>3.75:2012/07/13:mq_getsetattr:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/04/06:mq_notify:2:mq_notify:3:
+＠:LDP man-pages:3.75:2014/10/02:mq_open:2:mq_open:3:
+＠:LDP man-pages:3.75:2014/06/03:mq_timedreceive:2:mq_receive:3:
+＠:LDP man-pages:3.75:2014/06/03:mq_timedsend:2:mq_send:3:
+＠:LDP man-pages:3.75:2014/06/13:mq_unlink:2:mq_unlink:3:
+☆:LDP man-pages:3.68=>3.75:2010/06/10:mremap:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/02/24:msgctl:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/04/30:msgget:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:msgop:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:msgrcv:2:msgop:2:
+＠:LDP man-pages:3.75:2014/08/19:msgsnd:2:msgop:2:
+☆:LDP man-pages:3.68=>3.75:2014/04/20:msync:2:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2014/04/14:munlock:2:mlock:2:
+＠:LDP man-pages:3.75:2014/04/14:munlockall:2:mlock:2:
+＠:LDP man-pages:3.75:2014/08/19:munmap:2:mmap:2:
+※:LDP man-pages:3.75:2014/06/13:name_to_handle_at:2:open_by_handle_at:2:
+☆:LDP man-pages:3.68=>3.75:2013/07/30:nanosleep:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/09/17:nfsservctl:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/04/28:nice:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:oldfstat:2:stat:2:
+＠:LDP man-pages:3.75:2014/08/19:oldlstat:2:stat:2:
+＠:LDP man-pages:3.75:2014/09/21:oldolduname:2:uname:2:
+＠:LDP man-pages:3.75:2014/08/19:oldstat:2:stat:2:
+＠:LDP man-pages:3.75:2014/09/21:olduname:2:uname:2:
+☆:LDP man-pages:3.65=>3.75:2014/10/02:open:2:2014/04/28::amotoki@gmail.com:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2014/06/13:open_by_handle_at:2:::::
+＠:LDP man-pages:3.75:2014/10/02:openat:2:open:2:
+☆:LDP man-pages:3.68=>3.75:2012/12/31:outb:2:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2012/12/31:outb_p:2:outb:2:
+＠:LDP man-pages:3.75:2012/12/31:outl:2:outb:2:
+＠:LDP man-pages:3.75:2012/12/31:outl_p:2:outb:2:
+＠:LDP man-pages:3.75:2012/12/31:outsb:2:outb:2:
+＠:LDP man-pages:3.75:2012/12/31:outsl:2:outb:2:
+＠:LDP man-pages:3.75:2012/12/31:outsw:2:outb:2:
+＠:LDP man-pages:3.75:2012/12/31:outw:2:outb:2:
+＠:LDP man-pages:3.75:2012/12/31:outw_p:2:outb:2:
+☆:LDP man-pages:3.68=>3.75:2008/10/06:pause:2:2014/06/08::suto@av.crl.sony.co.jp:SUTO, Mitsuaki:
+＠:LDP man-pages:3.75:2003/07/14:pciconfig_iobase:2:pciconfig_read:2:
+☆:LDP man-pages:3.68=>3.75:2003/07/14:pciconfig_read:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2003/07/14:pciconfig_write:2:pciconfig_read:2:
+×:LDP man-pages:3.75:2014/08/19:perf_event_open:2:::::
+×:LDP man-pages:3.75:2013/02/13:perfmonctl:2:::::
+☆:LDP man-pages:3.68=>3.75:2014/04/15:personality:2:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2013/02/12:phys:2:unimplemented:2:
+☆:LDP man-pages:3.68=>3.75:2014/07/08:pipe:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/07/08:pipe2:2:pipe:2:
+☆:LDP man-pages:3.68=>3.75:2012/07/13:pivot_root:2:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2014/09/06:poll:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/03:posix_fadvise:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/09/06:ppoll:2:poll:2:
+☆:LDP man-pages:3.40=>3.75:2014/04/14:prctl:2:2012/05/26::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:pread:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/06/21:pread64:2:pread:2:
+＠:LDP man-pages:3.75:2014/10/15:preadv:2:readv:2:
+＠:LDP man-pages:3.75:2014/10/02:prlimit:2:getrlimit:2:
+×:LDP man-pages:3.75:2014/08/19:process_vm_readv:2:::::
+※:LDP man-pages:3.75:2014/08/19:process_vm_writev:2:process_vm_readv:2:
+＠:LDP man-pages:3.75:2013/02/12:prof:2:unimplemented:2:
+＠:LDP man-pages:3.75:2014/08/19:pselect:2:select:2:
+＠:LDP man-pages:3.75:2014/08/19:pselect6:2:select:2:
+×:LDP man-pages:3.75:2014/08/19:ptrace:2:::::
+＠:LDP man-pages:3.75:2013/02/12:putmsg:2:unimplemented:2:
+＠:LDP man-pages:3.75:2013/02/12:putpmsg:2:unimplemented:2:
+＠:LDP man-pages:3.75:2013/06/21:pwrite:2:pread:2:
+＠:LDP man-pages:3.75:2013/06/21:pwrite64:2:pwrite:2:
+＠:LDP man-pages:3.75:2014/10/15:pwritev:2:readv:2:
+☆:LDP man-pages:3.65=>3.75:2014/05/10:query_module:2:2014/04/24::amotoki@gmail.com:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2010/06/16:quotactl:2:::::
+☆:LDP man-pages:3.65=>3.75:2014/05/04:read:2:2014/04/24::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/03/15:readahead:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:readdir:2:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+☆:LDP man-pages:3.68=>3.75:2014/10/15:readlink:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/10/15:readlinkat:2:readlink:2:
+☆:LDP man-pages:3.68=>3.75:2014/10/15:readv:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/09/21:reboot:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:recv:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:recvfrom:2:recv:2:
+☆:LDP man-pages:3.68=>3.75:2014/06/13:recvmmsg:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:recvmsg:2:recv:2:
+☆:LDP man-pages:3.65=>3.75:2014/05/28:remap_file_pages:2:2014/04/24::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/02/06:removexattr:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.65=>3.75:2014/08/19:rename:2:2014/04/24::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:renameat:2:rename:2:
+＠:LDP man-pages:3.75:2014/08/19:renameat2:2:rename:2:
+×:LDP man-pages:3.75:2010/02/25:request_key:2:::::
+×:LDP man-pages:3.75:2014/02/11:restart_syscall:2:::::
+☆:LDP man-pages:3.68=>3.75:2008/05/08:rmdir:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/04/27:rt_sigaction:2:sigaction:2:
+＠:LDP man-pages:3.75:2013/12/11:rt_sigpending:2:sigpending:2:
+＠:LDP man-pages:3.75:2013/04/19:rt_sigprocmask:2:sigprocmask:2:
+×:LDP man-pages:3.75:2012/07/13:rt_sigqueueinfo:2:::::
+＠:LDP man-pages:3.75:2013/07/30:rt_sigreturn:2:sigreturn:2:
+＠:LDP man-pages:3.75:2013/04/19:rt_sigsuspend:2:sigsuspend:2:
+＠:LDP man-pages:3.75:2014/08/19:rt_sigtimedwait:2:sigtimedwait:2:
+※:LDP man-pages:3.75:2012/07/13:rt_tgsigqueueinfo:2:rt_sigqueueinfo:2:
+×:LDP man-pages:3.75:2012/12/17:s390_runtime_instr:2:::::
+＠:LDP man-pages:3.75:2014/08/19:sbrk:2:brk:2:
+☆:LDP man-pages:3.68=>3.75:2014/05/12:sched_get_priority_max:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/12:sched_get_priority_min:2:sched_get_priority_max:2:
+＠:LDP man-pages:3.75:2014/08/19:sched_getaffinity:2:sched_setaffinity:2:
+※:LDP man-pages:3.75:2014/10/02:sched_getattr:2:sched_setattr:2:
+＠:LDP man-pages:3.75:2014/05/11:sched_getparam:2:sched_setparam:2:
+＠:LDP man-pages:3.75:2014/10/02:sched_getscheduler:2:sched_setscheduler:2:
+☆:LDP man-pages:3.68=>3.75:2014/04/28:sched_rr_get_interval:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:sched_setaffinity:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2014/10/02:sched_setattr:2:::::
+☆:LDP man-pages:3.68=>3.75:2014/05/11:sched_setparam:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.65=>3.75:2014/10/02:sched_setscheduler:2:2014/04/24::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/04/28:sched_yield:2:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+＠:LDP man-pages:3.75:2013/02/12:security:2:unimplemented:2:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:select:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/12/30:select_tut:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/06/03:semctl:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.65=>3.75:2014/05/21:semget:2:2014/04/24::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/09/21:semop:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/09/21:semtimedop:2:semop:2:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:send:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2011/09/14:sendfile:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2011/09/14:sendfile64:2:sendfile:2:
+☆:LDP man-pages:3.68=>3.75:2014/07/08:sendmmsg:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:sendmsg:2:send:2:
+＠:LDP man-pages:3.75:2014/08/19:sendto:2:send:2:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:set_mempolicy:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+※:LDP man-pages:3.75:2014/05/10:set_robust_list:2:get_robust_list:2:
+☆:LDP man-pages:3.68=>3.75:2012/07/13:set_thread_area:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/07/08:set_tid_address:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/04/08:setcontext:2:getcontext:3:
+＠:LDP man-pages:3.75:2012/10/25:setdomainname:2:getdomainname:2:
+＠:LDP man-pages:3.75:2014/09/21:setegid:2:seteuid:2:
+☆:LDP man-pages:3.68=>3.75:2014/09/21:seteuid:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/08/08:setfsgid:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/08/08:setfsgid32:2:setfsgid:2:
+☆:LDP man-pages:3.68=>3.75:2013/08/08:setfsuid:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/08/08:setfsuid32:2:setfsuid:2:
+☆:LDP man-pages:3.68=>3.75:2014/09/21:setgid:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/09/21:setgid32:2:setgid:2:
+＠:LDP man-pages:3.75:2014/08/19:setgroups:2:getgroups:2:
+＠:LDP man-pages:3.75:2014/08/19:setgroups32:2:setgroups:2:
+＠:LDP man-pages:3.75:2010/09/20:sethostid:2:gethostid:3:
+＠:LDP man-pages:3.75:2014/08/19:sethostname:2:gethostname:2:
+＠:LDP man-pages:3.75:2014/07/08:setitimer:2:getitimer:2:
+☆:LDP man-pages:3.68=>3.75:2014/09/21:setns:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/01/07:setpgid:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/01/07:setpgrp:2:setpgid:2:
+＠:LDP man-pages:3.75:2014/08/19:setpriority:2:getpriority:2:
+＠:LDP man-pages:3.75:2014/09/21:setregid:2:setreuid:2:
+＠:LDP man-pages:3.75:2014/09/21:setregid32:2:setregid:2:
+＠:LDP man-pages:3.75:2014/09/21:setresgid:2:setresuid:2:
+＠:LDP man-pages:3.75:2010/11/22:setresgid32:2:setresgid:2:
+☆:LDP man-pages:3.68=>3.75:2014/09/21:setresuid:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/09/21:setresuid32:2:setresuid:2:
+☆:LDP man-pages:3.68=>3.75:2014/09/21:setreuid:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/09/21:setreuid32:2:setreuid:2:
+＠:LDP man-pages:3.75:2014/10/02:setrlimit:2:getrlimit:2:
+☆:LDP man-pages:3.68=>3.75:2013/02/11:setsid:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/04/28:setsockopt:2:getsockopt:2:
+＠:LDP man-pages:3.75:2012/04/26:settimeofday:2:gettimeofday:2:
+☆:LDP man-pages:3.68=>3.75:2014/09/21:setuid:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/09/21:setuid32:2:setuid:2:
+☆:LDP man-pages:3.68=>3.75:2008/12/03:setup:2:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2014/02/06:setxattr:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/02/25:sgetmask:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/07/08:shmat:2:shmop:2:
+☆:LDP man-pages:3.68=>3.75:2014/02/07:shmctl:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/07/08:shmdt:2:shmop:2:
+☆:LDP man-pages:3.65=>3.75:2014/10/02:shmget:2:2014/04/24::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.65=>3.75:2014/07/08:shmop:2:2014/04/24::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/09/06:shutdown:2:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2014/04/27:sigaction:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/09/26:sigaltstack:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:signal:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/07/08:signalfd:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/07/08:signalfd4:2:signalfd:2:
+☆:LDP man-pages:3.68=>3.75:2013/12/11:sigpending:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/04/19:sigprocmask:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/12/16:sigqueue:2:sigqueue:3:
+☆:LDP man-pages:3.68=>3.75:2013/07/30:sigreturn:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/04/19:sigsuspend:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:sigtimedwait:2:sigwaitinfo:2:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:sigwaitinfo:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/12/31:socket:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/10/16:socketcall:2:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+☆:LDP man-pages:3.68=>3.75:2008/10/11:socketpair:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/07/08:splice:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/08/05:spu_create:2:2014/06/08::amotoki@gmail.com:Akihiro Motoki:
+☆:LDP man-pages:3.68=>3.75:2012/08/05:spu_run:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/02/25:ssetmask:2:sgetmask:2:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:stat:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:stat64:2:stat:2:
+☆:LDP man-pages:3.68=>3.75:2014/06/13:statfs:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/06/13:statfs64:2:statfs:2:
+＠:LDP man-pages:3.75:2013/09/26:statvfs:2:statvfs:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/10:stime:2:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2013/02/12:stty:2:unimplemented:2:
+×:LDP man-pages:3.75:2012/07/13:subpage_prot:2:::::
+＠:LDP man-pages:3.75:2014/05/28:swapoff:2:swapon:2:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:swapon:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.65=>3.75:2014/08/19:symlink:2:2014/04/24::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/08/19:symlinkat:2:symlink:2:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:sync:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:sync_file_range:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:sync_file_range2:2:sync_file_range:2:
+＠:LDP man-pages:3.75:2014/08/19:syncfs:2:sync:2:
+☆:LDP man-pages:3.68=>3.75:2014/05/10:syscall:2:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:syscalls:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/12/22:sysctl:2:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+☆:LDP man-pages:3.68=>3.75:2010/06/27:sysfs:2:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:sysinfo:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/07/08:syslog:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/07/08:tee:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2012/07/13:tgkill:2:tkill:2:
+☆:LDP man-pages:3.68=>3.75:2011/09/09:time:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2014/08/19:timer_create:2:::::
+☆:LDP man-pages:3.68=>3.75:2009/02/20:timer_delete:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2009/02/20:timer_getoverrun:2:::::
+※:LDP man-pages:3.75:2012/10/15:timer_gettime:2:timer_settime:2:
+×:LDP man-pages:3.75:2012/10/15:timer_settime:2:::::
+☆:LDP man-pages:3.68=>3.75:2011/09/14:timerfd_create:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2011/09/14:timerfd_gettime:2:timerfd_create:2:
+＠:LDP man-pages:3.75:2011/09/14:timerfd_settime:2:timerfd_create:2:
+☆:LDP man-pages:3.68=>3.75:2012/10/22:times:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/07/13:tkill:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/04/01:truncate:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/04/01:truncate64:2:truncate:2:
+＠:LDP man-pages:3.75:2013/02/12:tuxcall:2:unimplemented:2:
+＠:LDP man-pages:3.75:2014/10/02:ugetrlimit:2:getrlimit:2:
+☆:LDP man-pages:3.68=>3.75:2008/01/09:umask:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/02/26:umount:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/02/26:umount2:2:umount:2:
+☆:LDP man-pages:3.68=>3.75:2014/09/21:uname:2:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2013/02/12:unimplemented:2:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:unlink:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:unlinkat:2:unlink:2:
+☆:LDP man-pages:3.68=>3.75:2014/09/21:unshare:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2005/01/09:uselib:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2003/08/04:ustat:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:utime:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2014/01/24:utimensat:2:::::
+＠:LDP man-pages:3.75:2014/08/19:utimes:2:utime:2:
+☆:LDP man-pages:3.68=>3.75:2012/08/05:vfork:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2007/07/26:vhangup:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2009/02/20:vm86:2:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2009/02/20:vm86old:2:vm86:2:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:vmsplice:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/02/12:vserver:2:unimplemented:2:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:wait:2:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2012/09/23:wait3:2:wait4:2:
+☆:LDP man-pages:3.68=>3.75:2012/09/23:wait4:2:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:waitid:2:wait:2:
+＠:LDP man-pages:3.75:2014/08/19:waitpid:2:wait:2:
+☆:LDP man-pages:3.65=>3.75:2014/05/04:write:2:2014/04/24::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/10/15:writev:2:readv:2:
+＠:LDP man-pages:3.75:2007/12/28:CIRCLEQ_ENTRY:3:queue:3:
+＠:LDP man-pages:3.75:2007/12/28:CIRCLEQ_HEAD:3:queue:3:
+＠:LDP man-pages:3.75:2007/12/28:CIRCLEQ_INIT:3:queue:3:
+＠:LDP man-pages:3.75:2007/12/28:CIRCLEQ_INSERT_AFTER:3:queue:3:
+＠:LDP man-pages:3.75:2007/12/28:CIRCLEQ_INSERT_BEFORE:3:queue:3:
+＠:LDP man-pages:3.75:2007/12/28:CIRCLEQ_INSERT_HEAD:3:queue:3:
+＠:LDP man-pages:3.75:2007/12/28:CIRCLEQ_INSERT_TAIL:3:queue:3:
+＠:LDP man-pages:3.75:2007/12/28:CIRCLEQ_REMOVE:3:queue:3:
+＠:LDP man-pages:3.75:2008/11/20:CMSG_ALIGN:3:cmsg:3:
+＠:LDP man-pages:3.75:2008/11/20:CMSG_FIRSTHDR:3:cmsg:3:
+＠:LDP man-pages:3.75:2008/11/20:CMSG_NXTHDR:3:cmsg:3:
+＠:LDP man-pages:3.75:2008/11/20:CMSG_SPACE:3:cmsg:3:
+＠:LDP man-pages:3.75:2012/03/15:CPU_ALLOC:3:CPU_SET:3:
+＠:LDP man-pages:3.75:2012/03/15:CPU_ALLOC_SIZE:3:CPU_SET:3:
+＠:LDP man-pages:3.75:2012/03/15:CPU_AND:3:CPU_SET:3:
+＠:LDP man-pages:3.75:2012/03/15:CPU_AND_S:3:CPU_SET:3:
+＠:LDP man-pages:3.75:2012/03/15:CPU_CLR:3:CPU_SET:3:
+＠:LDP man-pages:3.75:2012/03/15:CPU_CLR_S:3:CPU_SET:3:
+＠:LDP man-pages:3.75:2012/03/15:CPU_COUNT:3:CPU_SET:3:
+＠:LDP man-pages:3.75:2012/03/15:CPU_COUNT_S:3:CPU_SET:3:
+＠:LDP man-pages:3.75:2012/03/15:CPU_EQUAL:3:CPU_SET:3:
+＠:LDP man-pages:3.75:2012/03/15:CPU_EQUAL_S:3:CPU_SET:3:
+＠:LDP man-pages:3.75:2012/03/15:CPU_FREE:3:CPU_SET:3:
+＠:LDP man-pages:3.75:2012/03/15:CPU_ISSET:3:CPU_SET:3:
+＠:LDP man-pages:3.75:2012/03/15:CPU_ISSET_S:3:CPU_SET:3:
+＠:LDP man-pages:3.75:2012/03/15:CPU_OR:3:CPU_SET:3:
+＠:LDP man-pages:3.75:2012/03/15:CPU_OR_S:3:CPU_SET:3:
+☆:LDP man-pages:3.68=>3.75:2012/03/15:CPU_SET:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2012/03/15:CPU_SET_S:3:CPU_SET:3:
+＠:LDP man-pages:3.75:2012/03/15:CPU_XOR:3:CPU_SET:3:
+＠:LDP man-pages:3.75:2012/03/15:CPU_XOR_S:3:CPU_SET:3:
+＠:LDP man-pages:3.75:2012/03/15:CPU_ZERO:3:CPU_SET:3:
+＠:LDP man-pages:3.75:2012/03/15:CPU_ZERO_S:3:CPU_SET:3:
+＠:LDP man-pages:3.75:2014/08/19:DES_FAILED:3:des_crypt:3:
+＠:LDP man-pages:3.75:2014/08/19:FD_CLR:3:select:2:
+＠:LDP man-pages:3.75:2014/08/19:FD_ISSET:3:select:2:
+＠:LDP man-pages:3.75:2014/08/19:FD_SET:3:select:2:
+＠:LDP man-pages:3.75:2014/08/19:FD_ZERO:3:select:2:
+＠:LDP man-pages:3.75:2007/07/26:HUGE_VAL:3:INFINITY:3:
+＠:LDP man-pages:3.75:2007/07/26:HUGE_VALF:3:INFINITY:3:
+＠:LDP man-pages:3.75:2007/07/26:HUGE_VALL:3:INFINITY:3:
+☆:LDP man-pages:3.68=>3.75:2007/07/26:INFINITY:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2007/12/28:LIST_ENTRY:3:queue:3:
+＠:LDP man-pages:3.75:2007/12/28:LIST_HEAD:3:queue:3:
+＠:LDP man-pages:3.75:2007/12/28:LIST_INIT:3:queue:3:
+＠:LDP man-pages:3.75:2007/12/28:LIST_INSERT_AFTER:3:queue:3:
+＠:LDP man-pages:3.75:2007/12/28:LIST_INSERT_HEAD:3:queue:3:
+＠:LDP man-pages:3.75:2007/12/28:LIST_REMOVE:3:queue:3:
+☆:LDP man-pages:3.68=>3.75:1999/07/04:MB_CUR_MAX:3:2014/06/08::cz8cb01@linux.or.jp:HAYAKAWA Hitoshi:
+☆:LDP man-pages:3.68=>3.75:1999/07/04:MB_LEN_MAX:3:2014/06/08::cz8cb01@linux.or.jp:HAYAKAWA Hitoshi:
+＠:LDP man-pages:3.75:2007/07/26:NAN:3:INFINITY:3:
+＠:LDP man-pages:3.75:2007/12/28:TAILQ_ENTRY:3:queue:3:
+＠:LDP man-pages:3.75:2007/12/28:TAILQ_HEAD:3:queue:3:
+＠:LDP man-pages:3.75:2007/12/28:TAILQ_INIT:3:queue:3:
+＠:LDP man-pages:3.75:2007/12/28:TAILQ_INSERT_AFTER:3:queue:3:
+＠:LDP man-pages:3.75:2007/12/28:TAILQ_INSERT_HEAD:3:queue:3:
+＠:LDP man-pages:3.75:2007/12/28:TAILQ_INSERT_TAIL:3:queue:3:
+＠:LDP man-pages:3.75:2007/12/28:TAILQ_REMOVE:3:queue:3:
+＠:LDP man-pages:3.75:2010/10/13:__after_morecore_hook:3:malloc_hook:3:
+＠:LDP man-pages:3.75:2013/06/21:__fbufsize:3:stdio_ext:3:
+＠:LDP man-pages:3.75:2013/06/21:__flbf:3:stdio_ext:3:
+＠:LDP man-pages:3.75:2013/06/21:__fpending:3:stdio_ext:3:
+＠:LDP man-pages:3.75:2001/12/15:__fpurge:3:fpurge:3:
+＠:LDP man-pages:3.75:2013/06/21:__freadable:3:stdio_ext:3:
+＠:LDP man-pages:3.75:2013/06/21:__freading:3:stdio_ext:3:
+＠:LDP man-pages:3.75:2010/10/13:__free_hook:3:malloc_hook:3:
+＠:LDP man-pages:3.75:2013/06/21:__fsetlocking:3:stdio_ext:3:
+＠:LDP man-pages:3.75:2013/06/21:__fwritable:3:stdio_ext:3:
+＠:LDP man-pages:3.75:2013/06/21:__fwriting:3:stdio_ext:3:
+＠:LDP man-pages:3.75:2010/10/13:__malloc_hook:3:malloc_hook:3:
+＠:LDP man-pages:3.75:2010/10/13:__malloc_initialize_hook:3:malloc_hook:3:
+＠:LDP man-pages:3.75:2010/10/13:__memalign_hook:3:malloc_hook:3:
+＠:LDP man-pages:3.75:2010/10/13:__realloc_hook:3:malloc_hook:3:
+☆:LDP man-pages:3.68=>3.75:2012/12/31:__setfpucw:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+＠:LDP man-pages:3.75:2013/06/21:_flushlbf:3:stdio_ext:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:a64l:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2014/03/25:abort:3:2014/06/08::tyoshino@eng.toyo.ac.jp:Takashi Yoshino:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:abs:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:acos:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/20:acosf:3:acos:3:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:acosh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/20:acoshf:3:acosh:3:
+＠:LDP man-pages:3.75:2010/09/20:acoshl:3:acosh:3:
+＠:LDP man-pages:3.75:2010/09/20:acosl:3:acos:3:
+＠:LDP man-pages:3.75:2009/09/15:addmntent:3:getmntent:3:
+☆:LDP man-pages:3.68=>3.75:2008/06/14:addseverity:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:adjtime:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/05/08:aio_cancel:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/07/04:aio_error:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/05/08:aio_fsync:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/04/26:aio_init:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/05/08:aio_read:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/07/04:aio_return:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/05/08:aio_suspend:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/05/08:aio_write:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/09/02:aligned_alloc:3:posix_memalign:3:
+☆:LDP man-pages:3.68=>3.75:2013/10/07:alloca:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/05/28:alphasort:3:scandir:3:
+＠:LDP man-pages:3.75:2014/05/28:argz:3:argz_add:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:argz_add:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/28:argz_add_sep:3:argz_add:3:
+＠:LDP man-pages:3.75:2014/05/28:argz_append:3:argz_add:3:
+＠:LDP man-pages:3.75:2014/05/28:argz_count:3:argz_add:3:
+＠:LDP man-pages:3.75:2014/05/28:argz_create:3:argz_add:3:
+＠:LDP man-pages:3.75:2014/05/28:argz_create_sep:3:argz_add:3:
+＠:LDP man-pages:3.75:2014/05/28:argz_delete:3:argz_add:3:
+＠:LDP man-pages:3.75:2014/05/28:argz_extract:3:argz_add:3:
+＠:LDP man-pages:3.75:2014/05/28:argz_insert:3:argz_add:3:
+＠:LDP man-pages:3.75:2014/05/28:argz_next:3:argz_add:3:
+＠:LDP man-pages:3.75:2014/05/28:argz_replace:3:argz_add:3:
+＠:LDP man-pages:3.75:2014/05/28:argz_stringify:3:argz_add:3:
+＠:LDP man-pages:3.75:2014/08/19:asctime:3:ctime:3:
+＠:LDP man-pages:3.75:2014/08/19:asctime_r:3:ctime:3:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:asin:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/20:asinf:3:asin:3:
+☆:LDP man-pages:3.68=>3.75:2013/10/14:asinh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/10/14:asinhf:3:asinh:3:
+＠:LDP man-pages:3.75:2013/10/14:asinhl:3:asinh:3:
+＠:LDP man-pages:3.75:2010/09/20:asinl:3:asin:3:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:asprintf:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2013/09/26:assert:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2013/09/26:assert_perror:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/10/07:atan:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:atan2:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/20:atan2f:3:atan2:3:
+＠:LDP man-pages:3.75:2010/09/20:atan2l:3:atan2:3:
+＠:LDP man-pages:3.75:2013/10/07:atanf:3:atan:3:
+☆:LDP man-pages:3.68=>3.75:2010/09/11:atanh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/11:atanhf:3:atanh:3:
+＠:LDP man-pages:3.75:2010/09/11:atanhl:3:atanh:3:
+＠:LDP man-pages:3.75:2013/10/07:atanl:3:atan:3:
+☆:LDP man-pages:3.68=>3.75:2008/12/05:atexit:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/01/22:atof:3:2014/06/08::tyoshino@eng.toyo.ac.jp:Takashi Yoshino:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:atoi:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2014/08/19:atol:3:atoi:3:
+＠:LDP man-pages:3.75:2014/08/19:atoll:3:atoi:3:
+＠:LDP man-pages:3.75:2014/08/19:atoq:3:atoi:3:
+＠:LDP man-pages:3.75:2013/09/26:auth_destroy:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:authnone_create:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:authunix_create:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:authunix_create_default:3:rpc:3:
+☆:LDP man-pages:3.68=>3.75:2008/06/14:backtrace:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/06/14:backtrace_symbols:3:backtrace:3:
+＠:LDP man-pages:3.75:2008/06/14:backtrace_symbols_fd:3:backtrace:3:
+☆:LDP man-pages:3.68=>3.75:2014/06/13:basename:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/10/21:bcmp:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2013/10/22:bcopy:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2010/09/10:be16toh:3:endian:3:
+＠:LDP man-pages:3.75:2010/09/10:be32toh:3:endian:3:
+＠:LDP man-pages:3.75:2010/09/10:be64toh:3:endian:3:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:bindresvport:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/10/22:bsd_signal:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2003/11/01:bsearch:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:bstring:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2011/09/22:btowc:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/04/23:btree:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/04/08:byteorder:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/10/22:bzero:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2008/08/11:cabs:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/08/11:cabsf:3:cabs:3:
+＠:LDP man-pages:3.75:2008/08/11:cabsl:3:cabs:3:
+☆:LDP man-pages:3.68=>3.75:2011/09/15:cacos:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2011/09/15:cacosf:3:cacos:3:
+☆:LDP man-pages:3.68=>3.75:2011/09/15:cacosh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2011/09/15:cacoshf:3:cacosh:3:
+＠:LDP man-pages:3.75:2011/09/15:cacoshl:3:cacosh:3:
+＠:LDP man-pages:3.75:2011/09/15:cacosl:3:cacos:3:
+＠:LDP man-pages:3.75:2014/05/21:calloc:3:malloc:3:
+＠:LDP man-pages:3.75:2013/09/26:callrpc:3:rpc:3:
+☆:LDP man-pages:3.68=>3.75:2013/05/11:canonicalize_file_name:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2008/08/11:carg:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/08/11:cargf:3:carg:3:
+＠:LDP man-pages:3.75:2008/08/11:cargl:3:carg:3:
+☆:LDP man-pages:3.68=>3.75:2008/08/11:casin:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/08/11:casinf:3:casin:3:
+☆:LDP man-pages:3.68=>3.75:2008/08/11:casinh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/08/11:casinhf:3:casinh:3:
+＠:LDP man-pages:3.75:2008/08/11:casinhl:3:casinh:3:
+＠:LDP man-pages:3.75:2008/08/11:casinl:3:casin:3:
+☆:LDP man-pages:3.68=>3.75:2011/09/15:catan:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2011/09/15:catanf:3:catan:3:
+☆:LDP man-pages:3.68=>3.75:2011/09/15:catanh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2011/09/15:catanhf:3:catanh:3:
+＠:LDP man-pages:3.75:2011/09/15:catanhl:3:catanh:3:
+＠:LDP man-pages:3.75:2011/09/15:catanl:3:catan:3:
+＠:LDP man-pages:3.75:2014/08/19:catclose:3:catopen:3:
+☆:LDP man-pages:3.68=>3.75:2014/06/13:catgets:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:catopen:3:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/08/19:cbc_crypt:3:des_crypt:3:
+☆:LDP man-pages:3.68=>3.75:2013/09/18:cbrt:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/09/18:cbrtf:3:cbrt:3:
+＠:LDP man-pages:3.75:2013/09/18:cbrtl:3:cbrt:3:
+☆:LDP man-pages:3.68=>3.75:2008/08/11:ccos:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/08/11:ccosf:3:ccos:3:
+☆:LDP man-pages:3.68=>3.75:2008/08/11:ccosh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/08/11:ccoshf:3:ccosh:3:
+＠:LDP man-pages:3.75:2008/08/11:ccoshl:3:ccosh:3:
+＠:LDP man-pages:3.75:2008/08/11:ccosl:3:ccos:3:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:ceil:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/06/21:ceilf:3:ceil:3:
+＠:LDP man-pages:3.75:2013/06/21:ceill:3:ceil:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:cerf:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:cerfc:3:cerf:3:
+＠:LDP man-pages:3.75:2014/08/19:cerfcf:3:cerf:3:
+＠:LDP man-pages:3.75:2014/08/19:cerfcl:3:cerf:3:
+＠:LDP man-pages:3.75:2014/08/19:cerff:3:cerf:3:
+＠:LDP man-pages:3.75:2014/08/19:cerfl:3:cerf:3:
+☆:LDP man-pages:3.68=>3.75:2008/08/11:cexp:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:cexp2:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:cexp2f:3:cexp2:3:
+＠:LDP man-pages:3.75:2014/08/19:cexp2l:3:cexp2:3:
+＠:LDP man-pages:3.75:2008/08/11:cexpf:3:cexp:3:
+＠:LDP man-pages:3.75:2008/08/11:cexpl:3:cexp:3:
+＠:LDP man-pages:3.75:2014/05/08:cfgetispeed:3:termios:3:
+＠:LDP man-pages:3.75:2014/05/08:cfgetospeed:3:termios:3:
+＠:LDP man-pages:3.75:2014/05/08:cfmakeraw:3:termios:3:
+☆:LDP man-pages:3.68=>3.75:2007/07/26:cfree:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/05/08:cfsetispeed:3:termios:3:
+＠:LDP man-pages:3.75:2014/05/08:cfsetospeed:3:termios:3:
+＠:LDP man-pages:3.75:2014/05/08:cfsetspeed:3:termios:3:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:cimag:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/06/21:cimagf:3:cimag:3:
+＠:LDP man-pages:3.75:2013/06/21:cimagl:3:cimag:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:clearenv:3:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/01/15:clearerr:3:ferror:3:
+＠:LDP man-pages:3.75:2008/08/29:clearerr_unlocked:3:unlocked_stdio:3:
+＠:LDP man-pages:3.75:2013/09/26:clnt_broadcast:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:clnt_call:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:clnt_control:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:clnt_create:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:clnt_destroy:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:clnt_freeres:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:clnt_geterr:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:clnt_pcreateerror:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:clnt_perrno:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:clnt_perror:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:clnt_spcreateerror:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:clnt_sperrno:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:clnt_sperror:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:clntraw_create:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:clnttcp_create:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:clntudp_bufcreate:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:clntudp_create:3:rpc:3:
+☆:LDP man-pages:3.68=>3.75:2014/09/21:clock:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/07/04:clock_getcpuclockid:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/12/28:clock_getres:3:clock_getres:2:
+＠:LDP man-pages:3.75:2013/12/28:clock_gettime:3:clock_getres:2:
+＠:LDP man-pages:3.75:2013/12/28:clock_settime:3:clock_getres:2:
+☆:LDP man-pages:3.68=>3.75:2008/08/11:clog:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2008/08/11:clog10:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/08/11:clog10f:3:clog10:3:
+＠:LDP man-pages:3.75:2008/08/11:clog10l:3:clog10:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:clog2:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:clog2f:3:clog2:3:
+＠:LDP man-pages:3.75:2014/08/19:clog2l:3:clog2:3:
+＠:LDP man-pages:3.75:2008/08/11:clogf:3:clog:3:
+＠:LDP man-pages:3.75:2008/08/11:clogl:3:clog:3:
+☆:LDP man-pages:3.68=>3.75:2008/09/23:closedir:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2012/08/17:closelog:3:syslog:3:
+☆:LDP man-pages:3.68=>3.75:2008/11/20:cmsg:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2014/03/20:confstr:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:conj:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/06/21:conjf:3:conj:3:
+＠:LDP man-pages:3.75:2013/06/21:conjl:3:conj:3:
+☆:LDP man-pages:3.68=>3.75:2013/10/14:copysign:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/10/14:copysignf:3:copysign:3:
+＠:LDP man-pages:3.75:2013/10/14:copysignl:3:copysign:3:
+☆:LDP man-pages:3.68=>3.75:2013/10/14:cos:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/10/14:cosf:3:cos:3:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:cosh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/20:coshf:3:cosh:3:
+＠:LDP man-pages:3.75:2010/09/20:coshl:3:cosh:3:
+＠:LDP man-pages:3.75:2013/10/14:cosl:3:cos:3:
+☆:LDP man-pages:3.68=>3.75:2008/08/11:cpow:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/08/11:cpowf:3:cpow:3:
+＠:LDP man-pages:3.75:2008/08/11:cpowl:3:cpow:3:
+☆:LDP man-pages:3.68=>3.75:2013/09/18:cproj:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/09/18:cprojf:3:cproj:3:
+＠:LDP man-pages:3.75:2013/09/18:cprojl:3:cproj:3:
+☆:LDP man-pages:3.68=>3.75:2013/09/18:creal:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/09/18:crealf:3:creal:3:
+＠:LDP man-pages:3.75:2013/09/18:creall:3:creal:3:
+☆:LDP man-pages:3.68=>3.75:2014/02/26:crypt:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2014/02/26:crypt_r:3:crypt:3:
+☆:LDP man-pages:3.68=>3.75:2008/08/11:csin:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/08/11:csinf:3:csin:3:
+☆:LDP man-pages:3.68=>3.75:2008/08/11:csinh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/08/11:csinhf:3:csinh:3:
+＠:LDP man-pages:3.75:2008/08/11:csinhl:3:csinh:3:
+＠:LDP man-pages:3.75:2008/08/11:csinl:3:csin:3:
+☆:LDP man-pages:3.68=>3.75:2008/08/11:csqrt:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/08/11:csqrtf:3:csqrt:3:
+＠:LDP man-pages:3.75:2008/08/11:csqrtl:3:csqrt:3:
+☆:LDP man-pages:3.68=>3.75:2008/08/11:ctan:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/08/11:ctanf:3:ctan:3:
+☆:LDP man-pages:3.68=>3.75:2008/08/11:ctanh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/08/11:ctanhf:3:ctanh:3:
+＠:LDP man-pages:3.75:2008/08/11:ctanhl:3:ctanh:3:
+＠:LDP man-pages:3.75:2008/08/11:ctanl:3:ctan:3:
+☆:LDP man-pages:3.68=>3.75:2013/07/04:ctermid:3:2014/06/08::nagoya@cc.hit-u.ac.jp:NAGOYA Hiroaki:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:ctime:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:ctime_r:3:ctime:3:
+＠:LDP man-pages:3.75:2013/04/19:cuserid:3:getlogin:3:
+☆:LDP man-pages:3.68=>3.75:2013/10/28:daemon:3:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/08/19:daylight:3:tzset:3:
+＠:LDP man-pages:3.75:2012/05/04:db:3:dbopen:3:
+☆:LDP man-pages:3.68=>3.75:2012/05/04:dbopen:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:des_crypt:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/08/19:des_setparity:3:des_crypt:3:
+☆:LDP man-pages:3.68=>3.75:2013/10/28:difftime:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/07/05:dirfd:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/06/13:dirname:3:basename:3:
+☆:LDP man-pages:3.68=>3.75:2013/07/05:div:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2007/05/18:dl_iterate_phdr:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/10/02:dladdr:3:dlopen:3:
+＠:LDP man-pages:3.75:2014/10/02:dlclose:3:dlopen:3:
+＠:LDP man-pages:3.75:2014/10/02:dlerror:3:dlopen:3:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:dlopen:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/10/02:dlsym:3:dlopen:3:
+＠:LDP man-pages:3.75:2014/10/02:dlvsym:3:dlopen:3:
+＠:LDP man-pages:3.75:2014/05/28:dn_comp:3:resolver:3:
+＠:LDP man-pages:3.75:2014/05/28:dn_expand:3:resolver:3:
+☆:LDP man-pages:3.68=>3.75:2010/09/15:dprintf:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2014/09/21:drand48:3:2014/06/08::tyoshino@eng.toyo.ac.jp:YOSHINO Takashi:
+☆:LDP man-pages:3.68=>3.75:2013/09/09:drand48_r:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2010/09/20:drem:3:remainder:3:
+＠:LDP man-pages:3.75:2010/09/20:dremf:3:remainder:3:
+＠:LDP man-pages:3.75:2010/09/20:dreml:3:remainder:3:
+☆:LDP man-pages:3.68=>3.75:2014/03/12:duplocale:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/09/25:dysize:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+＠:LDP man-pages:3.75:2013/09/25:eaccess:3:euidaccess:3:
+＠:LDP man-pages:3.75:2014/08/19:ecb_crypt:3:des_crypt:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:ecvt:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2007/07/26:ecvt_r:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/07/17:edata:3:end:3:
+☆:LDP man-pages:3.68=>3.75:2013/07/22:encrypt:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2013/07/22:encrypt_r:3:encrypt:3:
+☆:LDP man-pages:3.68=>3.75:2008/07/17:end:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2003/09/09:endaliasent:3:setaliasent:3:
+＠:LDP man-pages:3.75:2002/02/28:endfsent:3:getfsent:3:
+＠:LDP man-pages:3.75:2014/10/02:endgrent:3:getgrent:3:
+＠:LDP man-pages:3.75:2014/03/11:endhostent:3:gethostbyname:3:
+☆:LDP man-pages:3.68=>3.75:2010/09/10:endian:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2009/09/15:endmntent:3:getmntent:3:
+＠:LDP man-pages:3.75:2008/08/19:endnetent:3:getnetent:3:
+＠:LDP man-pages:3.75:2014/05/28:endnetgrent:3:setnetgrent:3:
+＠:LDP man-pages:3.75:2008/08/19:endprotoent:3:getprotoent:3:
+＠:LDP man-pages:3.75:2013/06/21:endpwent:3:getpwent:3:
+＠:LDP man-pages:3.75:2014/05/28:endrpcent:3:getrpcent:3:
+＠:LDP man-pages:3.75:2008/08/19:endservent:3:getservent:3:
+＠:LDP man-pages:3.75:2014/05/28:endspent:3:getspnam:3:
+＠:LDP man-pages:3.75:2013/07/22:endttyent:3:getttyent:3:
+＠:LDP man-pages:3.75:2013/06/21:endusershell:3:getusershell:3:
+＠:LDP man-pages:3.75:2014/08/19:endutent:3:getutent:3:
+＠:LDP man-pages:3.75:2014/08/19:endutxent:3:getutent:3:
+＠:LDP man-pages:3.75:2014/05/28:envz:3:envz_add:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:envz_add:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/28:envz_entry:3:envz_add:3:
+＠:LDP man-pages:3.75:2014/05/28:envz_get:3:envz_add:3:
+＠:LDP man-pages:3.75:2014/05/28:envz_merge:3:envz_add:3:
+＠:LDP man-pages:3.75:2014/05/28:envz_remove:3:envz_add:3:
+＠:LDP man-pages:3.75:2014/05/28:envz_strip:3:envz_add:3:
+＠:LDP man-pages:3.75:2014/09/21:erand48:3:drand48:3:
+＠:LDP man-pages:3.75:2013/09/09:erand48_r:3:drand48_r:3:
+☆:LDP man-pages:3.68=>3.75:2013/10/29:erf:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/10/29:erfc:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/10/29:erfcf:3:erfc:3:
+＠:LDP man-pages:3.75:2013/10/29:erfcl:3:erfc:3:
+＠:LDP man-pages:3.75:2013/10/29:erff:3:erf:3:
+＠:LDP man-pages:3.75:2013/10/29:erfl:3:erf:3:
+☆:LDP man-pages:3.68=>3.75:2013/12/30:err:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/09/06:errno:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/08/29:error:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/08/29:error_at_line:3:error:3:
+＠:LDP man-pages:3.75:2010/08/29:error_message_count:3:error:3:
+＠:LDP man-pages:3.75:2010/08/29:error_one_per_line:3:error:3:
+＠:LDP man-pages:3.75:2010/08/29:error_print_progname:3:error:3:
+＠:LDP man-pages:3.75:2013/12/30:errx:3:err:3:
+＠:LDP man-pages:3.75:2008/07/17:etext:3:end:3:
+☆:LDP man-pages:3.68=>3.75:2014/07/08:ether_aton:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/07/08:ether_aton_r:3:ether_aton:3:
+＠:LDP man-pages:3.75:2014/07/08:ether_hostton:3:ether_aton:3:
+＠:LDP man-pages:3.75:2014/07/08:ether_line:3:ether_aton:3:
+＠:LDP man-pages:3.75:2014/07/08:ether_ntoa:3:ether_aton:3:
+＠:LDP man-pages:3.75:2014/07/08:ether_ntoa_r:3:ether_aton:3:
+＠:LDP man-pages:3.75:2014/07/08:ether_ntohost:3:ether_aton:3:
+☆:LDP man-pages:3.68=>3.75:2013/09/25:euidaccess:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/07/08:eventfd_read:3:eventfd:2:
+＠:LDP man-pages:3.75:2014/07/08:eventfd_write:3:eventfd:2:
+☆:LDP man-pages:3.68=>3.75:2010/09/25:exec:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/25:execl:3:exec:3:
+＠:LDP man-pages:3.75:2010/09/25:execle:3:exec:3:
+＠:LDP man-pages:3.75:2010/09/25:execlp:3:exec:3:
+＠:LDP man-pages:3.75:2010/09/25:execv:3:exec:3:
+＠:LDP man-pages:3.75:2010/09/25:execvp:3:exec:3:
+＠:LDP man-pages:3.75:2010/09/25:execvpe:3:exec:3:
+☆:LDP man-pages:3.68=>3.75:2014/03/25:exit:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:exp:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2008/08/11:exp10:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/08/11:exp10f:3:exp10:3:
+＠:LDP man-pages:3.75:2008/08/11:exp10l:3:exp10:3:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:exp2:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/20:exp2f:3:exp2:3:
+＠:LDP man-pages:3.75:2010/09/20:exp2l:3:exp2:3:
+＠:LDP man-pages:3.75:2010/09/20:expf:3:exp:3:
+＠:LDP man-pages:3.75:2010/09/20:expl:3:exp:3:
+☆:LDP man-pages:3.68=>3.75:2013/10/14:expm1:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/10/14:expm1f:3:expm1:3:
+＠:LDP man-pages:3.75:2013/10/14:expm1l:3:expm1:3:
+☆:LDP man-pages:3.68=>3.75:2013/07/10:fabs:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/07/10:fabsf:3:fabs:3:
+＠:LDP man-pages:3.75:2013/07/10:fabsl:3:fabs:3:
+☆:LDP man-pages:3.68=>3.75:2009/02/23:fclose:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:fcloseall:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:fcvt:3:ecvt:3:
+＠:LDP man-pages:3.75:2007/07/26:fcvt_r:3:ecvt_r:3:
+☆:LDP man-pages:3.68=>3.75:2013/07/15:fdim:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/07/15:fdimf:3:fdim:3:
+＠:LDP man-pages:3.75:2013/07/15:fdiml:3:fdim:3:
+＠:LDP man-pages:3.75:2012/04/22:fdopen:3:fopen:3:
+＠:LDP man-pages:3.75:2010/06/20:fdopendir:3:opendir:3:
+＠:LDP man-pages:3.75:2014/04/01:feclearexcept:3:fenv:3:
+＠:LDP man-pages:3.75:2014/04/01:fedisableexcept:3:fenv:3:
+＠:LDP man-pages:3.75:2014/04/01:feenableexcept:3:fenv:3:
+＠:LDP man-pages:3.75:2014/04/01:fegetenv:3:fenv:3:
+＠:LDP man-pages:3.75:2014/04/01:fegetexcept:3:fenv:3:
+＠:LDP man-pages:3.75:2014/04/01:fegetexceptflag:3:fenv:3:
+＠:LDP man-pages:3.75:2014/04/01:fegetround:3:fenv:3:
+＠:LDP man-pages:3.75:2014/04/01:feholdexcept:3:fenv:3:
+☆:LDP man-pages:3.68=>3.75:2014/04/01:fenv:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/01/15:feof:3:ferror:3:
+＠:LDP man-pages:3.75:2008/08/29:feof_unlocked:3:unlocked_stdio:3:
+＠:LDP man-pages:3.75:2014/04/01:feraiseexcept:3:fenv:3:
+☆:LDP man-pages:3.68=>3.75:2014/01/15:ferror:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2008/08/29:ferror_unlocked:3:unlocked_stdio:3:
+＠:LDP man-pages:3.75:2014/04/01:fesetenv:3:fenv:3:
+＠:LDP man-pages:3.75:2014/04/01:fesetexceptflag:3:fenv:3:
+＠:LDP man-pages:3.75:2014/04/01:fesetround:3:fenv:3:
+＠:LDP man-pages:3.75:2014/04/01:fetestexcept:3:fenv:3:
+＠:LDP man-pages:3.75:2014/04/01:feupdateenv:3:fenv:3:
+☆:LDP man-pages:3.68=>3.75:2014/04/20:fexecve:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/07/15:fflush:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2008/08/29:fflush_unlocked:3:unlocked_stdio:3:
+☆:LDP man-pages:3.68=>3.75:2014/04/14:ffs:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2014/04/14:ffsl:3:ffs:3:
+＠:LDP man-pages:3.75:2014/04/14:ffsll:3:ffs:3:
+☆:LDP man-pages:3.68=>3.75:2013/12/31:fgetc:3:2014/06/08::amotoki@gmail.com:Akihiro Motoki:
+＠:LDP man-pages:3.75:2008/08/29:fgetc_unlocked:3:unlocked_stdio:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:fgetgrent:3:2014/06/08::nishi@rpts.cl.nec.co.jp:HIROFUMI Nishizuka:
+＠:LDP man-pages:3.75:2014/08/19:fgetgrent_r:3:getgrent_r:3:
+＠:LDP man-pages:3.75:2014/05/28:fgetpos:3:fseek:3:
+☆:LDP man-pages:3.68=>3.75:2013/04/19:fgetpwent:3:2014/06/08::nishi@rpts.cl.nec.co.jp:HIROFUMI Nishizuka:
+＠:LDP man-pages:3.75:2010/10/21:fgetpwent_r:3:getpwent_r:3:
+＠:LDP man-pages:3.75:2013/12/31:fgets:3:fgetc:3:
+＠:LDP man-pages:3.75:2008/08/29:fgets_unlocked:3:unlocked_stdio:3:
+＠:LDP man-pages:3.75:2014/05/28:fgetspent:3:getspnam:3:
+＠:LDP man-pages:3.75:2014/05/28:fgetspent_r:3:getspnam:3:
+☆:LDP man-pages:3.68=>3.75:2013/04/19:fgetwc:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2008/08/29:fgetwc_unlocked:3:unlocked_stdio:3:
+☆:LDP man-pages:3.68=>3.75:2011/09/28:fgetws:3:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2008/08/29:fgetws_unlocked:3:unlocked_stdio:3:
+＠:LDP man-pages:3.75:2014/01/15:fileno:3:ferror:3:
+＠:LDP man-pages:3.75:2008/08/29:fileno_unlocked:3:unlocked_stdio:3:
+☆:LDP man-pages:3.68=>3.75:2013/07/22:finite:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/07/22:finitef:3:finite:3:
+＠:LDP man-pages:3.75:2013/07/22:finitel:3:finite:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:flockfile:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/07/23:floor:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/07/23:floorf:3:floor:3:
+＠:LDP man-pages:3.75:2013/07/23:floorl:3:floor:3:
+☆:LDP man-pages:3.68=>3.75:2013/09/17:fma:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/09/17:fmaf:3:fma:3:
+＠:LDP man-pages:3.75:2013/09/17:fmal:3:fma:3:
+☆:LDP man-pages:3.68=>3.75:2013/09/17:fmax:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/09/17:fmaxf:3:fmax:3:
+＠:LDP man-pages:3.75:2013/09/17:fmaxl:3:fmax:3:
+☆:LDP man-pages:3.68=>3.75:2014/04/06:fmemopen:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/09/17:fmin:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/09/17:fminf:3:fmin:3:
+＠:LDP man-pages:3.75:2013/09/17:fminl:3:fmin:3:
+☆:LDP man-pages:3.68=>3.75:2012/03/15:fmod:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2012/03/15:fmodf:3:fmod:3:
+＠:LDP man-pages:3.75:2012/03/15:fmodl:3:fmod:3:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:fmtmsg:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2000/10/15:fnmatch:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/04/22:fopen:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2013/03/17:fopencookie:3:::::
+＠:LDP man-pages:3.75:2014/08/19:forkpty:3:openpty:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:fpathconf:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2013/08/06:fpclassify:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/07/08:fprintf:3:printf:3:
+☆:LDP man-pages:3.68=>3.75:2001/12/15:fpurge:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+＠:LDP man-pages:3.75:2014/01/11:fputc:3:puts:3:
+＠:LDP man-pages:3.75:2008/08/29:fputc_unlocked:3:unlocked_stdio:3:
+＠:LDP man-pages:3.75:2014/01/11:fputs:3:puts:3:
+＠:LDP man-pages:3.75:2008/08/29:fputs_unlocked:3:unlocked_stdio:3:
+☆:LDP man-pages:3.68=>3.75:2013/04/19:fputwc:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2008/08/29:fputwc_unlocked:3:unlocked_stdio:3:
+☆:LDP man-pages:3.68=>3.75:2011/09/28:fputws:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2008/08/29:fputws_unlocked:3:unlocked_stdio:3:
+☆:LDP man-pages:3.68=>3.75:2012/03/30:fread:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/08/29:fread_unlocked:3:unlocked_stdio:3:
+＠:LDP man-pages:3.75:2014/05/21:free:3:malloc:3:
+＠:LDP man-pages:3.75:2014/04/06:freeaddrinfo:3:getaddrinfo:3:
+＠:LDP man-pages:3.75:2010/09/04:freehostent:3:getipnodebyname:3:
+＠:LDP man-pages:3.75:2014/02/26:freeifaddrs:3:getifaddrs:3:
+※:LDP man-pages:3.75:2014/05/28:freelocale:3:newlocale:3:
+＠:LDP man-pages:3.75:2012/04/22:freopen:3:fopen:3:
+☆:LDP man-pages:3.68=>3.75:2013/08/06:frexp:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/08/06:frexpf:3:frexp:3:
+＠:LDP man-pages:3.75:2013/08/06:frexpl:3:frexp:3:
+＠:LDP man-pages:3.75:2014/01/11:fscanf:3:scanf:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:fseek:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:fseeko:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/28:fsetpos:3:fseek:3:
+＠:LDP man-pages:3.75:2013/09/26:fstatvfs:3:statvfs:3:
+＠:LDP man-pages:3.75:2014/05/28:ftell:3:fseek:3:
+＠:LDP man-pages:3.75:2014/10/02:ftello:3:fseeko:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:ftime:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:ftok:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+＠:LDP man-pages:3.75:2014/08/19:ftrylockfile:3:flockfile:3:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:fts:3:2014/06/08::sato@complex.eng.hokudai.ac.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/03/18:fts_children:3:fts:3:
+＠:LDP man-pages:3.75:2014/03/18:fts_close:3:fts:3:
+＠:LDP man-pages:3.75:2014/03/18:fts_open:3:fts:3:
+＠:LDP man-pages:3.75:2014/03/18:fts_read:3:fts:3:
+＠:LDP man-pages:3.75:2014/03/18:fts_set:3:fts:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:ftw:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:funlockfile:3:flockfile:3:
+※:LDP man-pages:3.75:2014/01/24:futimens:3:utimensat:2:
+☆:LDP man-pages:3.68=>3.75:2013/10/29:futimes:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/03/19:fwide:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+＠:LDP man-pages:3.75:2014/03/19:fwprintf:3:wprintf:3:
+＠:LDP man-pages:3.75:2012/03/30:fwrite:3:fread:3:
+＠:LDP man-pages:3.75:2008/08/29:fwrite_unlocked:3:unlocked_stdio:3:
+※:LDP man-pages:3.75:2014/05/28:gai_cancel:3:getaddrinfo_a:3:
+※:LDP man-pages:3.75:2014/05/28:gai_error:3:getaddrinfo_a:3:
+＠:LDP man-pages:3.75:2014/04/06:gai_strerror:3:getaddrinfo:3:
+※:LDP man-pages:3.75:2014/05/28:gai_suspend:3:getaddrinfo_a:3:
+☆:LDP man-pages:3.68=>3.75:2008/08/05:gamma:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/08/05:gammaf:3:gamma:3:
+＠:LDP man-pages:3.75:2008/08/05:gammal:3:gamma:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:gcvt:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:get_current_dir_name:3:getcwd:3:
+＠:LDP man-pages:3.75:2013/09/26:get_myaddress:3:rpc:3:
+＠:LDP man-pages:3.75:2012/03/20:get_nprocs:3:get_nprocs_conf:3:
+☆:LDP man-pages:3.68=>3.75:2012/03/20:get_nprocs_conf:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/04/06:getaddrinfo:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2014/05/28:getaddrinfo_a:3:::::
+＠:LDP man-pages:3.75:2003/09/09:getaliasbyname:3:setaliasent:3:
+＠:LDP man-pages:3.75:2003/09/09:getaliasbyname_r:3:setaliasent:3:
+＠:LDP man-pages:3.75:2003/09/09:getaliasent:3:setaliasent:3:
+＠:LDP man-pages:3.75:2003/09/09:getaliasent_r:3:setaliasent:3:
+×:LDP man-pages:3.75:2014/08/19:getauxval:3:::::
+＠:LDP man-pages:3.75:2013/12/31:getc:3:fgetc:3:
+＠:LDP man-pages:3.75:2008/08/29:getc_unlocked:3:unlocked_stdio:3:
+＠:LDP man-pages:3.75:2013/12/31:getchar:3:fgetc:3:
+＠:LDP man-pages:3.75:2008/08/29:getchar_unlocked:3:unlocked_stdio:3:
+☆:LDP man-pages:3.68=>3.75:2014/04/08:getcontext:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:getcwd:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2014/06/13:getdate:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/06/13:getdate_err:3:getdate:3:
+＠:LDP man-pages:3.75:2014/06/13:getdate_r:3:getdate:3:
+＠:LDP man-pages:3.75:2014/08/19:getdelim:3:getline:3:
+☆:LDP man-pages:3.68=>3.75:2014/06/13:getdirentries:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:getdtablesize:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/08/14:getenv:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2002/02/28:getfsent:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+＠:LDP man-pages:3.75:2002/02/28:getfsfile:3:getfsent:3:
+＠:LDP man-pages:3.75:2002/02/28:getfsspec:3:getfsent:3:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:getgrent:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:getgrent_r:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/08/19:getgrgid:3:getgrnam:3:
+＠:LDP man-pages:3.75:2014/08/19:getgrgid_r:3:getgrnam:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:getgrnam:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:getgrnam_r:3:getgrnam:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:getgrouplist:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/03/11:gethostbyaddr:3:gethostbyname:3:
+＠:LDP man-pages:3.75:2014/03/11:gethostbyaddr_r:3:gethostbyname:3:
+☆:LDP man-pages:3.68=>3.75:2014/03/11:gethostbyname:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/03/11:gethostbyname2:3:gethostbyname:3:
+＠:LDP man-pages:3.75:2014/03/11:gethostbyname2_r:3:gethostbyname:3:
+＠:LDP man-pages:3.75:2014/03/11:gethostbyname_r:3:gethostbyname:3:
+＠:LDP man-pages:3.75:2014/03/11:gethostent:3:gethostbyname:3:
+＠:LDP man-pages:3.75:2014/03/11:gethostent_r:3:gethostbyname:3:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:gethostid:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/02/26:getifaddrs:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/04:getipnodebyaddr:3:getipnodebyname:3:
+☆:LDP man-pages:3.68=>3.75:2010/09/04:getipnodebyname:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:getline:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/04/01:getloadavg:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2013/04/19:getlogin:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/04/19:getlogin_r:3:getlogin:3:
+☆:LDP man-pages:3.68=>3.75:2009/09/15:getmntent:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2009/09/15:getmntent_r:3:getmntent:3:
+☆:LDP man-pages:3.67=>3.75:2014/05/28:getnameinfo:3:2014/06/04::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/08/19:getnetbyaddr:3:getnetent:3:
+＠:LDP man-pages:3.75:2010/09/10:getnetbyaddr_r:3:getnetent_r:3:
+＠:LDP man-pages:3.75:2008/08/19:getnetbyname:3:getnetent:3:
+＠:LDP man-pages:3.75:2010/09/10:getnetbyname_r:3:getnetent_r:3:
+☆:LDP man-pages:3.68=>3.75:2008/08/19:getnetent:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/09/10:getnetent_r:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/28:getnetgrent:3:setnetgrent:3:
+＠:LDP man-pages:3.75:2014/05/28:getnetgrent_r:3:setnetgrent:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/09:getopt:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/09:getopt_long:3:getopt:3:
+＠:LDP man-pages:3.75:2014/05/09:getopt_long_only:3:getopt:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:getpass:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+＠:LDP man-pages:3.75:2008/08/19:getprotobyname:3:getprotoent:3:
+＠:LDP man-pages:3.75:2010/09/10:getprotobyname_r:3:getprotoent_r:3:
+＠:LDP man-pages:3.75:2008/08/19:getprotobynumber:3:getprotoent:3:
+＠:LDP man-pages:3.75:2010/09/10:getprotobynumber_r:3:getprotoent_r:3:
+☆:LDP man-pages:3.68=>3.75:2008/08/19:getprotoent:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/09/10:getprotoent_r:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/04/01:getpt:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/10/21:getpw:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:getpwent:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/10/21:getpwent_r:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/07/22:getpwnam:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/07/22:getpwnam_r:3:getpwnam:3:
+＠:LDP man-pages:3.75:2013/07/22:getpwuid:3:getpwnam:3:
+＠:LDP man-pages:3.75:2013/07/22:getpwuid_r:3:getpwnam:3:
+＠:LDP man-pages:3.75:2014/05/28:getrpcbyname:3:getrpcent:3:
+＠:LDP man-pages:3.75:2010/09/10:getrpcbyname_r:3:getrpcent_r:3:
+＠:LDP man-pages:3.75:2014/05/28:getrpcbynumber:3:getrpcent:3:
+＠:LDP man-pages:3.75:2010/09/10:getrpcbynumber_r:3:getrpcent_r:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:getrpcent:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/09/10:getrpcent_r:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:getrpcport:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+☆:LDP man-pages:3.68=>3.75:2014/01/24:gets:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/08/19:getservbyname:3:getservent:3:
+＠:LDP man-pages:3.75:2010/09/10:getservbyname_r:3:getservent_r:3:
+＠:LDP man-pages:3.75:2008/08/19:getservbyport:3:getservent:3:
+＠:LDP man-pages:3.75:2010/09/10:getservbyport_r:3:getservent_r:3:
+☆:LDP man-pages:3.68=>3.75:2008/08/19:getservent:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/09/10:getservent_r:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/28:getspent:3:getspnam:3:
+＠:LDP man-pages:3.75:2014/05/28:getspent_r:3:getspnam:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:getspnam:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/28:getspnam_r:3:getspnam:3:
+☆:LDP man-pages:3.68=>3.75:2014/04/08:getsubopt:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/07/22:getttyent:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2013/07/22:getttynam:3:getttyent:3:
+☆:LDP man-pages:3.68=>3.75:2010/09/10:getumask:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:getusershell:3:2014/06/08::ishioka@dad.eec.toshiba.co.jp:ISHIOKA Takashi:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:getutent:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:getutent_r:3:getutent:3:
+＠:LDP man-pages:3.75:2014/08/19:getutid:3:getutent:3:
+＠:LDP man-pages:3.75:2014/08/19:getutid_r:3:getutent:3:
+＠:LDP man-pages:3.75:2014/08/19:getutline:3:getutent:3:
+＠:LDP man-pages:3.75:2014/08/19:getutline_r:3:getutent:3:
+☆:LDP man-pages:3.68=>3.75:2014/04/08:getutmp:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/04/08:getutmpx:3:getutmp:3:
+＠:LDP man-pages:3.75:2014/08/19:getutxent:3:getutent:3:
+＠:LDP man-pages:3.75:2014/08/19:getutxid:3:getutent:3:
+＠:LDP man-pages:3.75:2014/08/19:getutxline:3:getutent:3:
+☆:LDP man-pages:3.68=>3.75:2010/09/26:getw:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2013/04/19:getwc:3:fgetwc:3:
+＠:LDP man-pages:3.75:2008/08/29:getwc_unlocked:3:unlocked_stdio:3:
+☆:LDP man-pages:3.68=>3.75:1999/07/25:getwchar:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2008/08/29:getwchar_unlocked:3:unlocked_stdio:3:
+＠:LDP man-pages:3.75:2014/08/19:getwd:3:getcwd:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:glob:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2014/08/19:globfree:3:glob:3:
+＠:LDP man-pages:3.75:2014/08/19:gmtime:3:ctime:3:
+＠:LDP man-pages:3.75:2014/08/19:gmtime_r:3:ctime:3:
+＠:LDP man-pages:3.75:2014/05/28:gnu_dev_major:3:makedev:3:
+＠:LDP man-pages:3.75:2014/05/28:gnu_dev_makedev:3:makedev:3:
+＠:LDP man-pages:3.75:2014/05/28:gnu_dev_minor:3:makedev:3:
+＠:LDP man-pages:3.75:2012/08/26:gnu_get_libc_release:3:gnu_get_libc_version:3:
+☆:LDP man-pages:3.68=>3.75:2012/08/26:gnu_get_libc_version:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2008/06/14:grantpt:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2014/03/30:group_member:3:::::
+☆:LDP man-pages:3.68=>3.75:2007/07/26:gsignal:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/03/11:h_errno:3:gethostbyname:3:
+☆:LDP man-pages:3.68=>3.75:2012/04/23:hash:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2009/09/15:hasmntopt:3:getmntent:3:
+＠:LDP man-pages:3.75:2014/01/05:hcreate:3:hsearch:3:
+＠:LDP man-pages:3.75:2014/01/05:hcreate_r:3:hsearch:3:
+＠:LDP man-pages:3.75:2014/01/05:hdestroy:3:hsearch:3:
+＠:LDP man-pages:3.75:2014/01/05:hdestroy_r:3:hsearch:3:
+＠:LDP man-pages:3.75:2014/03/11:herror:3:gethostbyname:3:
+☆:LDP man-pages:3.68=>3.75:2014/01/05:hsearch:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/01/05:hsearch_r:3:hsearch:3:
+＠:LDP man-pages:3.75:2014/03/11:hstrerror:3:gethostbyname:3:
+＠:LDP man-pages:3.75:2010/09/10:htobe16:3:endian:3:
+＠:LDP man-pages:3.75:2010/09/10:htobe32:3:endian:3:
+＠:LDP man-pages:3.75:2010/09/10:htobe64:3:endian:3:
+＠:LDP man-pages:3.75:2010/09/10:htole16:3:endian:3:
+＠:LDP man-pages:3.75:2010/09/10:htole32:3:endian:3:
+＠:LDP man-pages:3.75:2010/09/10:htole64:3:endian:3:
+＠:LDP man-pages:3.75:2014/04/08:htonl:3:byteorder:3:
+＠:LDP man-pages:3.75:2014/04/08:htons:3:byteorder:3:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:hypot:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/20:hypotf:3:hypot:3:
+＠:LDP man-pages:3.75:2010/09/20:hypotl:3:hypot:3:
+☆:LDP man-pages:3.68=>3.75:2014/06/13:iconv:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2008/08/11:iconv_close:3:2014/06/08::sato@complex.eng.hokudai.ac.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2008/08/11:iconv_open:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2012/11/21:if_freenameindex:3:if_nameindex:3:
+＠:LDP man-pages:3.75:2014/04/01:if_indextoname:3:if_nametoindex:3:
+☆:LDP man-pages:3.68=>3.75:2012/11/21:if_nameindex:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/04/01:if_nametoindex:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/08/06:ilogb:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/08/06:ilogbf:3:ilogb:3:
+＠:LDP man-pages:3.75:2013/08/06:ilogbl:3:ilogb:3:
+＠:LDP man-pages:3.75:2014/08/19:imaxabs:3:abs:3:
+＠:LDP man-pages:3.75:2013/07/05:imaxdiv:3:div:3:
+☆:LDP man-pages:3.68=>3.75:2014/04/01:index:3:2014/06/08::nishi@rpts.cl.nec.co.jp:HIROFUMI Nishizuka:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:inet:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/28:inet_addr:3:inet:3:
+＠:LDP man-pages:3.75:2014/05/28:inet_aton:3:inet:3:
+＠:LDP man-pages:3.75:2014/05/28:inet_lnaof:3:inet:3:
+＠:LDP man-pages:3.75:2014/05/28:inet_makeaddr:3:inet_addr:3:
+※:LDP man-pages:3.75:2014/05/28:inet_net_ntop:3:inet_net_pton:3:
+×:LDP man-pages:3.75:2014/05/28:inet_net_pton:3:::::
+＠:LDP man-pages:3.75:2014/05/28:inet_netof:3:inet:3:
+＠:LDP man-pages:3.75:2014/05/28:inet_network:3:inet:3:
+＠:LDP man-pages:3.75:2014/05/28:inet_ntoa:3:inet:3:
+☆:LDP man-pages:3.68=>3.75:2008/11/11:inet_ntop:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2008/06/18:inet_pton:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:1993/06/02:infnan:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2007/07/26:initgroups:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/03/25:initstate:3:random:3:
+＠:LDP man-pages:3.75:2014/03/25:initstate_r:3:random_r:3:
+＠:LDP man-pages:3.75:2014/05/28:innetgr:3:setnetgrent:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:insque:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/11/11:intro:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/28:iruserok:3:rcmd:3:
+＠:LDP man-pages:3.75:2014/05/28:iruserok_af:3:rcmd:3:
+＠:LDP man-pages:3.75:2014/03/18:isalnum:3:isalpha:3:
+＠:LDP man-pages:3.75:2014/03/18:isalnum_l:3:isalpha:3:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:isalpha:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/03/18:isascii:3:isalpha:3:
+＠:LDP man-pages:3.75:2014/03/18:isascii_l:3:isalpha:3:
+☆:LDP man-pages:3.68=>3.75:2014/01/27:isatty:3:2014/06/08::nagoya@cc.hit-u.ac.jp:NAGOYA Hiroaki:
+＠:LDP man-pages:3.75:2014/03/18:isblank:3:isalpha:3:
+＠:LDP man-pages:3.75:2014/03/18:isblank_l:3:isalpha:3:
+＠:LDP man-pages:3.75:2014/03/18:iscntrl:3:isalpha:3:
+＠:LDP man-pages:3.75:2014/03/18:iscntrl_l:3:isalpha:3:
+＠:LDP man-pages:3.75:2014/03/18:isdigit:3:isalpha:3:
+＠:LDP man-pages:3.75:2014/03/18:isdigit_l:3:isalpha:3:
+×:LDP man-pages:3.75:2014/03/13:isfdtype:3:::::
+＠:LDP man-pages:3.75:2013/08/06:isfinite:3:fpclassify:3:
+＠:LDP man-pages:3.75:2014/03/18:isgraph:3:isalpha:3:
+＠:LDP man-pages:3.75:2014/03/18:isgraph_l:3:isalpha:3:
+☆:LDP man-pages:3.68=>3.75:2014/01/27:isgreater:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/01/27:isgreaterequal:3:isgreater:3:
+＠:LDP man-pages:3.75:2013/08/06:isinf:3:fpclassify:3:
+＠:LDP man-pages:3.75:2013/07/22:isinff:3:finite:3:
+＠:LDP man-pages:3.75:2013/07/22:isinfl:3:finite:3:
+＠:LDP man-pages:3.75:2014/01/27:isless:3:isgreater:3:
+＠:LDP man-pages:3.75:2014/01/27:islessequal:3:isgreater:3:
+＠:LDP man-pages:3.75:2014/01/27:islessgreater:3:isgreater:3:
+＠:LDP man-pages:3.75:2014/03/18:islower:3:isalpha:3:
+＠:LDP man-pages:3.75:2014/03/18:islower_l:3:isalpha:3:
+＠:LDP man-pages:3.75:2013/08/06:isnan:3:fpclassify:3:
+＠:LDP man-pages:3.75:2013/07/22:isnanf:3:finite:3:
+＠:LDP man-pages:3.75:2013/07/22:isnanl:3:finite:3:
+＠:LDP man-pages:3.75:2013/08/06:isnormal:3:fpclassify:3:
+＠:LDP man-pages:3.75:2014/03/18:isprint:3:isalpha:3:
+＠:LDP man-pages:3.75:2014/03/18:isprint_l:3:isalpha:3:
+＠:LDP man-pages:3.75:2014/03/18:ispunct:3:isalpha:3:
+＠:LDP man-pages:3.75:2014/03/18:ispunct_l:3:isalpha:3:
+＠:LDP man-pages:3.75:2014/03/18:isspace:3:isalpha:3:
+＠:LDP man-pages:3.75:2014/03/18:isspace_l:3:isalpha:3:
+＠:LDP man-pages:3.75:2014/01/27:isunordered:3:isgreater:3:
+＠:LDP man-pages:3.75:2014/03/18:isupper:3:isalpha:3:
+＠:LDP man-pages:3.75:2014/03/18:isupper_l:3:isalpha:3:
+☆:LDP man-pages:3.68=>3.75:2014/01/28:iswalnum:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2014/01/28:iswalpha:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2014/02/10:iswblank:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2014/02/10:iswcntrl:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2014/02/26:iswctype:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:1999/07/25:iswdigit:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:1999/07/25:iswgraph:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:1999/07/25:iswlower:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:1999/07/25:iswprint:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:1999/07/25:iswpunct:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:1999/07/25:iswspace:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:1999/07/25:iswupper:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:1999/07/25:iswxdigit:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2014/03/18:isxdigit:3:isalpha:3:
+＠:LDP man-pages:3.75:2014/03/18:isxdigit_l:3:isalpha:3:
+☆:LDP man-pages:3.68=>3.75:2014/01/18:j0:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/01/18:j0f:3:j0:3:
+＠:LDP man-pages:3.75:2014/01/18:j0l:3:j0:3:
+＠:LDP man-pages:3.75:2014/01/18:j1:3:j0:3:
+＠:LDP man-pages:3.75:2014/01/18:j1f:3:j0:3:
+＠:LDP man-pages:3.75:2014/01/18:j1l:3:j0:3:
+＠:LDP man-pages:3.75:2014/01/18:jn:3:j0:3:
+＠:LDP man-pages:3.75:2014/01/18:jnf:3:j0:3:
+＠:LDP man-pages:3.75:2014/01/18:jnl:3:j0:3:
+＠:LDP man-pages:3.75:2014/09/21:jrand48:3:drand48:3:
+＠:LDP man-pages:3.75:2013/09/09:jrand48_r:3:drand48_r:3:
+＠:LDP man-pages:3.75:2014/05/28:key_decryptsession:3:key_setsecret:3:
+＠:LDP man-pages:3.75:2014/05/28:key_encryptsession:3:key_setsecret:3:
+＠:LDP man-pages:3.75:2014/05/28:key_gendes:3:key_setsecret:3:
+＠:LDP man-pages:3.75:2014/05/28:key_secretkey_is_set:3:key_setsecret:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:key_setsecret:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/07/08:klogctl:3:syslog:2:
+＠:LDP man-pages:3.75:2014/05/28:l64a:3:a64l:3:
+＠:LDP man-pages:3.75:2014/08/19:labs:3:abs:3:
+＠:LDP man-pages:3.75:2014/05/28:lckpwdf:3:getspnam:3:
+＠:LDP man-pages:3.75:2014/09/21:lcong48:3:drand48:3:
+＠:LDP man-pages:3.75:2013/09/09:lcong48_r:3:drand48_r:3:
+☆:LDP man-pages:3.68=>3.75:2013/08/19:ldexp:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/08/19:ldexpf:3:ldexp:3:
+＠:LDP man-pages:3.75:2013/08/19:ldexpl:3:ldexp:3:
+＠:LDP man-pages:3.75:2013/07/05:ldiv:3:div:3:
+＠:LDP man-pages:3.75:2010/09/10:le16toh:3:endian:3:
+＠:LDP man-pages:3.75:2010/09/10:le32toh:3:endian:3:
+＠:LDP man-pages:3.75:2010/09/10:le64toh:3:endian:3:
+＠:LDP man-pages:3.75:1999/09/27:lfind:3:lsearch:3:
+☆:LDP man-pages:3.68=>3.75:2014/01/18:lgamma:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/01/18:lgamma_r:3:lgamma:3:
+＠:LDP man-pages:3.75:2014/01/18:lgammaf:3:lgamma:3:
+＠:LDP man-pages:3.75:2014/01/18:lgammaf_r:3:lgamma:3:
+＠:LDP man-pages:3.75:2014/01/18:lgammal:3:lgamma:3:
+＠:LDP man-pages:3.75:2014/01/18:lgammal_r:3:lgamma:3:
+☆:LDP man-pages:3.68=>3.75:2012/05/08:lio_listio:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:llabs:3:abs:3:
+＠:LDP man-pages:3.75:2013/07/05:lldiv:3:div:3:
+＠:LDP man-pages:3.75:2014/01/18:llrint:3:lrint:3:
+＠:LDP man-pages:3.75:2014/01/18:llrintf:3:lrint:3:
+＠:LDP man-pages:3.75:2014/01/18:llrintl:3:lrint:3:
+＠:LDP man-pages:3.75:2013/08/26:llround:3:lround:3:
+＠:LDP man-pages:3.75:2013/08/26:llroundf:3:lround:3:
+＠:LDP man-pages:3.75:2013/08/26:llroundl:3:lround:3:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:localeconv:3:2014/06/08::tyoshino@eng.toyo.ac.jp:Takashi Yoshino:
+＠:LDP man-pages:3.75:2014/08/19:localtime:3:ctime:3:
+＠:LDP man-pages:3.75:2014/08/19:localtime_r:3:ctime:3:
+☆:LDP man-pages:3.68=>3.75:2014/06/13:lockf:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:log:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:log10:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/20:log10f:3:log10:3:
+＠:LDP man-pages:3.75:2010/09/20:log10l:3:log10:3:
+☆:LDP man-pages:3.68=>3.75:2014/02/28:log1p:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/02/28:log1pf:3:log1p:3:
+＠:LDP man-pages:3.75:2014/02/28:log1pl:3:log1p:3:
+☆:LDP man-pages:3.68=>3.75:2010/09/12:log2:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/12:log2f:3:log2:3:
+＠:LDP man-pages:3.75:2010/09/12:log2l:3:log2:3:
+☆:LDP man-pages:3.68=>3.75:2014/02/28:logb:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/02/28:logbf:3:logb:3:
+＠:LDP man-pages:3.75:2014/02/28:logbl:3:logb:3:
+＠:LDP man-pages:3.75:2010/09/20:logf:3:log:3:
+☆:LDP man-pages:3.68=>3.75:2004/05/06:login:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/08/19:login_tty:3:openpty:3:
+＠:LDP man-pages:3.75:2010/09/20:logl:3:log:3:
+＠:LDP man-pages:3.75:2004/05/06:logout:3:login:3:
+＠:LDP man-pages:3.75:2014/08/19:logwtmp:3:updwtmp:3:
+☆:LDP man-pages:3.68=>3.75:2009/01/13:longjmp:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/09/21:lrand48:3:drand48:3:
+＠:LDP man-pages:3.75:2013/09/09:lrand48_r:3:drand48_r:3:
+☆:LDP man-pages:3.68=>3.75:2014/01/18:lrint:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/01/18:lrintf:3:lrint:3:
+＠:LDP man-pages:3.75:2014/01/18:lrintl:3:lrint:3:
+☆:LDP man-pages:3.68=>3.75:2013/08/26:lround:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/08/26:lroundf:3:lround:3:
+＠:LDP man-pages:3.75:2013/08/26:lroundl:3:lround:3:
+☆:LDP man-pages:3.68=>3.75:1999/09/27:lsearch:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:lseek64:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2013/10/29:lutimes:3:futimes:3:
+＠:LDP man-pages:3.75:2014/05/28:major:3:makedev:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:makecontext:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:makedev:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2012/05/06:mallinfo:3:::::
+☆:LDP man-pages:3.68=>3.75:2014/05/21:malloc:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2014/06/13:malloc_get_state:3:::::
+☆:LDP man-pages:3.68=>3.75:2010/10/13:malloc_hook:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/04/19:malloc_info:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+※:LDP man-pages:3.75:2014/06/13:malloc_set_state:3:malloc_get_state:3:
+☆:LDP man-pages:3.68=>3.75:2012/05/06:malloc_stats:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2014/05/28:malloc_trim:3:::::
+×:LDP man-pages:3.75:2014/06/13:malloc_usable_size:3:::::
+×:LDP man-pages:3.75:2014/07/08:mallopt:3:::::
+☆:LDP man-pages:3.68=>3.75:2014/06/13:matherr:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:mblen:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:mbrlen:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:mbrtowc:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:mbsinit:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:mbsnrtowcs:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:mbsrtowcs:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:mbstowcs:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:mbtowc:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+×:LDP man-pages:3.75:2014/01/11:mcheck:3:::::
+※:LDP man-pages:3.75:2014/01/11:mcheck_check_all:3:mcheck:3:
+※:LDP man-pages:3.75:2014/01/11:mcheck_pedantic:3:mcheck:3:
+＠:LDP man-pages:3.75:2013/09/02:memalign:3:posix_memalign:3:
+☆:LDP man-pages:3.68=>3.75:2014/03/10:memccpy:3:2014/06/08::tyoshino@eng.toyo.ac.jp:Takashi Yoshino:
+☆:LDP man-pages:3.68=>3.75:2014/03/10:memchr:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/03/14:memcmp:3:2014/06/08::nishi@rpts.cl.nec.co.jp:HIROFUMI Nishizuka:
+☆:LDP man-pages:3.68=>3.75:2014/03/17:memcpy:3:2014/06/08::tyoshino@eng.toyo.ac.jp:Takashi Yoshino:
+☆:LDP man-pages:3.68=>3.75:2014/03/17:memfrob:3:2014/06/08::ishikawa@linux.or.jp:ISHIKAWA Mutsumi:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:memmem:3:2014/06/08::tyoshino@eng.toyo.ac.jp:Takashi Yoshino:
+☆:LDP man-pages:3.68=>3.75:2014/03/17:memmove:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:mempcpy:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/03/10:memrchr:3:memchr:3:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:memset:3:2014/06/08::tyoshino@eng.toyo.ac.jp:Takashi Yoshino:
+＠:LDP man-pages:3.75:2014/05/28:minor:3:makedev:3:
+☆:LDP man-pages:3.68=>3.75:2014/06/13:mkdtemp:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/03/24:mkfifo:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2014/03/24:mkfifoat:3:mkfifo:3:
+＠:LDP man-pages:3.75:2014/08/19:mkostemp:3:mkstemp:3:
+＠:LDP man-pages:3.75:2014/08/19:mkostemps:3:mkstemp:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:mkstemp:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:mkstemps:3:mkstemp:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:mktemp:3:2014/06/08::tanisako@osa.dec.com:Kazuyuki Tanisako:
+＠:LDP man-pages:3.75:2014/08/19:mktime:3:ctime:3:
+＠:LDP man-pages:3.75:2014/08/19:mmap64:3:mmap:2:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:modf:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/06/21:modff:3:modf:3:
+＠:LDP man-pages:3.75:2013/06/21:modfl:3:modf:3:
+☆:LDP man-pages:3.68=>3.75:2012/04/26:mpool:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+※:LDP man-pages:3.75:2014/01/11:mprobe:3:mcheck:3:
+☆:LDP man-pages:3.68=>3.75:2014/06/13:mq_close:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:mq_getattr:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/04/06:mq_notify:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:mq_open:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/06/03:mq_receive:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/06/03:mq_send:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/10/02:mq_setattr:3:mq_getattr:3:
+＠:LDP man-pages:3.75:2014/06/03:mq_timedreceive:3:mq_receive:3:
+＠:LDP man-pages:3.75:2014/06/03:mq_timedsend:3:mq_send:3:
+☆:LDP man-pages:3.68=>3.75:2014/06/13:mq_unlink:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/09/21:mrand48:3:drand48:3:
+＠:LDP man-pages:3.75:2013/09/09:mrand48_r:3:drand48_r:3:
+×:LDP man-pages:3.75:2012/04/18:mtrace:3:::::
+※:LDP man-pages:3.75:2012/04/18:muntrace:3:mtrace:3:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:nan:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/20:nanf:3:nan:3:
+＠:LDP man-pages:3.75:2010/09/20:nanl:3:nan:3:
+＠:LDP man-pages:3.75:2013/08/26:nearbyint:3:rint:3:
+＠:LDP man-pages:3.75:2013/08/26:nearbyintf:3:rint:3:
+＠:LDP man-pages:3.75:2013/08/26:nearbyintl:3:rint:3:
+☆:LDP man-pages:3.68=>3.75:2014/03/20:netlink:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+×:LDP man-pages:3.75:2014/05/28:newlocale:3:::::
+☆:LDP man-pages:3.68=>3.75:2013/09/02:nextafter:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/09/02:nextafterf:3:nextafter:3:
+＠:LDP man-pages:3.75:2013/09/02:nextafterl:3:nextafter:3:
+＠:LDP man-pages:3.75:2013/09/02:nexttoward:3:nextafter:3:
+＠:LDP man-pages:3.75:2013/09/02:nexttowardf:3:nextafter:3:
+＠:LDP man-pages:3.75:2013/09/02:nexttowardl:3:nextafter:3:
+＠:LDP man-pages:3.75:2014/08/19:nftw:3:ftw:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:nl_langinfo:3:2014/06/08::KY4N-UCD@asahi-net.or.jp:UCHIDA Norihiro:
+＠:LDP man-pages:3.75:2014/09/21:nrand48:3:drand48:3:
+＠:LDP man-pages:3.75:2013/09/09:nrand48_r:3:drand48_r:3:
+＠:LDP man-pages:3.75:2014/04/08:ntohl:3:byteorder:3:
+＠:LDP man-pages:3.75:2014/04/08:ntohs:3:byteorder:3:
+☆:LDP man-pages:3.68=>3.75:2014/04/06:offsetof:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:on_exit:3:2014/06/08:o:amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/04/06:open_memstream:3:fmemopen:3:
+＠:LDP man-pages:3.75:2014/04/06:open_wmemstream:3:fmemopen:3:
+☆:LDP man-pages:3.68=>3.75:2010/06/20:opendir:3:2014/06/08:o:amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2012/08/17:openlog:3:syslog:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:openpty:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/09:optarg:3:getopt:3:
+＠:LDP man-pages:3.75:2014/05/09:opterr:3:getopt:3:
+＠:LDP man-pages:3.75:2014/05/09:optind:3:getopt:3:
+＠:LDP man-pages:3.75:2014/05/09:optopt:3:getopt:3:
+＠:LDP man-pages:3.75:2014/08/19:passwd2des:3:xcrypt:3:
+＠:LDP man-pages:3.75:2014/05/28:pathconf:3:fpathconf:3:
+＠:LDP man-pages:3.75:2013/04/19:pclose:3:popen:3:
+☆:LDP man-pages:3.67=>3.75:2014/05/28:perror:3:2014/06/04::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/09/26:pmap_getmaps:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:pmap_getport:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:pmap_rmtcall:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:pmap_set:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:pmap_unset:3:rpc:3:
+☆:LDP man-pages:3.68=>3.75:2013/04/19:popen:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/06/03:posix_fallocate:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2013/09/02:posix_memalign:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/06/03:posix_openpt:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/09/12:pow:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2008/08/11:pow10:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2008/08/11:pow10f:3:pow10:3:
+＠:LDP man-pages:3.75:2008/08/11:pow10l:3:pow10:3:
+＠:LDP man-pages:3.75:2010/09/12:powf:3:pow:3:
+＠:LDP man-pages:3.75:2010/09/12:powl:3:pow:3:
+☆:LDP man-pages:3.68=>3.75:2014/07/08:printf:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/07/08:profil:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2006/04/29:program_invocation_name:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2006/04/29:program_invocation_short_name:3:program_invocation_name:3:
+＠:LDP man-pages:3.75:2010/10/06:psiginfo:3:psignal:3:
+☆:LDP man-pages:3.68=>3.75:2010/10/06:psignal:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/11/11:pthread_attr_destroy:3:pthread_attr_init:3:
+＠:LDP man-pages:3.75:2014/05/28:pthread_attr_getaffinity_np:3:pthread_attr_setaffinity_np:3:
+＠:LDP man-pages:3.75:2014/05/28:pthread_attr_getdetachstate:3:pthread_attr_setdetachstate:3:
+＠:LDP man-pages:3.75:2014/05/28:pthread_attr_getguardsize:3:pthread_attr_setguardsize:3:
+＠:LDP man-pages:3.75:2014/05/21:pthread_attr_getinheritsched:3:pthread_attr_setinheritsched:3:
+＠:LDP man-pages:3.75:2014/05/21:pthread_attr_getschedparam:3:pthread_attr_setschedparam:3:
+＠:LDP man-pages:3.75:2014/05/21:pthread_attr_getschedpolicy:3:pthread_attr_setschedpolicy:3:
+＠:LDP man-pages:3.75:2014/05/28:pthread_attr_getscope:3:pthread_attr_setscope:3:
+＠:LDP man-pages:3.75:2014/05/28:pthread_attr_getstack:3:pthread_attr_setstack:3:
+＠:LDP man-pages:3.75:2014/05/28:pthread_attr_getstackaddr:3:pthread_attr_setstackaddr:3:
+＠:LDP man-pages:3.75:2014/05/28:pthread_attr_getstacksize:3:pthread_attr_setstacksize:3:
+☆:LDP man-pages:3.68=>3.75:2008/11/11:pthread_attr_init:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:pthread_attr_setaffinity_np:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:pthread_attr_setdetachstate:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:pthread_attr_setguardsize:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/21:pthread_attr_setinheritsched:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/21:pthread_attr_setschedparam:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/21:pthread_attr_setschedpolicy:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:pthread_attr_setscope:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:pthread_attr_setstack:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:pthread_attr_setstackaddr:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:pthread_attr_setstacksize:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2008/11/17:pthread_cancel:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/11/24:pthread_cleanup_pop:3:pthread_cleanup_push:3:
+＠:LDP man-pages:3.75:2014/05/28:pthread_cleanup_pop_restore_np:3:pthread_cleanup_push_defer_np:3:
+☆:LDP man-pages:3.68=>3.75:2008/11/24:pthread_cleanup_push:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:pthread_cleanup_push_defer_np:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:pthread_create:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2008/11/27:pthread_detach:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/23:pthread_equal:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/23:pthread_exit:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/23:pthread_getaffinity_np:3:pthread_setaffinity_np:3:
+☆:LDP man-pages:3.68=>3.75:2010/09/10:pthread_getattr_np:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/23:pthread_getconcurrency:3:pthread_setconcurrency:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/23:pthread_getcpuclockid:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/28:pthread_getname_np:3:pthread_setname_np:3:
+＠:LDP man-pages:3.75:2014/05/28:pthread_getschedparam:3:pthread_setschedparam:3:
+☆:LDP man-pages:3.68=>3.75:2008/11/27:pthread_join:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/13:pthread_kill:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/13:pthread_kill_other_threads_np:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+※:LDP man-pages:3.75:2014/10/15:pthread_rwlockattr_getkind_np:3:pthread_rwlockattr_setkind_np:3:
+×:LDP man-pages:3.75:2014/10/15:pthread_rwlockattr_setkind_np:3:::::
+☆:LDP man-pages:3.68=>3.75:2014/05/13:pthread_self:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/23:pthread_setaffinity_np:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/13:pthread_setcancelstate:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/13:pthread_setcanceltype:3:pthread_setcancelstate:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/23:pthread_setconcurrency:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:pthread_setname_np:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:pthread_setschedparam:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:pthread_setschedprio:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/19:pthread_sigmask:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:pthread_sigqueue:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/19:pthread_testcancel:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/10:pthread_timedjoin_np:3:pthread_tryjoin_np:3:
+☆:LDP man-pages:3.68=>3.75:2010/09/10:pthread_tryjoin_np:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/13:pthread_yield:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:ptsname:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/06/21:ptsname_r:3:ptsname:3:
+＠:LDP man-pages:3.75:2014/01/11:putc:3:puts:3:
+＠:LDP man-pages:3.75:2008/08/29:putc_unlocked:3:unlocked_stdio:3:
+＠:LDP man-pages:3.75:2014/01/11:putchar:3:puts:3:
+＠:LDP man-pages:3.75:2008/08/29:putchar_unlocked:3:unlocked_stdio:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:putenv:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2003/09/09:putgrent:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2013/04/19:putpwent:3:2014/06/08::nishi@rpts.cl.nec.co.jp:HIROFUMI Nishizuka:
+☆:LDP man-pages:3.68=>3.75:2014/01/11:puts:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2014/05/28:putspent:3:getspnam:3:
+＠:LDP man-pages:3.75:2014/08/19:pututline:3:getutent:3:
+＠:LDP man-pages:3.75:2014/08/19:pututxline:3:getutent:3:
+＠:LDP man-pages:3.75:2010/09/26:putw:3:getw:3:
+＠:LDP man-pages:3.75:2013/04/19:putwc:3:fputwc:3:
+＠:LDP man-pages:3.75:2008/08/29:putwc_unlocked:3:unlocked_stdio:3:
+☆:LDP man-pages:3.68=>3.75:1999/07/25:putwchar:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2008/08/29:putwchar_unlocked:3:unlocked_stdio:3:
+＠:LDP man-pages:3.75:2013/09/02:pvalloc:3:posix_memalign:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:qecvt:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2007/07/26:qecvt_r:3:ecvt_r:3:
+＠:LDP man-pages:3.75:2014/08/19:qfcvt:3:qecvt:3:
+＠:LDP man-pages:3.75:2007/07/26:qfcvt_r:3:ecvt_r:3:
+＠:LDP man-pages:3.75:2014/08/19:qgcvt:3:qecvt:3:
+☆:LDP man-pages:3.68=>3.75:2012/03/08:qsort:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2012/03/08:qsort_r:3:qsort:3:
+☆:LDP man-pages:3.68=>3.75:2007/12/28:queue:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/03/10:raise:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/01/18:rand:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/01/18:rand_r:3:rand:3:
+☆:LDP man-pages:3.68=>3.75:2014/03/25:random:3:2014/06/08::tyoshino@eng.toyo.ac.jp:YOSHINO Takashi:
+☆:LDP man-pages:3.68=>3.75:2014/03/25:random_r:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/03/10:rawmemchr:3:memchr:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:rcmd:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/28:rcmd_af:3:rcmd:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:re_comp:3:2014/06/08::nishi@rpts.cl.nec.co.jp:HIROFUMI Nishizuka:
+＠:LDP man-pages:3.75:2014/05/28:re_exec:3:re_comp:3:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:readdir:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/06/21:readdir_r:3:readdir:3:
+＠:LDP man-pages:3.75:2014/05/21:realloc:3:malloc:3:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:realpath:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/04/23:recno:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/02/11:regcomp:3:regex:3:
+＠:LDP man-pages:3.75:2013/02/11:regerror:3:regex:3:
+☆:LDP man-pages:3.68=>3.75:2013/02/11:regex:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/02/11:regexec:3:regex:3:
+＠:LDP man-pages:3.75:2013/02/11:regfree:3:regex:3:
+＠:LDP man-pages:3.75:2013/09/26:registerrpc:3:rpc:3:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:remainder:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/20:remainderf:3:remainder:3:
+＠:LDP man-pages:3.75:2010/09/20:remainderl:3:remainder:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:remove:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2014/08/19:remque:3:insque:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/10:remquo:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/10:remquof:3:remquo:3:
+＠:LDP man-pages:3.75:2014/05/10:remquol:3:remquo:3:
+＠:LDP man-pages:3.75:2014/05/28:res_init:3:resolver:3:
+＠:LDP man-pages:3.75:2014/05/28:res_mkquery:3:resolver:3:
+＠:LDP man-pages:3.75:2014/05/28:res_query:3:resolver:3:
+＠:LDP man-pages:3.75:2014/05/28:res_querydomain:3:resolver:3:
+＠:LDP man-pages:3.75:2014/05/28:res_search:3:resolver:3:
+＠:LDP man-pages:3.75:2014/05/28:res_send:3:resolver:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:resolver:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/28:rewind:3:fseek:3:
+☆:LDP man-pages:3.68=>3.75:2013/09/02:rewinddir:3:2014/06/08::nishi@rpts.cl.nec.co.jp:HIROFUMI Nishizuka:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:rexec:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/28:rexec_af:3:rexec:3:
+＠:LDP man-pages:3.75:2014/04/01:rindex:3:index:3:
+☆:LDP man-pages:3.68=>3.75:2013/08/26:rint:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/08/26:rintf:3:rint:3:
+＠:LDP man-pages:3.75:2013/08/26:rintl:3:rint:3:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:round:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/06/21:roundf:3:round:3:
+＠:LDP man-pages:3.75:2013/06/21:roundl:3:round:3:
+☆:LDP man-pages:3.68=>3.75:2013/09/26:rpc:3:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2007/07/26:rpmatch:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/28:rresvport:3:rcmd:3:
+＠:LDP man-pages:3.75:2014/05/28:rresvport_af:3:rcmd:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:rtime:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2014/09/06:rtnetlink:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/28:ruserok:3:rcmd:3:
+＠:LDP man-pages:3.75:2014/05/28:ruserok_af:3:rcmd:3:
+☆:LDP man-pages:3.68=>3.75:2013/03/23:scalb:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/03/23:scalbf:3:scalb:3:
+＠:LDP man-pages:3.75:2013/03/23:scalbl:3:scalb:3:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:scalbln:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/06/21:scalblnf:3:scalbln:3:
+＠:LDP man-pages:3.75:2013/06/21:scalblnl:3:scalbln:3:
+＠:LDP man-pages:3.75:2013/06/21:scalbn:3:scalbln:3:
+＠:LDP man-pages:3.75:2013/06/21:scalbnf:3:scalbln:3:
+＠:LDP man-pages:3.75:2013/06/21:scalbnl:3:scalbln:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:scandir:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/28:scandirat:3:scandir:3:
+☆:LDP man-pages:3.68=>3.75:2014/01/11:scanf:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/10:sched_getcpu:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2012/08/14:secure_getenv:3:getenv:3:
+＠:LDP man-pages:3.75:2014/09/21:seed48:3:drand48:3:
+＠:LDP man-pages:3.75:2013/09/09:seed48_r:3:drand48_r:3:
+☆:LDP man-pages:3.68=>3.75:2013/09/09:seekdir:3:2014/06/08::nishi@rpts.cl.nec.co.jp:HIROFUMI Nishizuka:
+☆:LDP man-pages:3.68=>3.75:2012/05/13:sem_close:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/03/03:sem_destroy:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/03/03:sem_getvalue:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/03/10:sem_init:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/05/13:sem_open:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/02/26:sem_post:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/02/26:sem_timedwait:3:sem_wait:3:
+＠:LDP man-pages:3.75:2014/02/26:sem_trywait:3:sem_wait:3:
+☆:LDP man-pages:3.68=>3.75:2014/02/26:sem_unlink:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/02/26:sem_wait:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2003/09/09:setaliasent:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:setbuf:3:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/08/19:setbuffer:3:setbuf:3:
+＠:LDP man-pages:3.75:2014/04/08:setcontext:3:getcontext:3:
+☆:LDP man-pages:3.68=>3.75:2013/10/11:setenv:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2002/02/28:setfsent:3:getfsent:3:
+＠:LDP man-pages:3.75:2014/10/02:setgrent:3:getgrent:3:
+＠:LDP man-pages:3.75:2014/03/11:sethostent:3:gethostbyname:3:
+＠:LDP man-pages:3.75:2010/09/20:sethostid:3:gethostid:3:
+☆:LDP man-pages:3.68=>3.75:2014/01/07:setjmp:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2013/07/22:setkey:3:encrypt:3:
+＠:LDP man-pages:3.75:2013/07/22:setkey_r:3:encrypt:3:
+＠:LDP man-pages:3.75:2014/08/19:setlinebuf:3:setbuf:3:
+☆:LDP man-pages:3.67=>3.75:2014/05/28:setlocale:3:2014/06/04::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2001/10/05:setlogmask:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2009/09/15:setmntent:3:getmntent:3:
+＠:LDP man-pages:3.75:2008/08/19:setnetent:3:getnetent:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:setnetgrent:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/08/19:setprotoent:3:getprotoent:3:
+＠:LDP man-pages:3.75:2013/06/21:setpwent:3:getpwent:3:
+＠:LDP man-pages:3.75:2014/05/28:setrpcent:3:getrpcent:3:
+＠:LDP man-pages:3.75:2008/08/19:setservent:3:getservent:3:
+＠:LDP man-pages:3.75:2014/05/28:setspent:3:getspnam:3:
+＠:LDP man-pages:3.75:2014/03/25:setstate:3:random:3:
+＠:LDP man-pages:3.75:2014/03/25:setstate_r:3:random_r:3:
+＠:LDP man-pages:3.75:2013/07/22:setttyent:3:getttyent:3:
+＠:LDP man-pages:3.75:2013/06/21:setusershell:3:getusershell:3:
+＠:LDP man-pages:3.75:2014/08/19:setutent:3:getutent:3:
+＠:LDP man-pages:3.75:2014/08/19:setutxent:3:getutent:3:
+＠:LDP man-pages:3.75:2014/08/19:setvbuf:3:setbuf:3:
+＠:LDP man-pages:3.75:2014/05/28:sgetspent:3:getspnam:3:
+＠:LDP man-pages:3.75:2014/05/28:sgetspent_r:3:getspnam:3:
+☆:LDP man-pages:3.68=>3.75:2009/02/25:shm_open:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2009/02/25:shm_unlink:3:shm_open:3:
+＠:LDP man-pages:3.75:2014/04/14:sigaddset:3:sigsetops:3:
+＠:LDP man-pages:3.75:2014/04/14:sigandset:3:sigsetops:3:
+＠:LDP man-pages:3.75:2014/05/28:sigblock:3:sigvec:3:
+＠:LDP man-pages:3.75:2014/04/14:sigdelset:3:sigsetops:3:
+＠:LDP man-pages:3.75:2014/04/14:sigemptyset:3:sigsetops:3:
+＠:LDP man-pages:3.75:2014/04/14:sigfillset:3:sigsetops:3:
+＠:LDP man-pages:3.75:2014/05/28:siggetmask:3:sigvec:3:
+＠:LDP man-pages:3.75:2010/09/20:sighold:3:sigset:3:
+＠:LDP man-pages:3.75:2010/09/20:sigignore:3:sigset:3:
+☆:LDP man-pages:3.68=>3.75:2014/06/13:siginterrupt:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+＠:LDP man-pages:3.75:2014/04/14:sigisemptyset:3:sigsetops:3:
+＠:LDP man-pages:3.75:2014/04/14:sigismember:3:sigsetops:3:
+＠:LDP man-pages:3.75:2009/01/13:siglongjmp:3:longjmp:3:
+＠:LDP man-pages:3.75:2014/05/28:sigmask:3:sigvec:3:
+☆:LDP man-pages:3.68=>3.75:2013/07/04:signbit:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/01/18:signgam:3:lgamma:3:
+☆:LDP man-pages:3.68=>3.75:2009/02/04:significand:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2009/02/04:significandf:3:significand:3:
+＠:LDP man-pages:3.75:2009/02/04:significandl:3:significand:3:
+＠:LDP man-pages:3.75:2014/04/14:sigorset:3:sigsetops:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:sigpause:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/12/16:sigqueue:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/20:sigrelse:3:sigset:3:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:sigset:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/01/07:sigsetjmp:3:setjmp:3:
+＠:LDP man-pages:3.75:2014/05/28:sigsetmask:3:sigvec:3:
+☆:LDP man-pages:3.68=>3.75:2014/04/14:sigsetops:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/26:sigstack:3:sigaltstack:2:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:sigvec:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/12/16:sigwait:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/12/16:sin:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/12/23:sincos:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/12/23:sincosf:3:sincos:3:
+＠:LDP man-pages:3.75:2013/12/23:sincosl:3:sincos:3:
+＠:LDP man-pages:3.75:2013/12/16:sinf:3:sin:3:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:sinh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/20:sinhf:3:sinh:3:
+＠:LDP man-pages:3.75:2010/09/20:sinhl:3:sinh:3:
+＠:LDP man-pages:3.75:2013/12/16:sinl:3:sin:3:
+☆:LDP man-pages:3.68=>3.75:2010/02/03:sleep:3:2014/06/08::tyoshino@eng.toyo.ac.jp:YOSHINO Takashi:
+＠:LDP man-pages:3.75:2014/07/08:snprintf:3:printf:3:
+☆:LDP man-pages:3.68=>3.75:2014/02/28:sockatmark:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/07/08:sprintf:3:printf:3:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:sqrt:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/20:sqrtf:3:sqrt:3:
+＠:LDP man-pages:3.75:2010/09/20:sqrtl:3:sqrt:3:
+＠:LDP man-pages:3.75:2014/01/18:srand:3:rand:3:
+＠:LDP man-pages:3.75:2014/09/21:srand48:3:drand48:3:
+＠:LDP man-pages:3.75:2013/09/09:srand48_r:3:drand48_r:3:
+＠:LDP man-pages:3.75:2014/03/25:srandom:3:random:3:
+＠:LDP man-pages:3.75:2014/03/25:srandom_r:3:random_r:3:
+＠:LDP man-pages:3.75:2014/01/11:sscanf:3:scanf:3:
+＠:LDP man-pages:3.75:2007/07/26:ssignal:3:gsignal:3:
+☆:LDP man-pages:3.68=>3.75:2013/09/26:statvfs:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2013/12/10:stdarg:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2008/07/14:stderr:3:stdin:3:
+☆:LDP man-pages:3.68=>3.75:2008/07/14:stdin:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2001/12/26:stdio:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:stdio_ext:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2008/07/14:stdout:3:stdin:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/10:stpcpy:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/10:stpncpy:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+☆:LDP man-pages:3.68=>3.75:2014/05/10:strcasecmp:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:strcasestr:3:strstr:3:
+☆:LDP man-pages:3.68=>3.75:2014/01/20:strcat:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/01/20:strchr:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/01/20:strchrnul:3:strchr:3:
+☆:LDP man-pages:3.68=>3.75:2014/01/20:strcmp:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:strcoll:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/21:strcpy:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/02/28:strcspn:3:strspn:3:
+☆:LDP man-pages:3.68=>3.75:2013/04/19:strdup:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/04/19:strdupa:3:strdup:3:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:strerror:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/03/18:strerror_r:3:strerror:3:
+☆:LDP man-pages:3.68=>3.75:2000/12/05:strfmon:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:strfry:3:2014/06/08::motoki@hal.t.u-tokyo.ac.jp:Akihiro Motoki:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:strftime:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/01/04:string:3:2014/06/08::yoshino@civil.jcn.nihon-u.ac.jp:YOSHINO Takashi:
+☆:LDP man-pages:3.68=>3.75:2014/02/25:strlen:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/10:strncasecmp:3:strcasecmp:3:
+＠:LDP man-pages:3.75:2014/01/20:strncat:3:strcat:3:
+＠:LDP man-pages:3.75:2014/01/20:strncmp:3:strcmp:3:
+＠:LDP man-pages:3.75:2014/05/21:strncpy:3:strcpy:3:
+＠:LDP man-pages:3.75:2013/04/19:strndup:3:strdup:3:
+＠:LDP man-pages:3.75:2013/04/19:strndupa:3:strdup:3:
+☆:LDP man-pages:3.68=>3.75:2014/02/25:strnlen:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/02/25:strpbrk:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:strptime:3:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/01/20:strrchr:3:strchr:3:
+☆:LDP man-pages:3.68=>3.75:2014/02/25:strsep:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2010/09/15:strsignal:3:2014/06/08::argrath@yo.rim.or.jp:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2014/02/28:strspn:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:strstr:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:strtod:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:strtof:3:strtod:3:
+☆:LDP man-pages:3.68=>3.75:2014/01/22:strtoimax:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2013/05/19:strtok:3:2014/06/08:o:amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/05/19:strtok_r:3:strtok:3:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:strtol:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:strtold:3:strtod:3:
+＠:LDP man-pages:3.75:2014/03/18:strtoll:3:strtol:3:
+＠:LDP man-pages:3.75:2014/03/18:strtoq:3:strtol:3:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:strtoul:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/03/18:strtoull:3:strtoul:3:
+＠:LDP man-pages:3.75:2014/01/22:strtoumax:3:strtoimax:3:
+＠:LDP man-pages:3.75:2014/03/18:strtouq:3:strtoul:3:
+☆:LDP man-pages:3.68=>3.75:2001/12/19:strverscmp:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/05/10:strxfrm:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/09/26:svc_destroy:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:svc_freeargs:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:svc_getargs:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:svc_getcaller:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:svc_getreq:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:svc_getreqset:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:svc_register:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:svc_run:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:svc_sendreply:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:svc_unregister:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:svcerr_auth:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:svcerr_decode:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:svcerr_noproc:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:svcerr_noprog:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:svcerr_progvers:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:svcerr_systemerr:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:svcerr_weakauth:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:svcfd_create:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:svcraw_create:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:svctcp_create:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:svcudp_bufcreate:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:svcudp_create:3:rpc:3:
+☆:LDP man-pages:3.68=>3.75:2014/02/25:swab:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2014/05/28:swapcontext:3:makecontext:3:
+＠:LDP man-pages:3.75:2014/03/19:swprintf:3:wprintf:3:
+＠:LDP man-pages:3.75:2014/05/28:sys_errlist:3:perror:3:
+＠:LDP man-pages:3.75:2014/05/28:sys_nerr:3:perror:3:
+☆:LDP man-pages:3.68=>3.75:2014/03/20:sysconf:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/08/17:syslog:3:2014/06/08:o:amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.65=>3.75:2014/06/13:system:3:2014/04/24:o:amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/01/06:sysv_signal:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/01/06:tan:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/01/06:tanf:3:tan:3:
+☆:LDP man-pages:3.68=>3.75:2014/01/07:tanh:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/01/07:tanhf:3:tanh:3:
+＠:LDP man-pages:3.75:2014/01/07:tanhl:3:tanh:3:
+＠:LDP man-pages:3.75:2014/01/06:tanl:3:tan:3:
+＠:LDP man-pages:3.75:2014/05/08:tcdrain:3:termios:3:
+＠:LDP man-pages:3.75:2014/05/08:tcflow:3:termios:3:
+＠:LDP man-pages:3.75:2014/05/08:tcflush:3:termios:3:
+＠:LDP man-pages:3.75:2014/05/08:tcgetattr:3:termios:3:
+☆:LDP man-pages:3.68=>3.75:2014/01/13:tcgetpgrp:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/01/13:tcgetsid:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/08:tcsendbreak:3:termios:3:
+＠:LDP man-pages:3.75:2014/05/08:tcsetattr:3:termios:3:
+＠:LDP man-pages:3.75:2014/01/13:tcsetpgrp:3:tcgetpgrp:3:
+＠:LDP man-pages:3.75:2014/05/28:tdelete:3:tsearch:3:
+＠:LDP man-pages:3.75:2014/05/28:tdestroy:3:tsearch:3:
+☆:LDP man-pages:3.68=>3.75:2013/09/02:telldir:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/02/27:tempnam:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/05/08:termios:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/28:tfind:3:tsearch:3:
+☆:LDP man-pages:3.68=>3.75:2010/09/20:tgamma:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/09/20:tgammaf:3:tgamma:3:
+＠:LDP man-pages:3.75:2010/09/20:tgammal:3:tgamma:3:
+☆:LDP man-pages:3.68=>3.75:2013/07/04:timegm:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+＠:LDP man-pages:3.75:2013/07/04:timelocal:3:timegm:3:
+☆:LDP man-pages:3.68=>3.75:2010/02/25:timeradd:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2010/02/25:timerclear:3:timeradd:3:
+＠:LDP man-pages:3.75:2010/02/25:timercmp:3:timeradd:3:
+＠:LDP man-pages:3.75:2010/02/25:timerisset:3:timeradd:3:
+＠:LDP man-pages:3.75:2010/02/25:timersub:3:timeradd:3:
+＠:LDP man-pages:3.75:2014/08/19:timezone:3:tzset:3:
+☆:LDP man-pages:3.68=>3.75:2008/07/14:tmpfile:3:2014/06/08:o:ysato@h4.dion.ne.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2014/02/27:tmpnam:3:2014/06/08:o:amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/02/27:tmpnam_r:3:tmpnam:3:
+☆:LDP man-pages:3.68=>3.75:2013/12/23:toascii:3:2014/06/08::nishi@rpts.cl.nec.co.jp:HIROFUMI Nishizuka:
+＠:LDP man-pages:3.75:2014/03/18:tolower:3:toupper:3:
+＠:LDP man-pages:3.75:2014/03/18:tolower_l:3:toupper:3:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:toupper:3:2014/06/08::rui@linux.or.jp:Ueyama Rui:
+＠:LDP man-pages:3.75:2014/03/18:toupper_l:3:toupper:3:
+☆:LDP man-pages:3.68=>3.75:2013/12/24:towctrans:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:towlower:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+＠:LDP man-pages:3.75:2014/03/18:towlower_l:3:towlower:3:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:towupper:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+＠:LDP man-pages:3.75:2014/03/18:towupper_l:3:towupper:3:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:trunc:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/06/21:truncf:3:trunc:3:
+＠:LDP man-pages:3.75:2013/06/21:truncl:3:trunc:3:
+☆:LDP man-pages:3.68=>3.75:2014/05/28:tsearch:3:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2013/06/21:ttyname:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2013/06/21:ttyname_r:3:ttyname:3:
+☆:LDP man-pages:3.68=>3.75:2013/07/22:ttyslot:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/05/28:twalk:3:tsearch:3:
+＠:LDP man-pages:3.75:2014/08/19:tzname:3:tzset:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:tzset:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/12/23:ualarm:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/05/28:ulckpwdf:3:getspnam:3:
+☆:LDP man-pages:3.68=>3.75:2008/08/06:ulimit:3:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2012/12/21:undocumented:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/12/31:ungetc:3:fgetc:3:
+☆:LDP man-pages:3.68=>3.75:2013/12/09:ungetwc:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+☆:LDP man-pages:3.68=>3.75:2008/08/29:unlocked_stdio:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/12/09:unlockpt:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/10/11:unsetenv:3:setenv:3:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:updwtmp:3:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+＠:LDP man-pages:3.75:2014/08/19:updwtmpx:3:updwtmp:3:
+×:LDP man-pages:3.75:2014/03/10:uselocale:3:::::
+☆:LDP man-pages:3.68=>3.75:2013/12/10:usleep:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:utmpname:3:getutent:3:
+＠:LDP man-pages:3.75:2014/08/19:utmpxname:3:getutent:3:
+＠:LDP man-pages:3.75:2013/12/10:va_arg:3:stdarg:3:
+＠:LDP man-pages:3.75:2013/12/10:va_copy:3:stdarg:3:
+＠:LDP man-pages:3.75:2013/12/10:va_end:3:stdarg:3:
+＠:LDP man-pages:3.75:2013/12/10:va_start:3:stdarg:3:
+＠:LDP man-pages:3.75:2013/09/02:valloc:3:posix_memalign:3:
+＠:LDP man-pages:3.75:2013/06/21:vasprintf:3:asprintf:3:
+＠:LDP man-pages:3.75:2010/09/15:vdprintf:3:dprintf:3:
+＠:LDP man-pages:3.75:2013/12/30:verr:3:err:3:
+＠:LDP man-pages:3.75:2013/12/30:verrx:3:err:3:
+＠:LDP man-pages:3.75:2014/05/28:versionsort:3:scandir:3:
+＠:LDP man-pages:3.75:2014/07/08:vfprintf:3:printf:3:
+＠:LDP man-pages:3.75:2014/01/11:vfscanf:3:scanf:3:
+＠:LDP man-pages:3.75:2014/03/19:vfwprintf:3:wprintf:3:
+＠:LDP man-pages:3.75:2014/10/02:vlimit:3:getrlimit:2:
+＠:LDP man-pages:3.75:2014/07/08:vprintf:3:printf:3:
+＠:LDP man-pages:3.75:2014/01/11:vscanf:3:scanf:3:
+＠:LDP man-pages:3.75:2014/07/08:vsnprintf:3:printf:3:
+＠:LDP man-pages:3.75:2014/07/08:vsprintf:3:printf:3:
+＠:LDP man-pages:3.75:2014/01/11:vsscanf:3:scanf:3:
+＠:LDP man-pages:3.75:2014/03/19:vswprintf:3:wprintf:3:
+＠:LDP man-pages:3.75:2012/08/17:vsyslog:3:syslog:3:
+＠:LDP man-pages:3.75:2014/05/10:vtimes:3:getrusage:2:
+＠:LDP man-pages:3.75:2013/12/30:vwarn:3:err:3:
+＠:LDP man-pages:3.75:2013/12/30:vwarnx:3:err:3:
+＠:LDP man-pages:3.75:2014/03/19:vwprintf:3:wprintf:3:
+＠:LDP man-pages:3.75:2013/12/30:warn:3:err:3:
+＠:LDP man-pages:3.75:2013/12/30:warnx:3:err:3:
+☆:LDP man-pages:3.68=>3.75:2013/12/10:wcpcpy:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/12/16:wcpncpy:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:wcrtomb:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/01/22:wcscasecmp:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2013/12/02:wcscat:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2013/12/02:wcschr:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2013/12/02:wcscmp:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2013/12/02:wcscpy:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2013/12/02:wcscspn:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2013/04/19:wcsdup:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2013/11/21:wcslen:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/01/22:wcsncasecmp:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2013/11/25:wcsncat:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2013/11/25:wcsncmp:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/11/25:wcsncpy:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2013/11/25:wcsnlen:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:wcsnrtombs:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/11/18:wcspbrk:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2013/11/19:wcsrchr:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:wcsrtombs:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/11/11:wcsspn:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2013/11/12:wcsstr:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2014/01/22:wcstoimax:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2013/11/18:wcstok:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:wcstombs:3:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/01/22:wcstoumax:3:wcstoimax:3:
+☆:LDP man-pages:3.68=>3.75:2014/01/22:wcswidth:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2011/09/22:wctob:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:wctomb:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+☆:LDP man-pages:3.68=>3.75:2014/01/22:wctrans:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2014/01/22:wctype:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2014/01/22:wcwidth:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/11/05:wmemchr:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2013/11/05:wmemcmp:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2013/11/11:wmemcpy:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2013/11/11:wmemmove:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+＠:LDP man-pages:3.75:2014/03/18:wmempcpy:3:mempcpy:3:
+☆:LDP man-pages:3.68=>3.75:2013/11/11:wmemset:3:2014/06/08::fujiwara@linux.or.jp:FUJIWARA Teruyoshi:
+☆:LDP man-pages:3.68=>3.75:2008/07/14:wordexp:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2008/07/14:wordfree:3:wordexp:3:
+☆:LDP man-pages:3.68=>3.75:2014/03/19:wprintf:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:xcrypt:3:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2014/08/19:xdecrypt:3:xcrypt:3:
+☆:LDP man-pages:3.68=>3.75:2007/12/30:xdr:3:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+＠:LDP man-pages:3.75:2013/09/26:xdr_accepted_reply:3:rpc:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_array:3:xdr:3:
+＠:LDP man-pages:3.75:2013/09/26:xdr_authunix_parms:3:rpc:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_bool:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_bytes:3:xdr:3:
+＠:LDP man-pages:3.75:2013/09/26:xdr_callhdr:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:xdr_callmsg:3:rpc:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_char:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_destroy:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_double:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_enum:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_float:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_free:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_getpos:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_inline:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_int:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_long:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_opaque:3:xdr:3:
+＠:LDP man-pages:3.75:2013/09/26:xdr_opaque_auth:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:xdr_pmap:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:xdr_pmaplist:3:rpc:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_pointer:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_reference:3:xdr:3:
+＠:LDP man-pages:3.75:2013/09/26:xdr_rejected_reply:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:xdr_replymsg:3:rpc:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_setpos:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_short:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_string:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_u_char:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_u_int:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_u_long:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_u_short:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_union:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_vector:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_void:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdr_wrapstring:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdrmem_create:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdrrec_create:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdrrec_endofrecord:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdrrec_eof:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdrrec_skiprecord:3:xdr:3:
+＠:LDP man-pages:3.75:2007/12/30:xdrstdio_create:3:xdr:3:
+＠:LDP man-pages:3.75:2014/08/19:xencrypt:3:xcrypt:3:
+＠:LDP man-pages:3.75:2013/09/26:xprt_register:3:rpc:3:
+＠:LDP man-pages:3.75:2013/09/26:xprt_unregister:3:rpc:3:
+☆:LDP man-pages:3.68=>3.75:2014/01/18:y0:3:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/01/18:y0f:3:y0:3:
+＠:LDP man-pages:3.75:2014/01/18:y0l:3:y0:3:
+＠:LDP man-pages:3.75:2014/01/18:y1:3:y0:3:
+＠:LDP man-pages:3.75:2014/01/18:y1f:3:y0:3:
+＠:LDP man-pages:3.75:2014/01/18:y1l:3:y0:3:
+＠:LDP man-pages:3.75:2014/01/18:yn:3:y0:3:
+＠:LDP man-pages:3.75:2014/01/18:ynf:3:y0:3:
+＠:LDP man-pages:3.75:2014/01/18:ynl:3:y0:3:
+×:LDP man-pages:3.75:2012/08/05:cciss:4:::::
+☆:LDP man-pages:3.68=>3.75:1994/10/31:console:4:2014/06/08:o:argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2012/08/05:console_codes:4:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2009/02/28:console_ioctl:4:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+×:LDP man-pages:3.75:2009/03/31:cpuid:4:::::
+☆:LDP man-pages:3.68=>3.75:2012/08/05:dsp56k:4:2014/06/08::sato@complex.eng.hokudai.ac.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2014/05/10:fd:4:2014/06/08:o:ishikawa@linux.or.jp:ISHIKAWA Mutsumi:
+☆:LDP man-pages:3.68=>3.75:2007/11/24:full:4:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:1992/12/17:hd:4:2014/06/08:o:ishikawa@linux.or.jp:ISHIKAWA Mutsumi:
+×:LDP man-pages:3.75:2012/08/05:hpsa:4:::::
+☆:LDP man-pages:3.68=>3.75:2010/09/04:initrd:4:2014/06/08:o:amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2007/10/23:intro:4:2014/06/08:o:ishikawa@linux.or.jp:ISHIKAWA Mutsumi:
+＠:LDP man-pages:3.75:1992/11/21:kmem:4:mem:4:
+☆:LDP man-pages:3.68=>3.75:1995/01/15:lp:4:2014/06/08:o:ishikawa@linux.or.jp:ISHIKAWA Mutsumi:
+☆:LDP man-pages:3.68=>3.75:1992/11/21:mem:4:2014/06/08:o:ishikawa@linux.or.jp:ISHIKAWA Mutsumi:
+☆:LDP man-pages:3.68=>3.75:1996/02/10:mouse:4:2014/06/08:o:ss236rx@ymg.urban.ne.jp:Shouichi Saito:
+☆:LDP man-pages:3.68=>3.75:2009/03/31:msr:4:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2009/02/23:null:4:2014/06/08:o:ishikawa@linux.or.jp:ISHIKAWA Mutsumi:
+＠:LDP man-pages:3.75:1992/11/21:port:4:mem:4:
+＠:LDP man-pages:3.75:2002/10/09:ptmx:4:pts:4:
+☆:LDP man-pages:3.68=>3.75:2002/10/09:pts:4:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:1992/11/21:ram:4:2014/06/08:o:ishikawa@linux.or.jp:ISHIKAWA Mutsumi:
+☆:LDP man-pages:3.68=>3.75:2013/03/15:random:4:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/02/25:rtc:4:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2012/05/03:sd:4:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/08/05:sk98lin:4:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/09/04:st:4:2014/06/08::nakano@st.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2003/04/07:tty:4:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:1992/12/19:ttyS:4:2014/06/08::ishikawa@linux.or.jp:ISHIKAWA Mutsumi:
+☆:LDP man-pages:3.68=>3.75:2013/11/12:tty_ioctl:4:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2013/03/15:urandom:4:random:4:
+☆:LDP man-pages:3.68=>3.75:2007/12/17:vcs:4:2014/06/08::sato@complex.eng.hokudai.ac.jp:Yuichi SATO:
+＠:LDP man-pages:3.75:2007/12/17:vcsa:4:vcs:4:
+☆:LDP man-pages:3.68=>3.75:2013/09/04:wavelan:4:2014/06/08::ishikawa@linux.or.jp:ISHIKAWA Mutsumi:
+＠:LDP man-pages:3.75:2009/02/23:zero:4:null:4:
+☆:LDP man-pages:3.68=>3.75:2008/06/15:acct:5:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/07/08:charmap:5:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:core:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/08/09:dir_colors:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/04/17:elf:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/01/15:filesystems:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/01/15:fs:5:filesystems:5:
+☆:LDP man-pages:3.68=>3.75:2000/08/27:ftpusers:5:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2013/02/13:gai.conf:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/10/21:group:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2003/08/23:host.conf:5:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2002/06/16:hosts:5:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2003/08/24:hosts.equiv:5:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2007/10/23:intro:5:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+＠:LDP man-pages:3.75:2014/09/21:ipc:5:svipc:7:
+☆:LDP man-pages:3.68=>3.75:1993/07/24:issue:5:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.54=>3.75:2014/06/13:locale:5:2013/03/25::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:1992/12/29:motd:5:2014/06/08::nagoya@cc.hit-u.ac.jp:Hiroaki Nagoya:
+☆:LDP man-pages:3.68=>3.75:2008/09/04:networks:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/04/16:nologin:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/02/07:nscd.conf:5:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2013/02/13:nss:5:::::
+☆:LDP man-pages:3.68=>3.75:2013/02/12:nsswitch.conf:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2012/08/05:numa_maps:5:numa:7:
+☆:LDP man-pages:3.68=>3.75:2014/02/11:passwd:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.50=>3.75:2014/09/21:proc:5:2013/03/25::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/09/21:procfs:5:proc:5:
+☆:LDP man-pages:3.68=>3.75:2012/08/05:protocols:5:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+×:LDP man-pages:3.75:2014/06/02:repertoiremap:5:::::
+☆:LDP man-pages:3.68=>3.75:2014/02/22:resolv.conf:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/02/22:resolver:5:resolv.conf:5:
+☆:LDP man-pages:3.68=>3.75:1985/09/26:rpc:5:2014/06/08::argrath@ub32.org:Kentaro Shirakata:
+☆:LDP man-pages:3.68=>3.75:1992/12/29:securetty:5:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/05/22:services:5:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro Motoki:
+☆:LDP man-pages:3.68=>3.75:2012/12/31:shells:5:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2007/09/30:slabinfo:5:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:1996/10/21:termcap:5:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2012/12/31:ttytype:5:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2012/05/04:tzfile:5:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:utmp:5:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/08/19:utmpx:5:utmp:5:
+＠:LDP man-pages:3.75:2014/08/19:wtmp:5:utmp:5:
+☆:LDP man-pages:3.68=>3.75:2007/10/23:intro:6:2014/06/08::pessi@kmc.kyoto-u.ac.jp:II Ryouta:
+☆:LDP man-pages:3.68=>3.75:2014/04/06:aio:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:armscii-8:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2008/11/25:arp:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:ascii:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/09/19:boot:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/06/13:bootparam:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.67=>3.75:2014/09/21:capabilities:7:2014/06/04::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:charsets:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2011/09/16:complex:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:0000/00/00:cp1251:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+×:LDP man-pages:3.75:0000/00/00:cp1252:7:::::
+×:LDP man-pages:3.75:2014/05/21:cpuset:7:::::
+☆:LDP man-pages:3.68=>3.75:2014/09/21:credentials:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2008/11/20:ddp:7:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:environ:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/07/08:epoll:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2014/05/21:fanotify:7:::::
+☆:LDP man-pages:3.68=>3.75:2014/03/20:feature_test_macros:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2008/12/03:fifo:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/08/05:futex:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/07/08:glibc:7:libc:7:
+☆:LDP man-pages:3.68=>3.75:2012/07/28:glob:7:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2012/08/05:hier:7:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2010/11/07:hostname:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/05/10:icmp:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.67=>3.75:2014/09/06:inotify:7:2014/06/04::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2007/10/23:intro:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.65=>3.75:2014/05/10:ip:7:2014/04/24::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:ipv6:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/10/02:iso-8859-1:7:iso_8859-1:7:
+＠:LDP man-pages:3.75:2014/10/02:iso-8859-10:7:iso_8859-10:7:
+＠:LDP man-pages:3.75:2014/10/02:iso-8859-11:7:iso_8859-11:7:
+＠:LDP man-pages:3.75:2014/10/02:iso-8859-13:7:iso_8859-13:7:
+＠:LDP man-pages:3.75:2014/10/02:iso-8859-14:7:iso_8859-14:7:
+＠:LDP man-pages:3.75:2014/10/02:iso-8859-15:7:iso_8859-15:7:
+＠:LDP man-pages:3.75:2014/10/02:iso-8859-16:7:iso_8859-16:7:
+＠:LDP man-pages:3.75:2014/10/02:iso-8859-2:7:iso_8859-2:7:
+＠:LDP man-pages:3.75:2014/10/02:iso-8859-3:7:iso_8859-3:7:
+＠:LDP man-pages:3.75:2014/10/02:iso-8859-4:7:iso_8859-4:7:
+＠:LDP man-pages:3.75:2014/10/02:iso-8859-5:7:iso_8859-5:7:
+＠:LDP man-pages:3.75:2014/10/02:iso-8859-6:7:iso_8859-6:7:
+＠:LDP man-pages:3.75:2014/10/02:iso-8859-7:7:iso_8859-7:7:
+＠:LDP man-pages:3.75:2014/10/02:iso-8859-8:7:iso_8859-8:7:
+＠:LDP man-pages:3.75:2014/10/02:iso-8859-9:7:iso_8859-9:7:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:iso_8859-1:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:iso_8859-10:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:iso_8859-11:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:iso_8859-13:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:iso_8859-14:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:iso_8859-15:7:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:iso_8859-16:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:iso_8859-2:7:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:iso_8859-3:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:iso_8859-4:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:iso_8859-5:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:iso_8859-6:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:iso_8859-7:7:2014/06/08::hanataka@abyss.rim.or.jp:HANATAKA Shinya:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:iso_8859-8:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:iso_8859-9:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/10/02:iso_8859_1:7:iso_8859-1:7:
+＠:LDP man-pages:3.75:2014/10/02:iso_8859_10:7:iso_8859-10:7:
+＠:LDP man-pages:3.75:2014/10/02:iso_8859_11:7:iso_8859-11:7:
+＠:LDP man-pages:3.75:2014/10/02:iso_8859_13:7:iso_8859-13:7:
+＠:LDP man-pages:3.75:2014/10/02:iso_8859_14:7:iso_8859-14:7:
+＠:LDP man-pages:3.75:2014/10/02:iso_8859_15:7:iso_8859-15:7:
+＠:LDP man-pages:3.75:2014/10/02:iso_8859_16:7:iso_8859-16:7:
+＠:LDP man-pages:3.75:2014/10/02:iso_8859_2:7:iso_8859-2:7:
+＠:LDP man-pages:3.75:2014/10/02:iso_8859_3:7:iso_8859-3:7:
+＠:LDP man-pages:3.75:2014/10/02:iso_8859_4:7:iso_8859-4:7:
+＠:LDP man-pages:3.75:2014/10/02:iso_8859_5:7:iso_8859-5:7:
+＠:LDP man-pages:3.75:2014/10/02:iso_8859_6:7:iso_8859-6:7:
+＠:LDP man-pages:3.75:2014/10/02:iso_8859_7:7:iso_8859-7:7:
+＠:LDP man-pages:3.75:2014/10/02:iso_8859_8:7:iso_8859-8:7:
+＠:LDP man-pages:3.75:2014/10/02:iso_8859_9:7:iso_8859-9:7:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:koi8-r:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:koi8-u:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/10/02:latin1:7:iso_8859-1:7:
+＠:LDP man-pages:3.75:2014/10/02:latin10:7:iso_8859-16:7:
+＠:LDP man-pages:3.75:2014/10/02:latin2:7:iso_8859-2:7:
+＠:LDP man-pages:3.75:2014/10/02:latin3:7:iso_8859-3:7:
+＠:LDP man-pages:3.75:2014/10/02:latin4:7:iso_8859-4:7:
+＠:LDP man-pages:3.75:2014/10/02:latin5:7:iso_8859-9:7:
+＠:LDP man-pages:3.75:2014/10/02:latin6:7:iso_8859-10:7:
+＠:LDP man-pages:3.75:2014/10/02:latin7:7:iso_8859-13:7:
+＠:LDP man-pages:3.75:2014/10/02:latin8:7:iso_8859-14:7:
+＠:LDP man-pages:3.75:2014/10/02:latin9:7:iso_8859-15:7:
+☆:LDP man-pages:3.68=>3.75:2014/07/08:libc:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.67=>3.75:2014/05/28:locale:7:2014/06/04::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2004/09/15:mailaddr:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/08/05:man:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/08/19:man-pages:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2008/08/11:math_error:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:0000/00/00:mdoc:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:0000/00/00:mdoc.samples:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/09/21:mq_overview:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2014/09/21:namespaces:7:::::
+☆:LDP man-pages:3.68=>3.75:2014/01/24:netdevice:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/03/15:netlink:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/08/05:numa:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2011/09/09:operator:7:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.65=>3.75:2014/08/19:packet:7:2014/04/27::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2009/12/05:path_resolution:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2014/09/21:pid_namespaces:7:::::
+☆:LDP man-pages:3.68=>3.75:2014/07/08:pipe:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2007/12/21:posixoptions:7:2014/06/08::ysato444@yahoo.co.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2014/05/21:pthreads:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2005/10/10:pty:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/05/10:raw:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2009/01/12:regex:7:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+×:LDP man-pages:3.75:2012/07/07:rtld-audit:7:::::
+☆:LDP man-pages:3.68=>3.75:2013/03/05:rtnetlink:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2014/10/02:sched:7:::::
+☆:LDP man-pages:3.68=>3.75:2012/05/13:sem_overview:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2010/09/10:shm_overview:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2011/09/09:sigevent:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/10/15:signal:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/07/08:socket:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2007/12/20:spufs:7:::::
+☆:LDP man-pages:3.68=>3.75:2014/01/15:standards:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2000/11/16:suffixes:7:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
+☆:LDP man-pages:3.68=>3.75:2014/09/21:svipc:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2014/04/06:symlink:7:::::
+☆:LDP man-pages:3.68=>3.75:2014/03/31:tcp:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/02/12:termio:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/10/28:time:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/10/02:tis-620:7:iso_8859-11:7:
+☆:LDP man-pages:3.68=>3.75:2013/07/31:udp:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/07/08:udplite:7:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/06/13:unicode:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/08/05:units:7:2014/06/08::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2014/10/15:unix:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2014/03/18:uri:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/03/18:url:7:uri:7:
+＠:LDP man-pages:3.75:2014/03/18:urn:7:uri:7:
+×:LDP man-pages:3.75:2014/09/21:user_namespaces:7:::::
+☆:LDP man-pages:3.68=>3.75:2014/06/13:utf-8:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/06/13:utf8:7:utf-8:7:
+×:LDP man-pages:3.75:2014/08/19:vdso:7:::::
+☆:LDP man-pages:3.68=>3.75:2012/08/05:x25:7:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+×:LDP man-pages:3.75:2014/07/08:iconvconfig:8:::::
+☆:LDP man-pages:3.68=>3.75:2007/10/23:intro:8:2014/06/08::amotoki@dd.iij4u.or.jp:Akihiro MOTOKI:
+＠:LDP man-pages:3.75:2014/10/02:ld-linux:8:ld.so:8:
+＠:LDP man-pages:3.75:2014/10/02:ld-linux.so:8:ld.so:8:
+☆:LDP man-pages:3.68=>3.75:2014/10/02:ld.so:8:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/05/10:ldconfig:8:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2012/05/10:nscd:8:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2013/02/10:sln:8:2014/06/08::amotoki@gmail.com:Akihiro MOTOKI:
+☆:LDP man-pages:3.68=>3.75:2007/05/18:tzselect:8:2014/06/08::ysato@h4.dion.ne.jp:Yuichi SATO:
+☆:LDP man-pages:3.50=>3.75:2013/02/12:zdump:8:2013/03/26::nakano@apm.seikei.ac.jp:NAKANO Takeo:
+☆:LDP man-pages:3.68=>3.75:2010/02/25:zic:8:2014/06/08::sato@complex.eng.hokudai.ac.jp:Yuichi SATO:
OSDN Git Service
