pid_namespaces.7: srcfix

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

diff --git a/man7/pid_namespaces.7 b/man7/pid_namespaces.7
index eae9d96092013842684e57b945b65b9d72f78ba3..a84d85fd45f03d1963fdf98affb4fb7214281261 100644 (file)
--- a/man7/pid_namespaces.7
+++ b/man7/pid_namespaces.7
@@ -45,6 +45,9 @@ 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
@@ -104,6 +107,9 @@ 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).
+.\"
+.\" ============================================================
+.\"
 .SS Nesting PID namespaces
 PID namespaces can be nested.
 When a new PID namespace is created,
@@ -144,7 +150,9 @@ PID namespace from the caller of
 Calls to
 .BR getppid (2)
 for such processes return 0.
-
+.\"
+.\" ============================================================
+.\"
 .SS setns(2) and unshare(2) semantics
 Calls to
 .BR setns (2)
@@ -184,6 +192,9 @@ calls only change the PID namespace for created children, the
 .BR clone (2)
 calls necessarily put the new thread in a different PID namespace from
 the calling thread.
+.\"
+.\" ============================================================
+.\"
 .SS Miscellaneous
 After creating a new PID namespace,
 it is useful for the child to change its root directory