mirror of
https://github.com/clearlinux/systemd-stable.git
synced 2026-09-06 21:51:37 +00:00
Zbigniew Jędrzejewski-Szmek
368b458ef9
In a normal running system, non-passive targets and units used during
early bootup are always started. So refusing "manual start" for them
doesn't make any difference, because a "start" command doesn't cause
any action.
In early boot however, the administrator might want to start on
of those targets or services by hand. We shouldn't interfere with that.
Note: in case of systemd-tmpfiles-setup.service, really running the
unit after system is up would break the system. So e.g. restarting
should not be allowed. The unit has "RefuseManualStop=yes", which
prevents restart too.
(cherry picked from commit 0fdeb6e011)
Conflicts:
units/systemd-tmpfiles-setup.service.in
units/user/basic.target
27 lines
989 B
Plaintext
27 lines
989 B
Plaintext
# 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]
|
|
Description=Create Volatile Files and Directories
|
|
Documentation=man:tmpfiles.d(5) man:systemd-tmpfiles(8)
|
|
DefaultDependencies=no
|
|
Wants=local-fs.target
|
|
Conflicts=shutdown.target
|
|
After=systemd-readahead-collect.service systemd-readahead-replay.service local-fs.target
|
|
Before=sysinit.target shutdown.target
|
|
ConditionDirectoryNotEmpty=|/usr/lib/tmpfiles.d
|
|
ConditionDirectoryNotEmpty=|/lib/tmpfiles.d
|
|
ConditionDirectoryNotEmpty=|/usr/local/lib/tmpfiles.d
|
|
ConditionDirectoryNotEmpty=|/etc/tmpfiles.d
|
|
ConditionDirectoryNotEmpty=|/run/tmpfiles.d
|
|
RefuseManualStop=yes
|
|
|
|
[Service]
|
|
Type=oneshot
|
|
RemainAfterExit=yes
|
|
ExecStart=@rootbindir@/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev
|