ÿØÿàJFIFÿþ ÿÛC       ÿÛC ÿÀÿÄÿÄ"#QrÿÄÿÄ&1!A"2qQaáÿÚ ?Øy,æ/3JæÝ¹È߲؋5êXw²±ÉyˆR”¾I0ó2—PI¾IÌÚiMö¯–þrìN&"KgX:Šíµ•nTJnLK„…@!‰-ý ùúmë;ºgµŒ&ó±hw’¯Õ@”Ü— 9ñ-ë.²1<yà‚¹ïQÐU„ہ?.’¦èûbß±©Ö«Âw*VŒ) `$‰bØÔŸ’ëXÖ-ËTÜíGÚ3ð«g Ÿ§¯—Jx„–’U/ÂÅv_s(Hÿ@TñJÑãõçn­‚!ÈgfbÓc­:él[ðQe 9ÀPLbÃãCµm[5¿ç'ªjglå‡Ûí_§Úõl-;"PkÞÞÁQâ¼_Ñ^¢SŸx?"¸¦ùY騐ÒOÈ q’`~~ÚtËU¹CڒêV  I1Áß_ÿÙ# SPDX-License-Identifier: LGPL-2.1+ # # The systemd-pstore.service(1) archives the contents of /sys/fs/pstore # upon boot so that there is room for a subsequent dump. This service # is enabled with: # systemctl enable systemd-pstore # # With the service enabled, 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 even if kdump # is loaded, only needed if you want to use pstore with kdump. Without # this parameter, kdump could block writing to pstore for stability # reason. Note this increases the risk of kdump failure even if pstore # is not available. # # The printk.always_kmsg_dump parameter enables the kernel to write dmesg # upon a normal shutdown (shutdown, reboot, halt). # # To configure the kernel parameters, uncomment the appropriate # line(s) below. The value written is either 'Y' to enable the # kernel parameter, or 'N' to disable the kernel parameter. # # After making a change to this file, do: # systemd-tmpfiles --create path/to/tmpfiles.d/systemd-pstore.conf # # These changes are automatically applied on future re-boots. d /var/lib/systemd/pstore 0755 root root 14d #w- /sys/module/printk/parameters/always_kmsg_dump - - - - Y #w- /sys/module/kernel/parameters/crash_kexec_post_notifiers - - - - Y