diff options
| author | Michael Kerrisk <mtk.manpages@gmail.com> | 2017-08-18 21:37:55 +0200 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2017-08-19 13:47:26 +0200 |
| commit | e646a1bad9fc82df38d58dddcf09ce537a80f041 (patch) | |
| tree | b64181694bc12dbc18764bd44dd1f98c5305d7cd /man7 | |
| parent | b76974c1ec51463d46033bd653a806ddca8c6eb1 (diff) | |
| download | man-pages-e646a1bad9fc82df38d58dddcf09ce537a80f041.tar.gz | |
ioctl_console.2, ioctl_getfsmap.2, ioctl_iflags.2, ioctl_list.2, ioctl_ns.2, kcmp.2, kexec_load.2, keyctl.2, link.2, mmap.2, modify_ldt.2, msgctl.2, poll.2, query_module.2, quotactl.2, recv.2, recvmmsg.2, sched_setscheduler.2, seccomp.2, select.2, semctl.2, semop.2, send.2, set_thread_area.2, setns.2, shmctl.2, shmget.2, sigaction.2, sysinfo.2, timer_create.2, timerfd_create.2, uname.2, unshare.2, userfaultfd.2, ustat.2, utimensat.2, vmsplice.2, wait.2, adjtime.3, backtrace.3, bswap.3, btree.3, clock_getcpuclockid.3, confstr.3, dbopen.3, dl_iterate_phdr.3, dlinfo.3, duplocale.3, encrypt.3, end.3, endian.3, err.3, errno.3, fmemopen.3, fopencookie.3, frexp.3, fts.3, ftw.3, getaddrinfo.3, getaddrinfo_a.3, getcontext.3, getgrouplist.3, getifaddrs.3, getipnodebyname.3, getnameinfo.3, getopt.3, getprotoent_r.3, getpwent_r.3, getrpcent.3, getservent_r.3, getttyent.3, getumask.3, glob.3, gnu_get_libc_version.3, hash.3, hsearch.3, inet.3, inet_pton.3, insque.3, isalpha.3, makecontext.3, mallopt.3, mbstowcs.3, mcheck.3, memchr.3, mq_getattr.3, mq_open.3, mtrace.3, newlocale.3, ntp_gettime.3, offsetof.3, posix_openpt.3, printf.3, pthread_setname_np.3, pthread_setschedparam.3, rpc.3, scanf.3, sched_getcpu.3, sem_wait.3, setaliasent.3, sigqueue.3, sigvec.3, stdarg.3, strcat.3, strcpy.3, strftime.3, strtol.3, toupper.3, ttyslot.3, fuse.4, loop.4, st.4, elf.5, cgroup_namespaces.7, cgroups.7, feature_test_macros.7, inode.7, inotify.7, keyrings.7, man-pages.7, math_error.7, mount_namespaces.7, mq_overview.7, pthreads.7, sched.7, session-keyring.7, udplite.7, unix.7, vdso.7: Use consistent markup for code snippets
The preferred form is
.PP/.IP
.in +4n
.EX
<code>
.EE
.in
.PP/.IP
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Diffstat (limited to 'man7')
| -rw-r--r-- | man7/cgroup_namespaces.7 | 4 | ||||
| -rw-r--r-- | man7/cgroups.7 | 16 | ||||
| -rw-r--r-- | man7/feature_test_macros.7 | 4 | ||||
| -rw-r--r-- | man7/inode.7 | 8 | ||||
| -rw-r--r-- | man7/inotify.7 | 4 | ||||
| -rw-r--r-- | man7/keyrings.7 | 6 | ||||
| -rw-r--r-- | man7/man-pages.7 | 12 | ||||
| -rw-r--r-- | man7/math_error.7 | 24 | ||||
| -rw-r--r-- | man7/mount_namespaces.7 | 114 | ||||
| -rw-r--r-- | man7/mq_overview.7 | 16 | ||||
| -rw-r--r-- | man7/pthreads.7 | 26 | ||||
| -rw-r--r-- | man7/sched.7 | 12 | ||||
| -rw-r--r-- | man7/session-keyring.7 | 8 | ||||
| -rw-r--r-- | man7/udplite.7 | 4 | ||||
| -rw-r--r-- | man7/unix.7 | 6 | ||||
| -rw-r--r-- | man7/vdso.7 | 4 |
16 files changed, 134 insertions, 134 deletions
diff --git a/man7/cgroup_namespaces.7 b/man7/cgroup_namespaces.7 index a3ff0a4ca4..9a416d63d9 100644 --- a/man7/cgroup_namespaces.7 +++ b/man7/cgroup_namespaces.7 @@ -72,16 +72,16 @@ First, (as superuser) we create a child cgroup in the hierarchy, and put the shell into that cgroup: .PP .EX -.nf .in +4n +.nf # \fBmkdir \-p /sys/fs/cgroup/freezer/sub\fP # \fBecho $$\fP # Show PID of this shell 30655 # \fBsh \-c \(aqecho 30655 > /sys/fs/cgroup/freezer/sub/cgroup.procs\(aq\fP # \fBcat /proc/self/cgroup | grep freezer\fP 7:freezer:/sub -.in .fi +.in .EE .PP Next, we use diff --git a/man7/cgroups.7 b/man7/cgroups.7 index 0ad417d097..5f432cf273 100644 --- a/man7/cgroups.7 +++ b/man7/cgroups.7 @@ -171,11 +171,11 @@ Thus, one might mount the .I cpu controller as follows: .PP -.nf .in +4n +.nf mount \-t cgroup \-o cpu none /sys/fs/cgroup/cpu -.in .fi +.in .PP It is possible to comount multiple controllers against the same hierarchy. For example, here the @@ -184,11 +184,11 @@ and .IR cpuacct controllers are comounted against a single hierarchy: .PP -.nf .in +4n +.nf mount \-t cgroup \-o cpu,cpuacct none /sys/fs/cgroup/cpu,cpuacct -.in .fi +.in .PP Comounting controllers has the effect that a process is in the same cgroup for all of the comounted controllers. @@ -201,11 +201,11 @@ for another. .PP It is possible to comount all v1 controllers against the same hierarchy: .PP -.nf .in +4n +.nf mount \-t cgroup \-o all cgroup /sys/fs/cgroup -.in .fi +.in .PP (One can achieve the same result by omitting .IR "\-o all" , @@ -617,8 +617,8 @@ that are compiled into the kernel. An example of the contents of this file (reformatted for readability) is the following: .IP -.nf .in +4n +.nf #subsys_name hierarchy num_cgroups enabled cpuset 4 1 1 cpu 8 1 1 @@ -632,8 +632,8 @@ perf_event 5 1 1 net_prio 9 1 1 hugetlb 0 1 0 pids 2 1 1 -.in .fi +.in .IP The fields in this file are, from left to right: .RS diff --git a/man7/feature_test_macros.7 b/man7/feature_test_macros.7 index bcc66f0141..63860f4676 100644 --- a/man7/feature_test_macros.7 +++ b/man7/feature_test_macros.7 @@ -780,9 +780,9 @@ feature test macros are set depending on the glibc version and what feature test macros are explicitly set. The following shell session, on a system with glibc 2.10, shows some examples of what we would see: +.PP .in +4n -.nf - +.EX $ \fBcc ftm.c\fP $ \fB./a.out\fP _POSIX_SOURCE defined diff --git a/man7/inode.7 b/man7/inode.7 index 3ed33d28b0..35fdb1c4b2 100644 --- a/man7/inode.7 +++ b/man7/inode.7 @@ -255,14 +255,14 @@ S_IFIFO 0010000 FIFO .PP Thus, to test for a regular file (for example), one could write: .PP -.nf .in +4n +.nf stat(pathname, &sb); if ((sb.st_mode & S_IFMT) == S_IFREG) { /* Handle regular file */ } -.in .fi +.in .PP Because tests of the above form are common, additional macros are defined by POSIX to allow the test of the file type in @@ -294,14 +294,14 @@ socket? (Not in POSIX.1-1996.) .PP The preceding code snippet could thus be rewritten as: .PP -.nf .in +4n +.nf stat(pathname, &sb); if (S_ISREG(sb.st_mode)) { /* Handle regular file */ } -.in .fi +.in .PP The definitions of most of the above file type test macros are provided if any of the following feature test macros is defined: diff --git a/man7/inotify.7 b/man7/inotify.7 index 5247829693..193feca5cf 100644 --- a/man7/inotify.7 +++ b/man7/inotify.7 @@ -103,9 +103,9 @@ see Each successful .BR read (2) returns a buffer containing one or more of the following structures: +.PP .in +4n -.nf - +.EX struct inotify_event { int wd; /* Watch descriptor */ .\" FIXME . The type of the 'wd' field should probably be "int32_t". diff --git a/man7/keyrings.7 b/man7/keyrings.7 index e29ba2a864..e6ec218789 100644 --- a/man7/keyrings.7 +++ b/man7/keyrings.7 @@ -552,8 +552,8 @@ is the following: 32100fab I--Q--- 4 perm 1f3f0000 1000 65534 keyring _uid.1000: 2 32a387ea I--Q--- 1 perm 3f010000 1000 1000 keyring _pid: 2 3ce56aea I--Q--- 5 perm 3f030000 1000 1000 keyring _ses: 1 -.in .fi +.in .IP The fields shown in each line of this file are as follows: .RS @@ -714,13 +714,13 @@ This file lists various information for each user ID that has at least one key on the system. An example of the data that one might see in this file is the following: .IP -.nf .in +4n +.nf 0: 10 9/9 2/1000000 22/25000000 42: 9 9/9 8/200 106/20000 1000: 11 11/11 10/200 271/20000 -.in .fi +.in .IP The fields shown in each line are as follows: .RS diff --git a/man7/man-pages.7 b/man7/man-pages.7 index 3d50fdf125..e4a7ede73c 100644 --- a/man7/man-pages.7 +++ b/man7/man-pages.7 @@ -203,9 +203,9 @@ EXAMPLE .\" AUTHORS sections are discouraged .\" AUTHORS [Discouraged] \fBSEE ALSO\fP - -.fi +.EE .in +.PP .IR "Where a traditional heading would apply" ", " "please use it" ; this kind of consistency can make the information easier to understand. If you must, you can create your own @@ -550,13 +550,13 @@ macro). Complete commands should, if long, be written as an indented line on their own, with a blank line before and after the command, for example +.PP .in +4n -.nf - +.EX man 7 man-pages - -.fi +.EE .in +.PP If the command is short, then it can be included inline in the text, in italic format, for example, .IR "man 7 man-pages" . diff --git a/man7/math_error.7 b/man7/math_error.7 index fced6e0979..afbb54f5de 100644 --- a/man7/math_error.7 +++ b/man7/math_error.7 @@ -55,13 +55,13 @@ A portable program that needs to check for an error from a mathematical function should set .I errno to zero, and make the following call +.PP .in +4n -.nf - +.EX feclearexcept(FE_ALL_EXCEPT); - -.fi +.EE .in +.PP before calling a mathematical function. .PP Upon return from the mathematical function, if @@ -69,14 +69,14 @@ Upon return from the mathematical function, if is nonzero, or the following call (see .BR fenv (3)) returns nonzero +.PP .in +4n -.nf - +.EX fetestexcept(FE_INVALID | FE_DIVBYZERO | FE_OVERFLOW | FE_UNDERFLOW); - -.fi +.EE .in +.PP .\" enum .\" { .\" FE_INVALID = 0x01, @@ -219,9 +219,9 @@ For example, the following code ensures that .BR log (3)'s argument is not a NaN and is not zero (a pole error) or less than zero (a domain error): +.PP .in +4n -.nf - +.EX double x, r; if (isnan(x) || islessequal(x, 0)) { @@ -229,9 +229,9 @@ if (isnan(x) || islessequal(x, 0)) { } r = log(x); - -.fi +.EE .in +.PP The discussion on this page does not apply to the complex mathematical functions (i.e., those declared by .IR <complex.h> ), diff --git a/man7/mount_namespaces.7 b/man7/mount_namespaces.7 index f5f2616e24..55bdb51c2c 100644 --- a/man7/mount_namespaces.7 +++ b/man7/mount_namespaces.7 @@ -284,15 +284,15 @@ we mark one mount point as shared and another as private, and then view the mounts in .IR /proc/self/mountinfo : .PP -.nf .in +4n +.nf sh1# \fBmount \-\-make\-shared /mntS\fP sh1# \fBmount \-\-make\-private /mntP\fP sh1# \fBcat /proc/self/mountinfo | grep \(aq/mnt\(aq | sed \(aqs/ \- .*//\(aq\fP 77 61 8:17 / /mntS rw,relatime shared:1 83 61 8:15 / /mntP rw,relatime -.in .fi +.in .PP From the .IR /proc/self/mountinfo @@ -311,25 +311,25 @@ is the root directory, .IR / , which is mounted as private: .PP -.nf .in +4n +.nf sh1# \fBcat /proc/self/mountinfo | awk \(aq$1 == 61\(aq | sed \(aqs/ \- .*//\(aq\fP 61 0 8:2 / / rw,relatime -.in .fi +.in .PP On a second terminal, we create a new mount namespace where we run a second shell and inspect the mounts: .PP -.nf .in +4n +.nf $ \fBPS1=\(aqsh2# \(aq sudo unshare \-m \-\-propagation unchanged sh\fP sh2# \fBcat /proc/self/mountinfo | grep \(aq/mnt\(aq | sed \(aqs/ \- .*//\(aq\fP 222 145 8:17 / /mntS rw,relatime shared:1 225 145 8:15 / /mntP rw,relatime -.in .fi +.in .PP The new mount namespace received a copy of the initial mount namespace's mount points. @@ -349,8 +349,8 @@ and .IR /mntP and inspect the set-up: .PP -.nf .in +4n +.nf sh2# \fBmkdir /mntS/a\fP sh2# \fBmount /dev/sdb6 /mntS/a\fP sh2# \fBmkdir /mntP/b\fP @@ -360,8 +360,8 @@ sh2# \fBcat /proc/self/mountinfo | grep \(aq/mnt\(aq | sed \(aqs/ \- .*//\(aq\fP 225 145 8:15 / /mntP rw,relatime 178 222 8:22 / /mntS/a rw,relatime shared:2 230 225 8:23 / /mntP/b rw,relatime -.in .fi +.in .PP From the above, it can be seen that .IR /mntS/a @@ -377,14 +377,14 @@ but the new mount created under the private mount point .IR /mntP did not propagate: .PP -.nf .in +4n +.nf sh1# \fBcat /proc/self/mountinfo | grep \(aq/mnt\(aq | sed \(aqs/ \- .*//\(aq\fP 77 61 8:17 / /mntS rw,relatime shared:1 83 61 8:15 / /mntP rw,relatime 179 77 8:22 / /mntS/a rw,relatime shared:2 -.in .fi +.in .\" .SS MS_SLAVE example Making a mount point a slave allows it to receive propagated @@ -399,38 +399,38 @@ from having side effects in other namespaces. We can demonstrate the effect of slaving by first marking two mount points as shared in the initial mount namespace: .PP -.nf .in +4n +.nf sh1# \fBmount \-\-make\-shared /mntX\fP sh1# \fBmount \-\-make\-shared /mntY\fP sh1# \fBcat /proc/self/mountinfo | grep \(aq/mnt\(aq | sed \(aqs/ \- .*//\(aq\fP 132 83 8:23 / /mntX rw,relatime shared:1 133 83 8:22 / /mntY rw,relatime shared:2 -.in .fi +.in .PP On a second terminal, we create a new mount namespace and inspect the mount points: .PP -.nf .in +4n +.nf sh2# \fBunshare \-m \-\-propagation unchanged sh\fP sh2# \fBcat /proc/self/mountinfo | grep \(aq/mnt\(aq | sed \(aqs/ \- .*//\(aq\fP 168 167 8:23 / /mntX rw,relatime shared:1 169 167 8:22 / /mntY rw,relatime shared:2 -.in .fi +.in .PP In the new mount namespace, we then mark one of the mount points as a slave: .PP -.nf .in +4n +.nf sh2# \fBmount \-\-make\-slave /mntY\fP sh2# \fBcat /proc/self/mountinfo | grep \(aq/mnt\(aq | sed \(aqs/ \- .*//\(aq\fP 168 167 8:23 / /mntX rw,relatime shared:1 169 167 8:22 / /mntY rw,relatime master:2 -.in .fi +.in .PP From the above output, we see that .IR /mntY @@ -442,14 +442,14 @@ Continuing in the new namespace, we create submounts under each of and .IR /mntY : .PP -.nf .in +4n +.nf sh2# \fBmkdir /mntX/a\fP sh2# \fBmount /dev/sda3 /mntX/a\fP sh2# \fBmkdir /mntY/b\fP sh2# \fBmount /dev/sda5 /mntY/b\fP -.in .fi +.in .PP When we inspect the state of the mount points in the new mount namespace, we see that @@ -459,15 +459,15 @@ was created as a new shared mount .IR /mntY/b was created as a private mount: .PP -.nf .in +4n +.nf sh2# \fBcat /proc/self/mountinfo | grep \(aq/mnt\(aq | sed \(aqs/ \- .*//\(aq\fP 168 167 8:23 / /mntX rw,relatime shared:1 169 167 8:22 / /mntY rw,relatime master:2 173 168 8:3 / /mntX/a rw,relatime shared:3 175 169 8:5 / /mntY/b rw,relatime -.in .fi +.in .PP Returning to the first terminal (in the initial mount namespace), we see that the mount @@ -478,21 +478,21 @@ but the mount .IR /mntY/b was not propagated: .PP -.nf .in +4n +.nf sh1# \fBcat /proc/self/mountinfo | grep \(aq/mnt\(aq | sed \(aqs/ \- .*//\(aq\fP 132 83 8:23 / /mntX rw,relatime shared:1 133 83 8:22 / /mntY rw,relatime shared:2 174 132 8:3 / /mntX/a rw,relatime shared:3 -.in .fi +.in .PP Now we create a new mount point under .IR /mntY in the first shell: .PP -.nf .in +4n +.nf sh1# \fBmkdir /mntY/c\fP sh1# \fBmount /dev/sda1 /mntY/c\fP sh1# \fBcat /proc/self/mountinfo | grep '/mnt' | sed 's/ \- .*//'\fP @@ -500,24 +500,24 @@ sh1# \fBcat /proc/self/mountinfo | grep '/mnt' | sed 's/ \- .*//'\fP 133 83 8:22 / /mntY rw,relatime shared:2 174 132 8:3 / /mntX/a rw,relatime shared:3 178 133 8:1 / /mntY/c rw,relatime shared:4 -.in .fi +.in .PP When we examine the mount points in the second mount namespace, we see that in this case the new mount has been propagated to the slave mount point, and that the new mount is itself a slave mount (to peer group 4): .PP -.nf .in +4n +.nf sh2# \fBcat /proc/self/mountinfo | grep \(aq/mnt\(aq | sed \(aqs/ \- .*//\(aq\fP 168 167 8:23 / /mntX rw,relatime shared:1 169 167 8:22 / /mntY rw,relatime master:2 173 168 8:3 / /mntX/a rw,relatime shared:3 175 169 8:5 / /mntY/b rw,relatime 179 169 8:1 / /mntY/c rw,relatime master:4 -.in .fi +.in .\" .SS MS_UNBINDABLE example One of the primary purposes of unbindable mounts is to avoid @@ -527,21 +527,21 @@ The problem is illustrated by the following shell session. .PP Suppose we have a system with the following mount points: .PP -.nf .in +4n +.nf # \fBmount | awk \(aq{print $1, $2, $3}\(aq\fP /dev/sda1 on / /dev/sdb6 on /mntX /dev/sdb7 on /mntY -.in .fi +.in .PP Suppose furthermore that we wish to recursively bind mount the root directory under several users' home directories. We do this for the first user, and inspect the mount points: .PP -.nf .in +4n +.nf # \fBmount \-\-rbind / /home/cecilia/\fP # \fBmount | awk \(aq{print $1, $2, $3}\(aq\fP /dev/sda1 on / @@ -550,14 +550,14 @@ We do this for the first user, and inspect the mount points: /dev/sda1 on /home/cecilia /dev/sdb6 on /home/cecilia/mntX /dev/sdb7 on /home/cecilia/mntY -.in .fi +.in .PP When we repeat this operation for the second user, we start to see the explosion problem: .PP -.nf .in +4n +.nf # \fBmount \-\-rbind / /home/henry\fP # \fBmount | awk \(aq{print $1, $2, $3}\(aq\fP /dev/sda1 on / @@ -572,8 +572,8 @@ we start to see the explosion problem: /dev/sda1 on /home/henry/home/cecilia /dev/sdb6 on /home/henry/home/cecilia/mntX /dev/sdb7 on /home/henry/home/cecilia/mntY -.in .fi +.in .PP Under .IR /home/henry , @@ -587,8 +587,8 @@ that were created in the previous step. Upon repeating the step for a third user, it becomes obvious that the explosion is exponential in nature: .PP -.nf .in +4n +.nf # \fBmount \-\-rbind / /home/otto\fP # \fBmount | awk \(aq{print $1, $2, $3}\(aq\fP /dev/sda1 on / @@ -615,8 +615,8 @@ it becomes obvious that the explosion is exponential in nature: /dev/sda1 on /home/otto/home/henry/home/cecilia /dev/sdb6 on /home/otto/home/henry/home/cecilia/mntX /dev/sdb7 on /home/otto/home/henry/home/cecilia/mntY -.in .fi +.in .PP The mount explosion problem in the above scenario can be avoided by making each of the new mounts unbindable. @@ -624,16 +624,16 @@ The effect of doing this is that recursive mounts of the root directory will not replicate the unbindable mounts. We make such a mount for the first user: .PP -.nf .in +4n +.nf # \fBmount \-\-rbind \-\-make\-unbindable / /home/cecilia\fP -.in .fi +.in .PP Before going further, we show that unbindable mounts are indeed unbindable: .PP -.nf .in +4n +.nf # \fBmkdir /mntZ\fP # \fBmount \-\-bind /home/cecilia /mntZ\fP mount: wrong fs type, bad option, bad superblock on /home/cecilia, @@ -641,25 +641,25 @@ mount: wrong fs type, bad option, bad superblock on /home/cecilia, In some cases useful info is found in syslog \- try dmesg | tail or so. -.in .fi +.in .PP Now we create unbindable recursive bind mounts for the other two users: .PP -.nf .in +4n +.nf # \fBmount \-\-rbind \-\-make\-unbindable / /home/henry\fP # \fBmount \-\-rbind \-\-make\-unbindable / /home/otto\fP -.in .fi +.in .PP Upon examining the list of mount points, we see there has been no explosion of mount points, because the unbindable mounts were not replicated under each user's directory: .PP -.nf .in +4n +.nf # \fBmount | awk \(aq{print $1, $2, $3}\(aq\fP /dev/sda1 on / /dev/sdb6 on /mntX @@ -673,8 +673,8 @@ under each user's directory: /dev/sda1 on /home/otto /dev/sdb6 on /home/otto/mntX /dev/sdb7 on /home/otto/mntY -.in .fi +.in .\" .SS Propagation type transitions The following table shows the effect that applying a new propagation type @@ -864,43 +864,43 @@ the filesystem remains visible at the correct location in the chroot-ed environment. .PP -.nf .in +4n +.nf # \fBmkdir \-p /mnt/proc\fP # \fBmount \-\-bind / /mnt\fP # \fBmount \-\-bind /proc /mnt/proc\fP -.in .fi +.in .PP Next, we ensure that the .IR /mnt mount is a shared mount in a new peer group (with no peers): .PP -.nf .in +4n +.nf # \fBmount \-\-make\-private /mnt\fP # Isolate from any previous peer group # \fBmount \-\-make\-shared /mnt\fP # \fBcat /proc/self/mountinfo | grep \(aq/mnt\(aq | sed \(aqs/ \- .*//\(aq\fP 239 61 8:2 / /mnt ... shared:102 248 239 0:4 / /mnt/proc ... shared:5 -.in .fi +.in .PP Next, we bind mount .IR /mnt/etc onto .IR /tmp/etc : .PP -.nf .in +4n +.nf # \fBmkdir \-p /tmp/etc\fP # \fBmount \-\-bind /mnt/etc /tmp/etc\fP # \fBcat /proc/self/mountinfo | egrep \(aq/mnt|/tmp/\(aq | sed \(aqs/ \- .*//\(aq\fP 239 61 8:2 / /mnt ... shared:102 248 239 0:4 / /mnt/proc ... shared:5 267 40 8:2 /etc /tmp/etc ... shared:102 -.in .fi +.in .PP Initially, these two mount points are in the same peer group, but we then make the @@ -912,16 +912,16 @@ and then make shared as well, so that it can propagate events to the next slave in the chain: .PP -.nf .in +4n +.nf # \fBmount \-\-make\-slave /tmp/etc\fP # \fBmount \-\-make\-shared /tmp/etc\fP # \fBcat /proc/self/mountinfo | egrep \(aq/mnt|/tmp/\(aq | sed \(aqs/ \- .*//\(aq\fP 239 61 8:2 / /mnt ... shared:102 248 239 0:4 / /mnt/proc ... shared:5 267 40 8:2 /etc /tmp/etc ... shared:105 master:102 -.in .fi +.in .PP Then we bind mount .IR /tmp/etc @@ -933,8 +933,8 @@ but we then make a slave of .IR /tmp/etc : .PP -.nf .in +4n +.nf # \fBmkdir \-p /mnt/tmp/etc\fP # \fBmount \-\-bind /tmp/etc /mnt/tmp/etc\fP # \fBmount \-\-make\-slave /mnt/tmp/etc\fP @@ -943,9 +943,9 @@ a slave of 248 239 0:4 / /mnt/proc ... shared:5 267 40 8:2 /etc /tmp/etc ... shared:105 master:102 273 239 8:2 /etc /mnt/tmp/etc ... master:105 - +.EE .in -.fi +.PP From the above, we see that .IR /mnt is the master of the slave @@ -960,23 +960,23 @@ to the directory, which renders the mount with ID 267 unreachable from the (new) root directory: .PP -.nf .in +4n +.nf # \fBchroot /mnt\fP -.in .fi +.in .PP When we examine the state of the mounts inside the chroot-ed environment, we see the following: .PP -.nf .in +4n +.nf # \fBcat /proc/self/mountinfo | sed \(aqs/ \- .*//\(aq\fP 239 61 8:2 / / ... shared:102 248 239 0:4 / /proc ... shared:5 273 239 8:2 /etc /tmp/etc ... master:105 propagate_from:102 -.in .fi +.in .PP Above, we see that the mount with ID 273 is a slave whose master is the peer group 105. diff --git a/man7/mq_overview.7 b/man7/mq_overview.7 index 9713d35981..b85f289f87 100644 --- a/man7/mq_overview.7 +++ b/man7/mq_overview.7 @@ -285,14 +285,14 @@ On Linux, message queues are created in a virtual filesystem. but the details are likely to differ.) This filesystem can be mounted (by the superuser) using the following commands: +.PP .in +4n -.nf - +.EX .RB "#" " mkdir /dev/mqueue" .RB "#" " mount \-t mqueue none /dev/mqueue" - -.fi +.EE .in +.PP The sticky bit is automatically enabled on the mount directory. .PP After the filesystem has been mounted, the message queues on the system @@ -304,14 +304,14 @@ and .PP The contents of each file in the directory consist of a single line containing information about the queue: +.PP .in +4n -.nf - +.EX .RB "$" " cat /dev/mqueue/mymq" QSIZE:129 NOTIFY:2 SIGNO:0 NOTIFY_PID:8260 - -.fi +.EE .in +.PP These fields are as follows: .TP .B QSIZE diff --git a/man7/pthreads.7 b/man7/pthreads.7 index ec0fa79efa..0cf1167504 100644 --- a/man7/pthreads.7 +++ b/man7/pthreads.7 @@ -139,9 +139,9 @@ called from multiple threads at the same time. POSIX.1-2001 and POSIX.1-2008 require that all functions specified in the standard shall be thread-safe, except for the following functions: +.PP .in +4n -.nf - +.EX asctime() basename() catgets() @@ -242,9 +242,9 @@ in an application where asynchronous cancelability is enabled (see .PP Only the following functions are required to be async-cancel-safe by POSIX.1-2001 and POSIX.1-2008: +.PP .in +4n -.nf - +.EX pthread_cancel() pthread_setcancelstate() pthread_setcanceltype() @@ -855,24 +855,24 @@ Since glibc 2.3.2, the .BR getconf (1) command can be used to determine the system's threading implementation, for example: -.nf +.PP .in +4n - +.EX bash$ getconf GNU_LIBPTHREAD_VERSION NPTL 2.3.4 -.in .fi +.in .PP With older glibc versions, a command such as the following should be sufficient to determine the default threading implementation: -.nf +.PP .in +4n - +.EX bash$ $( ldd /bin/ls | grep libc.so | awk \(aq{print $3}\(aq ) | \\ egrep \-i \(aqthreads|nptl\(aq Native POSIX Threads Library by Ulrich Drepper et al -.in .fi +.in .SS Selecting the threading implementation: LD_ASSUME_KERNEL On systems with a glibc that supports both LinuxThreads and NPTL (i.e., glibc 2.3.\fIx\fP), the @@ -888,14 +888,14 @@ of LinuxThreads. (broken) application that depends on some nonconformant behavior in LinuxThreads.) For example: -.nf +.PP .in +4n - +.EX bash$ $( LD_ASSUME_KERNEL=2.2.5 ldd /bin/ls | grep libc.so | \\ awk \(aq{print $3}\(aq ) | egrep \-i \(aqthreads|nptl\(aq linuxthreads-0.10 by Xavier Leroy -.in .fi +.in .SH SEE ALSO .ad l .nh diff --git a/man7/sched.7 b/man7/sched.7 index c246001aa4..45c32c22a7 100644 --- a/man7/sched.7 +++ b/man7/sched.7 @@ -754,12 +754,12 @@ jobs on the system. A process's autogroup (task group) membership can be viewed via the file .IR /proc/[pid]/autogroup : .PP -.nf .in +4n +.nf $ \fBcat /proc/1/autogroup\fP /autogroup-1 nice 0 -.in .fi +.in .PP This file can also be used to modify the CPU bandwidth allocated to an autogroup. @@ -878,11 +878,11 @@ the following to modify the autogroup nice value for .I all of the processes in a terminal session: .PP -.nf .in +4n +.nf $ \fBecho 10 > /proc/self/autogroup\fP -.in .fi +.in .SS Real-time features in the mainline Linux kernel .\" FIXME . Probably this text will need some minor tweaking .\" ask Carsten Emde about this. @@ -895,9 +895,9 @@ Until the patches have been completely merged into the mainline kernel, they must be installed to achieve the best real-time performance. These patches are named: +.PP .in +4n -.nf - +.EX patch-\fIkernelversion\fP-rt\fIpatchversion\fP .fi .in diff --git a/man7/session-keyring.7 b/man7/session-keyring.7 index 070235f5da..82a88d8d7d 100644 --- a/man7/session-keyring.7 +++ b/man7/session-keyring.7 @@ -85,21 +85,21 @@ These operations are also exposed through the .BR keyctl (1) utility as: .PP -.nf .in +4n +.nf keyctl session keyctl session - [<prog> <arg1> <arg2> ...] keyctl session <name> [<prog> <arg1> <arg2> ...] -.in .fi +.in .PP and: .PP -.nf .in +4n +.nf keyctl new_session -.in .fi +.in .SH SEE ALSO .ad l .nh diff --git a/man7/udplite.7 b/man7/udplite.7 index 0f6c68f355..d47c5c6d61 100644 --- a/man7/udplite.7 +++ b/man7/udplite.7 @@ -134,9 +134,9 @@ UDP-Litev4/v6 first appeared in Linux 2.6.20. .SH BUGS .\" FIXME . remove this section once glibc supports UDP-Lite Where glibc support is missing, the following definitions are needed: +.PP .in +4n -.nf - +.EX #define IPPROTO_UDPLITE 136 .\" The following two are defined in the kernel in linux/net/udplite.h #define UDPLITE_SEND_CSCOV 10 diff --git a/man7/unix.7 b/man7/unix.7 index 0ed3a4fc86..5b29d4d9a6 100644 --- a/man7/unix.7 +++ b/man7/unix.7 @@ -57,9 +57,9 @@ UNIX domain sockets support passing file descriptors or process credentials to other processes using ancillary data. .SS Address format A UNIX domain socket address is represented in the following structure: +.PP .in +4n -.nf - +.EX .\" #define UNIX_PATH_MAX 108 .\" struct sockaddr_un { @@ -673,8 +673,8 @@ if (getsockname(sfd, (struct sockaddr *) addrp, &addrlen)) == \-1) /* handle error */ ; printf("sun_path = %s\\n", ((struct sockaddr_un *) addrp)\->sun_path); -.in .fi +.in .PP This sort of messiness can be avoided if it is guaranteed that the applications that diff --git a/man7/vdso.7 b/man7/vdso.7 index bafd181ba3..2e4998ff42 100644 --- a/man7/vdso.7 +++ b/man7/vdso.7 @@ -575,9 +575,9 @@ to user space, so it was reconceived as a vDSO in the current format. .BR proc (5) .PP The documents, examples, and source code in the Linux source code tree: +.PP .in +4n -.nf - +.EX Documentation/ABI/stable/vdso Documentation/ia64/fsys.txt Documentation/vDSO/* (includes examples of using the vDSO) |