]> git.ipfire.org Git - thirdparty/openembedded/openembedded-core-contrib.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>
Tue, 10 Mar 2015 10:47:51 +0000 (10:47 +0000)
commite75c95ceca34879698b1ea229a2101dc1ccc12fc
treee9c7a675f8b4d0f98af37c2ab16a00dfb706d650
parentd7fe8b46a5e3fa0b3bac33a25bc3845c39f443f3
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]

(From OE-Core rev: 17e8595af2041cfd63adf73b344f7ccad3db7e01)

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