diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2014-06-28 00:06:30 -0400 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2014-06-28 00:06:30 -0400 |
| commit | 0fdeb6e011dfdb17636c81e2d7e0d632186359ce (patch) | |
| tree | 2a05105066042201236d18e87b0af913fdec6993 /units/systemd-tmpfiles-setup.service.in | |
| parent | 102bd40e1ed71c7ab980a90435a1c23d4c786c63 (diff) | |
units: remove RefuseManualStart from units which are always around
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.
Diffstat (limited to 'units/systemd-tmpfiles-setup.service.in')
| -rw-r--r-- | units/systemd-tmpfiles-setup.service.in | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/units/systemd-tmpfiles-setup.service.in b/units/systemd-tmpfiles-setup.service.in index d3c6da88c4..72ab083d54 100644 --- a/units/systemd-tmpfiles-setup.service.in +++ b/units/systemd-tmpfiles-setup.service.in @@ -12,7 +12,6 @@ DefaultDependencies=no Conflicts=shutdown.target After=systemd-readahead-collect.service systemd-readahead-replay.service local-fs.target systemd-sysusers.service Before=sysinit.target shutdown.target -RefuseManualStart=yes RefuseManualStop=yes [Service] |