summaryrefslogtreecommitdiff
path: root/man/systemd-pstore.service.xml
Commit message (Collapse)AuthorAgeFilesLines
* man: various typos and other small issuesZbigniew Jędrzejewski-Szmek2021-01-291-15/+12
| | | | Fixes #18397.
* license: LGPL-2.1+ -> LGPL-2.1-or-laterYu Watanabe2020-11-091-1/+1
|
* pstore: introduce tmpfiles.d/systemd-pstore.confEric DeVolder2020-05-151-0/+18
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* man: add .service suffix to systemd-pstore(8)Zbigniew Jędrzejewski-Szmek2020-02-291-0/+99
That is the pattern that we always use with executables not in $PATH.