aboutsummaryrefslogtreecommitdiffstats
path: root/man5
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2016-10-07 22:42:07 +0200
committerMichael Kerrisk <mtk.manpages@gmail.com>2016-10-07 22:47:23 +0200
commit750653a812a98d9d19c7d0f9fd263d124457be39 (patch)
tree95469e4ef92a614a95b341be8e085ab4bafe7b9f /man5
parent85976da34f36a3347dcae5a44140c3591bd538fd (diff)
downloadman-pages-750653a812a98d9d19c7d0f9fd263d124457be39.tar.gz
getrusage.2, madvise.2, memfd_create.2, mlock.2, mount.2, getauxval.3, core.5, capabilities.7, pid_namespaces.7, symlink.7, user_namespaces.7: Consistently use /proc/[pid] (not /proc/PID)
Reported-by: Mike Frysinger <vapier@gentoo.org> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Diffstat (limited to 'man5')
-rw-r--r--man5/core.56
1 files changed, 3 insertions, 3 deletions
diff --git a/man5/core.5 b/man5/core.5
index f780ce6811..0a1ed942fc 100644
--- a/man5/core.5
+++ b/man5/core.5
@@ -287,12 +287,12 @@ in an argument.
When collecting core dumps via a pipe to a user-space program,
it can be useful for the collecting program to gather data about
the crashing process from that process's
-.IR /proc/PID
+.IR /proc/[pid]
directory.
In order to do this safely,
the kernel must wait for the program collecting the core dump to exit,
so as not to remove the crashing process's
-.IR /proc/PID
+.IR /proc/[pid]
files prematurely.
This in turn creates the
possibility that a misbehaving collecting program can block
@@ -317,7 +317,7 @@ The default value for this file is 0.
.\"
.SS Controlling which mappings are written to the core dump
Since kernel 2.6.23, the Linux-specific
-.IR /proc/PID/coredump_filter
+.IR /proc/[pid]/coredump_filter
file can be used to control which memory segments are written to the
core dump file in the event that a core dump is performed for the
process with the corresponding process ID.