system/systemd
system/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd synced 2024-07-09 12:36:12 +00:00
Code Issues Projects Releases Wiki Activity
4f6d8ab076
systemd/units/systemd-journal-flush.service

32 lines
943 B
SYSTEMD
Raw Normal View History

license: LGPL-2.1+ -> LGPL-2.1-or-later
2020-11-09 04:23:58 +00:00
# SPDX-License-Identifier: LGPL-2.1-or-later
Add SPDX license headers to unit files
2017-11-18 16:35:03 +00:00
#
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 00:41:16 +00: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 17:52:14 +00: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 00:41:16 +00:00
Documentation=man:systemd-journald.service(8) man:journald.conf(5)
units: do more reordering of ordering config No functional change, just a cleanup to make the subsequent changes easier to see. This is a continuation of 9810e419425263bde86787bc21251f1ad3c35628 > The block is reordered and split to have: > 1. description + documentation > 2. (optionally) conditions > 3. all the dependencies The dependencies for shutdown.target are listed separately because they are the other deps are for startup, and shutdown.target only matter much later.
2022-09-15 13:54:18 +00:00
ConditionPathExists=!/etc/initrd-release
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 00:41:16 +00:00
DefaultDependencies=no
units: make templates for quotaon and systemd-quotacheck service
2022-09-19 14:57:48 +00:00
After=systemd-remount-fs.service systemd-quotacheck-root.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 19:41:02 +00:00
Before=systemd-tmpfiles-setup.service
units: do more reordering of ordering config No functional change, just a cleanup to make the subsequent changes easier to see. This is a continuation of 9810e419425263bde86787bc21251f1ad3c35628 > The block is reordered and split to have: > 1. description + documentation > 2. (optionally) conditions > 3. all the dependencies The dependencies for shutdown.target are listed separately because they are the other deps are for startup, and shutdown.target only matter much later.
2022-09-15 13:54:18 +00:00
Wants=systemd-journald.service
After=systemd-journald.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 15:22:36 +00: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 00:41:16 +00:00
unit: also stop systemd-journal-flush.service on soft-reboot After soft-reboot, /var/log/journal may be initially read-only, and becomes writable a bit later. In such case, runtime journal is initially opened by journald. Hence, we need to flush to /var when it is ready.
2024-05-24 21:09:52 +00:00
Before=soft-reboot.target systemd-soft-reboot.service
Conflicts=soft-reboot.target
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 00:41:16 +00:00
[Service]
units: drop full paths for utilities in $PATH This makes things a bit simpler and the build a bit faster, because we don't have to rewrite files to do the trivial substitution. @rootbindir@ is always in our internal $PATH that we use for non-absolute paths, so there should be no functional change.
2019-12-18 08:14:57 +00:00
ExecStart=journalctl --flush
ExecStop=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 00:41:16 +00: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-22 22:28:17 +00: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 20:34:32 +00:00
TimeoutSec=90s
Reference in New Issue Copy Permalink