[systemd-devel] Journal Log Persistence without restart of service

[Renjith Vijayan]

Hi All,

I am trying to make journal logs persistent across reboots in my platform.
Currently /var/log is mounted on volatile partition in the platform.
I have a non-volatile partition mounted at /var/diagnostics.
So i made the following change in tmpfile.d service config
file(volatile.conf) to create a symlink.

L+ /var/log/journal 0666 root root - /var/diagnostics/logs

Also, the following changes to make logs persistent is done in
journald.conf file.
Storage=persistent

But still when the system boots up it takes the run time journal path & no
files are present in /var/log/journal directory..
*systemd-journal[114]: Runtime journal is using 8.0M (max allowed 392.4M,
trying to leave 588.6M free of 3.8G available â current limit 392.4M).*
*Jan 09 05:18:58 ops-as5712 systemd-journal[114]: Runtime journal is using
8.0M (max allowed 392.4M, trying to leave 588.6M free of 3.8G available â
current limit 392.4M).*
*Jan 09 05:18:58 ops-as5712 systemd-journal[114]: Journal started*
*Jan 09 05:18:58 ops-as5712 systemd-journal[114]: Runtime journal is using
8.0M*

After i restart the systemd-journald service, the logs are becoming
persistent & getting stored in the permanent partition.

Could somebody point out what needs to be done to make it persistent
without the restart of systemd-journald service?

TIA,
Renjith
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20160424/96e5efde/attachment.html>