shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-11-05 15:21:37 +03:00
Code
dbca733213
systemd/units/systemd-journal-flush.service.in

25 lines
799 B
SYSTEMD
Raw Normal View History

Add SPDX license headers to unit files
2017-11-18 19:35:03 +03:00
# SPDX-License-Identifier: LGPL-2.1+
#
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 04:41:16 +04:00
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
[Unit]
systemd-journal-flush.service: remove "trigger" from description This service is now synchronous, so "trigger" is misleading.
2014-11-01 20:52:14 +03:00
Description=Flush Journal to Persistent Storage
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 04:41:16 +04:00
Documentation=man:systemd-journald.service(8) man:journald.conf(5)
DefaultDependencies=no
Requires=systemd-journald.service
units: drop systemd-user-sessions.service ordering dep on systemd-journal-flush.service (#10502) THis dep existed since the unit was introduced, but I cannot see what good it would do. Hence in the interest of simplifying things, let's drop it. If breakages appear later we can certainly revert this again. Fixes: #10469
2018-10-24 22:41:02 +03:00
After=systemd-journald.service systemd-remount-fs.service
Before=systemd-tmpfiles-setup.service
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 18:22:36 +03:00
RequiresMountsFor=/var/log/journal
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 04:41:16 +04:00
[Service]
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 02:28:17 +04:00
ExecStart=@rootbindir@/journalctl --flush
units: automatically revert to /run logging on shutdown if necessary Fixes: #867
2019-04-05 19:22:31 +03:00
ExecStop=@rootbindir@/journalctl --smart-relinquish-var
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 04:41:16 +04:00
Type=oneshot
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 02:28:17 +04:00
RemainAfterExit=yes
units: so far we defaulted to 90s as default timeout for most things, let's do so for our oneshot services too Fewer surprises, and stuff...
2015-02-02 23:34:32 +03:00
TimeoutSec=90s
Copy Permalink