]> code.ossystems Code Review - openembedded-core.git/commit
systemd: Fix the problem of an empty journal on boot
authorRandy Witt <randy.e.witt@linux.intel.com>
Fri, 6 Mar 2015 02:11:46 +0000 (18:11 -0800)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Mon, 9 Mar 2015 16:05:08 +0000 (16:05 +0000)
commit17e8595af2041cfd63adf73b344f7ccad3db7e01
treee198187057905664b4294069239a2a20faee6faa
parent3569d434e754a62ec998fbf48380d653d1524dc4
systemd: Fix the problem of an empty journal on boot

systemd by default tries to write the journal to /var/log/journal.
But base-files has a symlink /var/log -> /var/volatile/log. And
/var/volatile is a tmpfs mount in /etc/fstab.

If the journal service started before /var/volatile was mounted (which
was the typical scenario) then the journal would appear empty since
the old location was mounted over.

This change fixes the problem by ensuring that the journal doesn't start
until after the mount happens.

[Yocto #7388]

Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
meta/recipes-core/systemd/systemd/journald-volatile.conf [new file with mode: 0644]
meta/recipes-core/systemd/systemd_219.bb