core.5: tfix

Escape hyphens.

Signed-off-by: Jakub Wilk <jwilk@jwilk.net>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Jakub Wilk 2019-03-19 17:12:44 +01:00 committed by Michael Kerrisk
parent 03349e33f9
commit 4818bee547
1 changed files with 9 additions and 9 deletions

View File

@ -120,7 +120,7 @@ core dump files will have names of the form
.IR .pid ,
and such files are hidden unless one uses the
.BR ls (1)
.I -a
.I \-a
option.
.IP *
(Since Linux 3.7)
@ -458,24 +458,24 @@ employs the
.I core_pattern
feature that allows piping core dumps to a program.
One can verify this by checking whether core dumps are being piped to the
.BR systemd-coredump (8)
.BR systemd\-coredump (8)
program:
.PP
.in +4n
.EX
$ \fBcat /proc/sys/kernel/core_pattern\fP
|/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %e
|/usr/lib/systemd/systemd\-coredump %P %u %g %s %t %c %e
.EE
.in
.PP
In this case, core dumps will be placed in the location configured for
.BR systemd-coredump (8),
.BR systemd\-coredump (8),
typically as
.BR lz4 (1)
compressed files in the directory
.IR /var/lib/systemd/coredump/ .
One can list the core dumps that have been recorded by
.BR systemd-coredump (8)
.BR systemd\-coredump (8)
using
.BR coredumpctl (1):
.PP
@ -505,7 +505,7 @@ in the current directory, one could use:
.PP
.in +4n
.EX
$ \fBcoredumpctl dump 2955 -o core\fP
$ \fBcoredumpctl dump 2955 \-o core\fP
.EE
.in
.PP
@ -522,8 +522,8 @@ mechanism, using something like:
.PP
.in +2n
.EX
# echo "kernel.core_pattern=core.%p" > /etc/sysctl.d/50-coredump.conf
# /lib/systemd/systemd-sysctl
# echo "kernel.core_pattern=core.%p" > /etc/sysctl.d/50\-coredump.conf
# /lib/systemd/systemd\-sysctl
.EE
.in
.PP
@ -655,4 +655,4 @@ main(int argc, char *argv[])
.BR proc (5),
.BR pthreads (7),
.BR signal (7),
.BR systemd-coredump (8)
.BR systemd\-coredump (8)