aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2014-11-02 21:45:42 -0500
committerMike Gilbert <floppym@gentoo.org>2014-11-05 16:14:20 -0500
commit85e77df6eca7a7c14d3b3170b8dba3b7ae06ff64 (patch)
tree2353468df29f7eea1176a8c25b25ed5489457c4b
parentunits: don't order journal flushing afte remote-fs.target (diff)
downloadsystemd-85e77df6eca7a7c14d3b3170b8dba3b7ae06ff64.tar.gz
systemd-85e77df6eca7a7c14d3b3170b8dba3b7ae06ff64.tar.bz2
systemd-85e77df6eca7a7c14d3b3170b8dba3b7ae06ff64.zip
units: order sd-journal-flush after sd-remount-fs
Otherwise we could attempt to flush the journal while /var/log/ was still ro, and silently skip journal flushing. The way that errors in flushing are handled should still be changed to be more transparent and robust.
-rw-r--r--units/systemd-journal-flush.service.in1
1 files changed, 1 insertions, 0 deletions
diff --git a/units/systemd-journal-flush.service.in b/units/systemd-journal-flush.service.in
index 2612220e2..ba22c6d07 100644
--- a/units/systemd-journal-flush.service.in
+++ b/units/systemd-journal-flush.service.in
@@ -11,6 +11,7 @@ Documentation=man:systemd-journald.service(8) man:journald.conf(5)
DefaultDependencies=no
Requires=systemd-journald.service
After=systemd-journald.service
+After=systemd-remount-fs.service
Before=systemd-user-sessions.service systemd-tmpfiles-setup.service
RequiresMountsFor=/var/log/journal