asked 2013-12-28 17:02:10 +0200
Some bugs need reboots etc funny things which persistent systemd/journal logs don't capture. What is the recommended way to enable capture more detailed logs from jolla device?
FWIW, I replaced volatile word persistent in /etc/systemd/journald.conf and rebooted. Hopefully this catches my system SW update related problem details.
answered 2014-02-14 14:18:25 +0200
This post is a wiki. Anyone with karma >75 is welcome to improve it.
Enable developer mode. In shell get root rights and edit file /etc/systemd/journald.conf. Change setting Storage to be "Storage=persistent". Then restart journald service with command "systemctl restart systemd-journald.service". Now journal logs will be saved to the internal root filesystem. Use journalctl to view the logs.
Jolla SW updates will reset the logs to default memory only storage so persistent logs need to be re-enabled after SW updates.
answered 2013-12-28 17:22:34 +0200
Also, how to scrub personal details like user and server names from the logs?
Asked: 2013-12-28 17:02:10 +0200
Seen: 1,211 times
Last updated: Feb 14 '14
Also, along with the above change, create /var/log/journal (as root) then reboot and your system journals should be persisted in that directory.
Milhouse ( 2013-12-28 18:46:08 +0200 )edit