diff options
author | Eric DeVolder <eric.devolder@oracle.com> | 2020-04-13 16:22:04 -0500 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2020-05-15 23:15:26 +0200 |
commit | f00c36641a253f4ea659ec3def5d87ba1336eb3b (patch) | |
tree | 76f09c69c3be43f569107a128e5330a8d7864582 /test/TEST-03-JOBS | |
parent | b4e1563ffb12c50ff89c063e721b76bfc89407b7 (diff) | |
download | systemd-f00c36641a253f4ea659ec3def5d87ba1336eb3b.tar.gz |
pstore: introduce tmpfiles.d/systemd-pstore.conf
The systemd pstore service archives the contents of /sys/fs/pstore
upon boot so that there is room for a subsequent dump. The issue is
that while the service is present, the kernel still needs to be
configured to write data into the pstore. The kernel has two
parameters, crash_kexec_post_notifiers and printk.always_kmsg_dump,
that control writes into pstore.
The crash_kexec_post_notifiers parameter enables the kernel to write
dmesg (including stack trace) into pstore upon a panic, and
printk.always_kmsg_dump parameter enables the kernel to write dmesg
upon a shutdown (shutdown, reboot, halt).
As it stands today, these parameters are not managed/manipulated by
the systemd pstore service, and are solely reliant upon the user [to
have the foresight] to set them on the kernel command line at boot, or
post boot via sysfs. Furthermore, the user would need to set these
parameters in a persistent fashion so that that they are enabled on
subsequent reboots.
This patch introduces the setting of these two kernel parameters via
the systemd tmpfiles technique.
Diffstat (limited to 'test/TEST-03-JOBS')
0 files changed, 0 insertions, 0 deletions