1) A one-font macro is used for one argument. 2) Remove quotation marks from an argument of an one-font macro. The output is unchanged. Signed-off-by: Bjarni Ingi Gislason <bjarniig@xxxxxxxxx> --- man2/cacheflush.2 | 4 +-- man2/capget.2 | 4 +-- man2/chmod.2 | 4 +-- man2/chown.2 | 16 ++++++------ man2/clock_nanosleep.2 | 8 +++--- man2/clone.2 | 56 +++++++++++++++++++++--------------------- man2/connect.2 | 4 +-- man2/copy_file_range.2 | 4 +-- 8 files changed, 50 insertions(+), 50 deletions(-) diff --git a/man2/cacheflush.2 b/man2/cacheflush.2 index aba625721..625e6f7d6 100644 --- a/man2/cacheflush.2 +++ b/man2/cacheflush.2 @@ -71,7 +71,7 @@ is not one of .BR ICACHE , .BR DCACHE , or -.BR BCACHE +.B BCACHE (but see BUGS). .SH CONFORMING TO Historically, this system call was available on all MIPS UNIX variants @@ -95,7 +95,7 @@ arguments, making this function fairly expensive. Therefore, the whole cache is always flushed. .PP This function always behaves as if -.BR BCACHE +.B BCACHE has been passed for the .I cache argument and does not do any error checking on the diff --git a/man2/capget.2 b/man2/capget.2 index 798b00814..155070856 100644 --- a/man2/capget.2 +++ b/man2/capget.2 @@ -108,7 +108,7 @@ Kernels prior to 2.6.25 prefer Linux 2.6.25 added 64-bit capability sets, with version .BR _LINUX_CAPABILITY_VERSION_2 . There was, however, an API glitch, and Linux 2.6.26 added -.BR _LINUX_CAPABILITY_VERSION_3 +.B _LINUX_CAPABILITY_VERSION_3 to fix the problem. .PP Note that 64-bit capabilities use @@ -146,7 +146,7 @@ are 0 or, equivalently, the value returned by On older kernels that do not provide VFS capabilities support .BR capset () can, if the caller has the -.BR CAP_SETPCAP +.B CAP_SETPCAP capability, be used to change not only the caller's own capabilities, but also the capabilities of other threads. The call operates on the capabilities of the thread specified by the diff --git a/man2/chmod.2 b/man2/chmod.2 index 078301f90..fa9fee176 100644 --- a/man2/chmod.2 +++ b/man2/chmod.2 @@ -373,9 +373,9 @@ When .I pathname is a relative pathname, glibc constructs a pathname based on the symbolic link in -.IR /proc/self/fd +.I /proc/self/fd that corresponds to the -.IR dirfd +.I dirfd argument. .SH SEE ALSO .BR chmod (1), diff --git a/man2/chown.2 b/man2/chown.2 index 50db789ac..6bda47876 100644 --- a/man2/chown.2 +++ b/man2/chown.2 @@ -189,7 +189,7 @@ argument is a bit mask created by ORing together 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 @@ -364,25 +364,25 @@ then the group of a new file is made the same as that of the parent directory. .IP * If the filesystem is mounted with -.BR "\-o\ nogrpid" +.B \-o\ nogrpid and the set-group-ID bit is disabled on the parent directory, then the group of a new file is made the same as the process's filesystem GID. .IP * If the filesystem is mounted with -.BR "\-o\ nogrpid" +.B \-o\ nogrpid and the set-group-ID bit is enabled on the parent directory, then the group of a new file is made the same as that of the parent directory. .PP As at Linux 4.12, the -.BR "\-o\ grpid" +.B \-o\ grpid and -.BR "\-o\ nogrpid" +.B \-o\ nogrpid mount options are supported by ext2, ext3, ext4, and XFS. Filesystems that don't support these mount options follow the -.BR "\-o\ nogrpid" +.B \-o\ nogrpid rules. .SS Glibc notes On older kernels where @@ -395,9 +395,9 @@ When .I pathname is a relative pathname, glibc constructs a pathname based on the symbolic link in -.IR /proc/self/fd +.I /proc/self/fd that corresponds to the -.IR dirfd +.I dirfd argument. .SS NFS The diff --git a/man2/clock_nanosleep.2 b/man2/clock_nanosleep.2 index 4c7393d40..bca9f3d15 100644 --- a/man2/clock_nanosleep.2 +++ b/man2/clock_nanosleep.2 @@ -78,16 +78,16 @@ argument specifies the clock against which the sleep interval is to be measured. This argument can have one of the following values: .TP 17 -.BR CLOCK_REALTIME +.B CLOCK_REALTIME A settable system-wide real-time clock. .TP -.BR CLOCK_MONOTONIC +.B CLOCK_MONOTONIC A nonsettable, monotonically increasing clock that measures time since some unspecified point in the past that does not change after system startup. .\" On Linux this clock measures time since boot. .TP -.BR CLOCK_PROCESS_CPUTIME_ID +.B CLOCK_PROCESS_CPUTIME_ID A settable per-process clock that measures CPU time consumed by all threads in the process. .\" There is some trickery between glibc and the kernel @@ -129,7 +129,7 @@ returns immediately without suspending the calling thread. .BR clock_nanosleep () suspends the execution of the calling thread until either at least the time specified by -.IR request +.I request has elapsed, or a signal is delivered that causes a signal handler to be called or that terminates the process. diff --git a/man2/clone.2 b/man2/clone.2 index 7c55d897d..5e4b08348 100644 --- a/man2/clone.2 +++ b/man2/clone.2 @@ -247,7 +247,7 @@ they will be allowed to interleave their disk access. If several threads are doing I/O on behalf of the same process .RB ( aio_read (3), for instance), they should employ -.BR CLONE_IO +.B CLONE_IO to get better I/O performance. .\" with CFQ and AS. .IP @@ -407,11 +407,11 @@ Only a privileged process can employ .BR CLONE_NEWPID . This flag can't be specified in conjunction with -.BR CLONE_THREAD +.B CLONE_THREAD or .BR CLONE_PARENT . .TP -.BR CLONE_NEWUSER +.B CLONE_NEWUSER (This flag first became meaningful for .BR clone () in Linux 2.6.23, @@ -429,7 +429,7 @@ If this flag is not set, then (as with the process is created in the same user namespace as the calling process. .IP Before Linux 3.8, use of -.BR CLONE_NEWUSER +.B CLONE_NEWUSER required that the caller have three capabilities: .BR CAP_SYS_ADMIN , .BR CAP_SETUID , @@ -440,7 +440,7 @@ Starting with Linux 3.8, no privileges are needed to create a user namespace. .IP This flag can't be specified in conjunction with -.BR CLONE_THREAD +.B CLONE_THREAD or .BR CLONE_PARENT . For security reasons, @@ -449,7 +449,7 @@ For security reasons, .\" 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 +.B CLONE_NEWUSER cannot be specified in conjunction with .BR CLONE_FS . .IP @@ -551,7 +551,7 @@ and the resulting effect is architecture dependent. On x86, .I newtls is interpreted as a -.IR "struct user_desc\ *" +.I struct user_desc\ * (see .BR set_thread_area (2)). On x86-64 it is the new value to be set for the %fs base register @@ -617,7 +617,7 @@ altogether in Linux 2.6.38. Since then, the kernel silently ignores it without error. .\" glibc 2.8 removed this defn from bits/sched.h Starting with Linux 4.6, the same bit was reused for the -.BR CLONE_NEWCGROUP +.B CLONE_NEWCGROUP flag. .TP .BR CLONE_SYSVSEM " (since Linux 2.5.10)" @@ -722,9 +722,9 @@ if is specified (and note that, since Linux 2.6.0, .\" Precisely: Linux 2.6.0-test6 -.BR CLONE_SIGHAND +.B CLONE_SIGHAND also requires -.BR CLONE_VM +.B CLONE_VM to be included). .IP Signal dispositions and actions are process-wide: @@ -753,7 +753,7 @@ or or because the thread executed a machine language instruction that triggered a hardware exception (e.g., invalid memory access triggering -.BR SIGSEGV +.B SIGSEGV or a floating-point exception triggering .BR SIGFPE ). .IP @@ -863,7 +863,7 @@ option should not be specified. (If the child .I shares the parent's memory because of the use of the -.BR CLONE_VM +.B CLONE_VM flag, then no copy-on-write duplication occurs and chaos is likely to result.) .PP @@ -1049,13 +1049,13 @@ were specified in .TP .B EINVAL One (or both) of -.BR CLONE_NEWPID +.B CLONE_NEWPID or -.BR CLONE_NEWUSER +.B CLONE_NEWUSER and one (or both) of -.BR CLONE_THREAD +.B CLONE_THREAD or -.BR CLONE_PARENT +.B CLONE_PARENT were specified in .IR flags . .TP @@ -1063,23 +1063,23 @@ were specified in Returned by the glibc .BR clone () wrapper function when -.IR fn +.I fn or -.IR child_stack +.I child_stack is specified as NULL. .TP .B EINVAL -.BR CLONE_NEWIPC +.B CLONE_NEWIPC was specified in .IR flags , but the kernel was not configured with the .B CONFIG_SYSVIPC and -.BR CONFIG_IPC_NS +.B CONFIG_IPC_NS options. .TP .B EINVAL -.BR CLONE_NEWNET +.B CLONE_NEWNET was specified in .IR flags , but the kernel was not configured with the @@ -1087,7 +1087,7 @@ but the kernel was not configured with the option. .TP .B EINVAL -.BR CLONE_NEWPID +.B CLONE_NEWPID was specified in .IR flags , but the kernel was not configured with the @@ -1095,7 +1095,7 @@ but the kernel was not configured with the option. .TP .B EINVAL -.BR CLONE_NEWUSER +.B CLONE_NEWUSER was specified in .IR flags , but the kernel was not configured with the @@ -1103,7 +1103,7 @@ but the kernel was not configured with the option. .TP .B EINVAL -.BR CLONE_NEWUTS +.B CLONE_NEWUTS was specified in .IR flags , but the kernel was not configured with the @@ -1147,7 +1147,7 @@ One of the values in .I flags specified the creation of a new user namespace, but doing so would have caused the limit defined by the corresponding file in -.IR /proc/sys/user +.I /proc/sys/user to be exceeded. For further details, see .BR namespaces (7). @@ -1159,7 +1159,7 @@ For further details, see .BR CLONE_NEWNS , .BR CLONE_NEWPID , or -.BR CLONE_NEWUTS +.B CLONE_NEWUTS was specified by an unprivileged process (process without \fBCAP_SYS_ADMIN\fP). .TP .B EPERM @@ -1168,7 +1168,7 @@ was specified by a process other than process 0. (This error occurs only on Linux 2.5.15 and earlier.) .TP .B EPERM -.BR CLONE_NEWUSER +.B CLONE_NEWUSER was specified in .IR flags , but either the effective user ID or the effective group ID of the caller @@ -1196,7 +1196,7 @@ was specified in .IR flags , and the limit on the number of nested user namespaces would be exceeded. See the discussion of the -.BR ENOSPC +.B ENOSPC error above. .\" .SH VERSIONS .\" There is no entry for diff --git a/man2/connect.2 b/man2/connect.2 index 62bf8afbc..cf73908e9 100644 --- a/man2/connect.2 +++ b/man2/connect.2 @@ -122,7 +122,7 @@ dissolve the association by connecting to an address with the member of .I sockaddr set to -.BR AF_UNSPEC +.B AF_UNSPEC (supported on Linux since kernel 2.2). .SH RETURN VALUE If the connection or binding succeeds, zero is returned. @@ -191,7 +191,7 @@ The socket structure address is outside the user's address space. .B EINPROGRESS The socket is nonblocking and the connection cannot be completed immediately. (UNIX domain sockets failed with -.BR EAGAIN +.B EAGAIN instead.) It is possible to .BR select (2) diff --git a/man2/copy_file_range.2 b/man2/copy_file_range.2 index 9bb1813ee..26a3d45a2 100644 --- a/man2/copy_file_range.2 +++ b/man2/copy_file_range.2 @@ -154,9 +154,9 @@ Users may benefit from calling .BR copy_file_range () in a loop, and using the .BR lseek (2) -.BR SEEK_DATA +.B SEEK_DATA and -.BR SEEK_HOLE +.B SEEK_HOLE operations to find the locations of data segments. .PP .BR copy_file_range () -- 2.19.2 -- Bjarni I. Gislason
