The output is unchanged, except for a font change for a punctuation mark (getrandom.2). Signed-off-by: Bjarni Ingi Gislason <bjarniig@xxxxxxxxx> --- man2/get_mempolicy.2 | 2 +- man2/get_robust_list.2 | 10 +++++----- man2/getdents.2 | 2 +- man2/getgroups.2 | 6 +++--- man2/gethostname.2 | 2 +- man2/getitimer.2 | 20 ++++++++++---------- man2/getpid.2 | 4 ++-- man2/getpriority.2 | 2 +- man2/getrandom.2 | 28 ++++++++++++++-------------- man2/getrlimit.2 | 20 ++++++++++---------- man2/getrusage.2 | 2 +- man2/getsockopt.2 | 2 +- man2/gettid.2 | 4 ++-- 13 files changed, 52 insertions(+), 52 deletions(-) diff --git a/man2/get_mempolicy.2 b/man2/get_mempolicy.2 index 1ee68933b..eafc3801e 100644 --- a/man2/get_mempolicy.2 +++ b/man2/get_mempolicy.2 @@ -73,7 +73,7 @@ must be specified as NULL. If .I flags specifies -.BR MPOL_F_MEMS_ALLOWED +.B MPOL_F_MEMS_ALLOWED (available since Linux 2.6.24), the .I mode argument is ignored and the set of nodes (memories) that the diff --git a/man2/get_robust_list.2 b/man2/get_robust_list.2 index a553f10c8..3a33f222c 100644 --- a/man2/get_robust_list.2 +++ b/man2/get_robust_list.2 @@ -58,10 +58,10 @@ accidentally fails to unlock a futex before terminating or calling another thread that is waiting on that futex is notified that the former owner of the futex has died. This notification consists of two pieces: the -.BR FUTEX_OWNER_DIED +.B FUTEX_OWNER_DIED bit is set in the futex word, and the kernel performs a .BR futex (2) -.BR FUTEX_WAKE +.B FUTEX_WAKE operation on one of the threads waiting on the futex. .PP The @@ -124,7 +124,7 @@ The calling process does not have permission to see the robust futex list of the thread with the thread ID .IR pid , and does not have the -.BR CAP_SYS_PTRACE +.B CAP_SYS_PTRACE capability. .TP .B ESRCH @@ -165,8 +165,8 @@ and .BR futex (2), .BR pthread_mutexattr_setrobust (3) .PP -.IR Documentation/robust-futexes.txt +.I Documentation/robust-futexes.txt and -.IR Documentation/robust-futex-ABI.txt +.I Documentation/robust-futex-ABI.txt in the Linux kernel source tree .\" http://lwn.net/Articles/172149/ diff --git a/man2/getdents.2 b/man2/getdents.2 index 30bbf9a74..6fb3c855b 100644 --- a/man2/getdents.2 +++ b/man2/getdents.2 @@ -127,7 +127,7 @@ The .I d_type field is implemented since Linux 2.6.4. It occupies a space that was previously a zero-filled padding byte in the -.IR linux_dirent +.I linux_dirent structure. Thus, on kernels up to and including 2.6.3, attempting to access this field always provides the value 0 diff --git a/man2/getgroups.2 b/man2/getgroups.2 index 427be88a7..285986653 100644 --- a/man2/getgroups.2 +++ b/man2/getgroups.2 @@ -86,7 +86,7 @@ to be used in a further call to .BR setgroups () sets the supplementary group IDs for the calling process. Appropriate privileges are required (see the description of the -.BR EPERM +.B EPERM error, below). The .I size @@ -142,7 +142,7 @@ Out of memory. .B EPERM The calling process has insufficient privilege (the caller does not have the -.BR CAP_SETGID +.B CAP_SETGID capability in the user namespace in which it resides). .TP .BR EPERM " (since Linux 3.19)" @@ -150,7 +150,7 @@ The use of .BR setgroups () is denied in this user namespace. See the description of -.IR /proc/[pid]/setgroups +.I /proc/[pid]/setgroups in .BR user_namespaces (7). .SH CONFORMING TO diff --git a/man2/gethostname.2 b/man2/gethostname.2 index 4659337cc..12e1d8da7 100644 --- a/man2/gethostname.2 +++ b/man2/gethostname.2 @@ -118,7 +118,7 @@ is larger than the maximum allowed size. .I len is smaller than the actual size. (Before version 2.1, glibc uses -.BR EINVAL +.B EINVAL for this case.) .TP .B EPERM diff --git a/man2/getitimer.2 b/man2/getitimer.2 index baa02f3be..e5415eea8 100644 --- a/man2/getitimer.2 +++ b/man2/getitimer.2 @@ -30,7 +30,7 @@ and the timer is reset to the specified interval (if the interval is nonzero). .PP Three types of timers\(emspecified via the -.IR which +.I which argument\(emare provided, each of which counts against a different clock and generates a different signal on timer expiration: @@ -83,26 +83,26 @@ struct timeval { The function .BR getitimer () places the current value of the timer specified by -.IR which +.I which in the buffer pointed to by .IR curr_value . .PP The -.IR it_value +.I it_value substructure is populated with the amount of time remaining until the next expiration of the specified timer. This value changes as the timer counts down, and will be reset to -.IR it_interval +.I it_interval when the timer expires. If both fields of -.IR it_value +.I it_value are zero, then this timer is currently disarmed (inactive). .PP The -.IR it_interval +.I it_interval substructure is populated with the timer interval. If both fields of -.IR it_interval +.I it_interval are zero, then this is a single-shot timer (i.e., it expires just once). .SS setitimer() The function @@ -119,15 +119,15 @@ the buffer it points to is used to return the previous value of the timer .BR getitimer ()). .PP If either field in -.IR new_value.it_value +.I new_value.it_value is nonzero, then the timer is armed to initially expire at the specified time. If both fields in -.IR new_value.it_value +.I new_value.it_value are zero, then the timer is disarmed. .PP The -.IR new_value.it_interval +.I new_value.it_interval field specifies the new interval for the timer; if both of its subfields are zero, the timer is single-shot. .SH RETURN VALUE diff --git a/man2/getpid.2 b/man2/getpid.2 index cddde079c..7ce136472 100644 --- a/man2/getpid.2 +++ b/man2/getpid.2 @@ -48,7 +48,7 @@ the ID of the process to which this process has been reparented (either .BR init (1) or a "subreaper" process defined via the .BR prctl (2) -.BR PR_SET_CHILD_SUBREAPER +.B PR_SET_CHILD_SUBREAPER operation). .SH ERRORS These functions are always successful. @@ -68,7 +68,7 @@ which is unique for each thread. For further details, see .BR gettid (2) and the discussion of the -.BR CLONE_THREAD +.B CLONE_THREAD flag in .BR clone (2). .\" diff --git a/man2/getpriority.2 b/man2/getpriority.2 index 2134cf054..6def889cc 100644 --- a/man2/getpriority.2 +++ b/man2/getpriority.2 @@ -113,7 +113,7 @@ Traditionally, only a privileged process could lower the nice value (i.e., set a higher priority). However, since Linux 2.6.12, an unprivileged process can decrease the nice value of a target process that has a suitable -.BR RLIMIT_NICE +.B RLIMIT_NICE soft limit; see .BR getrlimit (2) for details. diff --git a/man2/getrandom.2 b/man2/getrandom.2 index f8377cbc4..7d2f4a57f 100644 --- a/man2/getrandom.2 +++ b/man2/getrandom.2 @@ -47,7 +47,7 @@ By default, draws entropy from the .I urandom source (i.e., the same source as the -.IR /dev/urandom +.I /dev/urandom device). This behavior can be changed via the .I flags @@ -82,7 +82,7 @@ If this bit is set, then random bytes are drawn from the .I random source (i.e., the same source as the -.IR /dev/random +.I /dev/random device) instead of the .I urandom @@ -104,12 +104,12 @@ argument. .TP .B GRND_NONBLOCK By default, when reading from the -.IR random +.I random source, .BR getrandom () blocks if no random bytes are available, and when reading from the -.IR urandom +.I urandom source, it blocks if the entropy pool has not yet been initialized. If the .B GRND_NONBLOCK @@ -127,11 +127,11 @@ returns the number of bytes that were copied to the buffer This may be less than the number of bytes requested via .I buflen if either -.BR GRND_RANDOM +.B GRND_RANDOM was specified in -.IR flags +.I flags and insufficient entropy was present in the -.IR random +.I random source or the system call was interrupted by a signal. .PP On error, \-1 is returned, and @@ -181,7 +181,7 @@ can be used to obtain randomness, see .BR random (7). .PP Unlike -.IR /dev/random +.I /dev/random and .IR /dev/urandom , .BR getrandom () @@ -201,7 +201,7 @@ that was opened by a library. As of Linux 3.19 the following limits apply: .IP * 3 When reading from the -.IR urandom +.I urandom source, a maximum of 33554431 bytes is returned by a single call to .BR getrandom () on systems where @@ -209,7 +209,7 @@ on systems where has a size of 32 bits. .IP * When reading from the -.IR random +.I random source, a maximum of 512 bytes is returned. .SS Interruption by a signal handler When reading from the @@ -220,7 +220,7 @@ is not set), .BR getrandom () will block until the entropy pool has been initialized (unless the -.BR GRND_NONBLOCK +.B GRND_NONBLOCK flag was specified). If a request is made to read a large number of bytes (more than 256), .BR getrandom () @@ -235,7 +235,7 @@ is set), .BR getrandom () will block until some random bytes become available (unless the -.BR GRND_NONBLOCK +.B GRND_NONBLOCK flag was specified). .PP The behavior when a call to @@ -254,7 +254,7 @@ and the request size is large .RI ( buflen "\ >\ 256)," the call either succeeds, returning a partially filled buffer, or fails with the error -.BR EINTR. +.BR EINTR . If the entropy pool has been initialized and the request size is small .RI ( buflen "\ <=\ 256)," then @@ -264,7 +264,7 @@ will not fail with Instead, it will return all of the bytes that have been requested. .PP When reading from the -.IR random +.I random source, blocking requests of any size can be interrupted by a signal handler (the call fails with the error .BR EINTR ). diff --git a/man2/getrlimit.2 b/man2/getrlimit.2 index f488af488..fea76d433 100644 --- a/man2/getrlimit.2 +++ b/man2/getrlimit.2 @@ -335,7 +335,7 @@ on BSD.) Since Linux 4.5, this limit also defines the maximum number of file descriptors that an unprivileged process (one without the -.BR CAP_SYS_RESOURCE +.B CAP_SYS_RESOURCE capability) may have "in flight" to other processes, by being passed across UNIX domain sockets. This limit applies to the @@ -468,14 +468,14 @@ and .BR getrlimit (). .PP If the -.IR new_limit +.I new_limit argument is a not NULL, then the .I rlimit structure to which it points is used to set new values for the soft and hard limits for .IR resource . If the -.IR old_limit +.I old_limit argument is a not NULL, then a successful call to .BR prlimit () places the previous soft and hard limits for @@ -536,7 +536,7 @@ capability is required to do this. The caller tried to increase the hard .B RLIMIT_NOFILE limit above the maximum defined by -.IR /proc/sys/fs/nr_open +.I /proc/sys/fs/nr_open (see .BR proc (5)) .TP @@ -608,7 +608,7 @@ current consumption of that resource will succeed its consumption of the resource). .PP One can set the resource limits of the shell using the built-in -.IR ulimit +.I ulimit command .RI ( limit in @@ -684,7 +684,7 @@ Since Linux 2.6.12, .\" Subject: [PATCH 7/7] make RLIMIT_CPU/SIGXCPU per-process .\" Date: 2005-01-23 23:27:46 GMT if a process reaches its soft -.BR RLIMIT_CPU +.B RLIMIT_CPU limit and has a handler installed for .BR SIGXCPU , then, in addition to invoking the signal handler, @@ -695,13 +695,13 @@ at which point the process is killed. Other implementations .\" Tested Solaris 10, FreeBSD 9, OpenBSD 5.0 do not change the -.BR RLIMIT_CPU +.B RLIMIT_CPU 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 The Linux-specific -.BR RLIMIT_RTTIME +.B RLIMIT_RTTIME limit exhibits the same behavior when the soft limit is encountered. .PP Kernels before 2.4.22 did not diagnose the error @@ -724,7 +724,7 @@ The glibc and .BR setrlimit () wrapper functions use a 64-bit -.IR rlim_t +.I rlim_t data type, even on 32-bit platforms. However, the .I rlim_t @@ -746,7 +746,7 @@ 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 +.B off_t (assuming a program compiled with .IR _FILE_OFFSET_BITS=64 ). .PP diff --git a/man2/getrusage.2 b/man2/getrusage.2 index 784848abe..a8e8f89c3 100644 --- a/man2/getrusage.2 +++ b/man2/getrusage.2 @@ -260,7 +260,7 @@ All new applications should be written using .BR getrusage (). .PP See also the description of -.IR /proc/[pid]/stat +.I /proc/[pid]/stat in .BR proc (5). .SH SEE ALSO diff --git a/man2/getsockopt.2 b/man2/getsockopt.2 index b3630099d..15e20aab1 100644 --- a/man2/getsockopt.2 +++ b/man2/getsockopt.2 @@ -158,7 +158,7 @@ is not in a valid part of the process address space. invalid in .BR setsockopt (). In some cases this error can also occur for an invalid value in -.IR optval +.I optval (e.g., for the .B IP_ADD_MEMBERSHIP option described in diff --git a/man2/gettid.2 b/man2/gettid.2 index 83fcbce1b..8747c2316 100644 --- a/man2/gettid.2 +++ b/man2/gettid.2 @@ -44,7 +44,7 @@ is equal to the process ID (PID, as returned by In a multithreaded process, all threads have the same PID, but each one has a unique TID. For further details, see the discussion of -.BR CLONE_THREAD +.B CLONE_THREAD in .BR clone (2). .SH RETURN VALUE @@ -72,7 +72,7 @@ POSIX thread ID (i.e., the opaque value returned by In a new thread group created by a .BR clone (2) call that does not specify the -.BR CLONE_THREAD +.B CLONE_THREAD flag (or, equivalently, a new process created by .BR fork (2)), the new process is a thread group leader, -- 2.19.2 -- Bjarni I. Gislason
