The output is unchanged, except the font changes for a punctuation mark. Signed-off-by: Bjarni Ingi Gislason <bjarniig@xxxxxxxxx> --- man2/epoll_create.2 | 2 +- man2/epoll_ctl.2 | 26 +++++++++++++------------- man2/epoll_wait.2 | 2 +- man2/eventfd.2 | 12 ++++++------ man2/execve.2 | 22 +++++++++++----------- man2/execveat.2 | 22 +++++++++++----------- 6 files changed, 43 insertions(+), 43 deletions(-) diff --git a/man2/epoll_create.2 b/man2/epoll_create.2 index 490e23e0f..d3a15afe3 100644 --- a/man2/epoll_create.2 +++ b/man2/epoll_create.2 @@ -62,7 +62,7 @@ argument is dropped, is the same as .BR epoll_create (). The following value can be included in -.IR flags +.I flags to obtain different behavior: .TP .B EPOLL_CLOEXEC diff --git a/man2/epoll_ctl.2 b/man2/epoll_ctl.2 index 6584d8b6f..bef1d6d24 100644 --- a/man2/epoll_ctl.2 +++ b/man2/epoll_ctl.2 @@ -52,7 +52,7 @@ with the internal file linked to .TP .B EPOLL_CTL_MOD Change the settings associated with -.IR fd +.I fd in the interest list to the new settings specified in .IR event . .TP @@ -197,14 +197,14 @@ are attached to the same target file using one or more of the epoll file descriptors will receive an event with .BR epoll_wait (2). The default in this scenario (when -.BR EPOLLEXCLUSIVE +.B EPOLLEXCLUSIVE is not set) is for all epoll file descriptors to receive an event. -.BR EPOLLEXCLUSIVE +.B EPOLLEXCLUSIVE is thus useful for avoiding thundering herd problems in certain scenarios. .IP If the same file descriptor is in multiple epoll instances, some with the -.BR EPOLLEXCLUSIVE +.B EPOLLEXCLUSIVE flag, and others without, then events will be provided to all epoll instances that did not specify .BR EPOLLEXCLUSIVE , @@ -215,12 +215,12 @@ The following values may be specified in conjunction with .BR EPOLLEXCLUSIVE : .BR EPOLLIN , .BR EPOLLOUT , -.BR EPOLLWAKEUP, +.BR EPOLLWAKEUP , and .BR EPOLLET . -.BR EPOLLHUP +.B EPOLLHUP and -.BR EPOLLERR +.B EPOLLERR can also be specified, but this is not required: as usual, these events are always reported if they occur, regardless of whether they are specified in @@ -305,7 +305,7 @@ in was .B EPOLL_CTL_MOD and -.IR events +.I events included .BR EPOLLEXCLUSIVE . .TP @@ -314,15 +314,15 @@ included was .B EPOLL_CTL_MOD and the -.BR EPOLLEXCLUSIVE +.B EPOLLEXCLUSIVE flag has previously been applied to this .IR epfd ",\ " fd pair. .TP .B EINVAL -.BR EPOLLEXCLUSIVE +.B EPOLLEXCLUSIVE was specified in -.IR event +.I event and .I fd refers to an epoll instance. @@ -401,14 +401,14 @@ If is specified in .IR flags , but the caller does not have the -.BR CAP_BLOCK_SUSPEND +.B 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 +.I 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 diff --git a/man2/epoll_wait.2 b/man2/epoll_wait.2 index 2f2e4e3e6..78e8f9d0b 100644 --- a/man2/epoll_wait.2 +++ b/man2/epoll_wait.2 @@ -256,7 +256,7 @@ The raw system call has a sixth argument, .IR "size_t sigsetsize" , which specifies the size in bytes of the -.IR sigmask +.I sigmask argument. The glibc .BR epoll_pwait () diff --git a/man2/eventfd.2 b/man2/eventfd.2 index 185778ab7..6b53279d4 100644 --- a/man2/eventfd.2 +++ b/man2/eventfd.2 @@ -43,7 +43,7 @@ returns a new file descriptor that can be used to refer to the eventfd object. .PP The following values may be bitwise ORed in -.IR flags +.I flags to change the behavior of .BR eventfd (): .TP @@ -59,7 +59,7 @@ for reasons why this may be useful. .TP .BR EFD_NONBLOCK " (since Linux 2.6.27)" Set the -.BR O_NONBLOCK +.B O_NONBLOCK file status flag on the open file description (see .BR open (2)) referred to by the new file descriptor. @@ -97,19 +97,19 @@ The semantics of .BR read (2) depend on whether the eventfd counter currently has a nonzero value and whether the -.BR EFD_SEMAPHORE +.B EFD_SEMAPHORE flag was specified when creating the eventfd file descriptor: .RS .IP * 3 If -.BR EFD_SEMAPHORE +.B EFD_SEMAPHORE was not specified and the eventfd counter has a nonzero value, then a .BR read (2) returns 8 bytes containing that value, and the counter's value is reset to zero. .IP * If -.BR EFD_SEMAPHORE +.B EFD_SEMAPHORE was specified and the eventfd counter has a nonzero value, then a .BR read (2) returns 8 bytes containing the value 1, @@ -319,7 +319,7 @@ or .PP The current value of an eventfd counter can be viewed via the entry for the corresponding file descriptor in the process's -.IR /proc/[pid]/fdinfo +.I /proc/[pid]/fdinfo directory. See .BR proc (5) diff --git a/man2/execve.2 b/man2/execve.2 index 788e62d03..4ff0a5341 100644 --- a/man2/execve.2 +++ b/man2/execve.2 @@ -390,7 +390,7 @@ ensures that the new program always has some stack space.) Since Linux 2.6.25, the kernel places a floor of 32 pages on this size limit, so that, even when -.BR RLIMIT_STACK +.B RLIMIT_STACK is set very low, applications are guaranteed to have at least as much argument and environment space as was provided by Linux 2.6.23 and earlier. @@ -435,7 +435,7 @@ The filesystem is mounted 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 +.B RLIMIT_NPROC resource limit (see .BR setrlimit (2)). For a more detailed explanation of this error, see NOTES. @@ -587,7 +587,7 @@ POSIX.1 says that values returned by .BR sysconf (3) should be invariant over the lifetime of a process. However, since Linux 2.6.23, if the -.BR RLIMIT_STACK +.B RLIMIT_STACK resource limit changes, then the value reported by .B _SC_ARG_MAX will also change, @@ -605,7 +605,7 @@ failure may occur past the point of no return: the original executable image has been torn down, but the new image could not be completely built. In such cases, the kernel kills the process with a -.BR SIGKILL +.B SIGKILL signal. .\" .SS Interpreter scripts @@ -643,13 +643,13 @@ Linux ignores the set-user-ID and set-group-ID bits on scripts. .\" 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 +.B EAGAIN error that can occur (since Linux 3.1) when calling .BR execve () is as follows. .PP The -.BR EAGAIN +.B EAGAIN error can occur when a .I preceding call to @@ -659,7 +659,7 @@ 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 +.B 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 @@ -682,17 +682,17 @@ 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 +.B RLIMIT_NPROC resource limit has been exceeded. If the -.BR PF_NPROC_EXCEEDED +.B 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 +.B RLIMIT_NPROC resource limit is still enforced for the common privileged daemon workflow\(emnamely, .BR fork (2) @@ -711,7 +711,7 @@ call and the call), then the .BR execve () call succeeds and the kernel clears the -.BR PF_NPROC_EXCEEDED +.B PF_NPROC_EXCEEDED process flag. The flag is also cleared if a subsequent call to .BR fork (2) diff --git a/man2/execveat.2 b/man2/execveat.2 index 7c31d8f17..a87add5d7 100644 --- a/man2/execveat.2 +++ b/man2/execveat.2 @@ -77,22 +77,22 @@ is ignored. If .I pathname is an empty string and the -.BR AT_EMPTY_PATH +.B AT_EMPTY_PATH flag is specified, then the file descriptor .I dirfd specifies the file to be executed (i.e., -.IR dirfd +.I dirfd refers to an executable file, rather than a directory). .PP The .I flags argument is a bit mask that can include zero or more of the following flags: .TP -.BR AT_EMPTY_PATH +.B AT_EMPTY_PATH If .I pathname is an empty string, operate on the file referred to by -.IR dirfd +.I dirfd (which may have been obtained using the .BR open (2) .B O_PATH @@ -131,7 +131,7 @@ Invalid flag specified in .B ELOOP .I flags includes -.BR AT_SYMLINK_NOFOLLOW +.B AT_SYMLINK_NOFOLLOW and the file identified by .I dirfd and a non-NULL @@ -178,25 +178,25 @@ to be implemented on systems that do not have the filesystem mounted. .PP When asked to execute a script file, the -.IR argv[0] +.I argv[0] that is passed to the script interpreter is a string of the form -.IR /dev/fd/N +.I /dev/fd/N or .IR /dev/fd/N/P , where .I N is the number of the file descriptor passed via the -.IR dirfd +.I dirfd argument. A string of the first form occurs when -.BR AT_EMPTY_PATH +.B AT_EMPTY_PATH is employed. A string of the second form occurs when the script is specified via both -.IR dirfd +.I dirfd and .IR pathname ; in this case, -.IR P +.I P is the value given in .IR pathname . .PP -- 2.19.2 -- Bjarni I. Gislason
