5 Commits

Author	SHA1	Message	Date
Zbigniew Jędrzejewski-Szmek	1f1926aa5e	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.	2014-11-02 21:52:56 -05:00
Zbigniew Jędrzejewski-Szmek	a65b824577	systemd-journal-flush.service: remove "trigger" from description ... This service is now synchronous, so "trigger" is misleading.	2014-11-01 14:39:48 -04:00
Lennart Poettering	919699ec30	units: don't order journal flushing afte remote-fs.target ... Instead, only depend on the actual file systems we need. This should solve dep loops on setups where remote-fs.target is moved into late boot.	2014-10-31 16:23:39 +01:00
Lennart Poettering	74055aa762	journalctl: add new --flush command and make use of it in systemd-journal-flush.service ... This new command will ask the journal daemon to flush all log data stored in /run to /var, and wait for it to complete. This is useful, so that in case of Storage=persistent we can order systemd-tmpfiles-setup afterwards, to ensure any possibly newly created directory in /var/log gets proper access mode and owners.	2014-10-23 00:39:42 +02:00
Lennart Poettering	b8156be03f	journal: replace implicit flushing of journal by explicit one ... The old automatism that the flushing of the journal from /run to /var was triggered by the appearance of /var/log/journal is broken if that directory is mounted from another host and hence always available to be useful as mount point. To avoid probelsm with this, introduce a new unit that is explicitly orderer after all mounte files systems and triggers the flushing.	2012-07-11 02:41:16 +02:00