2012-04-22 04:15:22 +04:00
/console-getty.service
2013-01-30 06:17:40 +04:00
/console-getty.service.m4
2012-06-25 16:24:56 +04:00
/console-shell.service
2013-01-30 06:17:40 +04:00
/console-shell.service.m4
2013-12-13 23:29:35 +04:00
/container-getty@.service
/container-getty@.service.m4
/debug-shell.service
/emergency.service
/getty@.service
/halt-local.service
/initrd-cleanup.service
/initrd-parse-etc.service
/initrd-switch-root.service
/initrd-udevadm-cleanup-db.service
/kmod-static-nodes.service
/quotaon.service
/rc-local.service
2012-06-25 16:24:56 +04:00
/rescue.service
2013-01-30 06:17:40 +04:00
/rescue.service.m4
2013-12-13 23:29:35 +04:00
/serial-getty@.service
/systemd-ask-password-console.service
2012-06-25 16:24:56 +04:00
/systemd-ask-password-wall.service
2013-12-13 23:29:35 +04:00
/systemd-backlight@.service
/systemd-binfmt.service
/systemd-bus-proxyd@.service
2012-06-25 15:47:45 +04:00
/systemd-fsck-root.service
2013-12-13 23:29:35 +04:00
/systemd-fsck@.service
2012-06-25 16:24:56 +04:00
/systemd-halt.service
2013-12-13 23:29:35 +04:00
/systemd-hibernate.service
/systemd-hostnamed.service
/systemd-hybrid-sleep.service
/systemd-initctl.service
/systemd-journal-flush.service
/systemd-journal-gatewayd.service
2014-06-13 15:10:30 +04:00
/systemd-journal-catalog-update.service
2013-12-13 23:29:35 +04:00
/systemd-journald.service
2012-06-25 16:24:56 +04:00
/systemd-kexec.service
2013-12-13 23:29:35 +04:00
/systemd-localed.service
/systemd-logind.service
/systemd-machined.service
/systemd-modules-load.service
/systemd-networkd.service
networkd-wait-online: improve interoptability and enable by default
To make sure we don't delay boot on systems where (some) network links are managed by someone else
we don't block if something else has successfully brought up a link.
We will still block until all links we are aware of that are managed by networkd have been
configured, but if no such links exist, and someone else have configured a link sufficiently
that it has a carrier, it may be that the link is ready so we should no longer block.
Note that in all likelyhood the link is not ready (no addresses/routes configured),
so whatever network managment daemon configured it should provide a similar wait-online
service to block network-online.target until it is ready.
The aim is to block as long as we know networking is not fully configured, but no longer. This
will allow systemd-networkd-wait-online.service to be enabled on any system, even if we don't
know whether networkd is the main/only network manager.
Even in the case networking is fully configured by networkd, the default behavior may not be
sufficient: if two links need to be configured, but the first is fully configured before the
second one appears we will assume the network is up. To work around that, we allow specifying
specific devices to wait for before considering the network up.
This unit is enabled by default, just like systemd-networkd, but will only be pulled in if
anyone pulls in network-online.target.
2014-04-23 19:42:55 +04:00
/systemd-networkd-wait-online.service
2013-12-13 23:29:35 +04:00
/systemd-nspawn@.service
/systemd-poweroff.service
/systemd-quotacheck.service
/systemd-random-seed.service
2012-06-25 16:24:56 +04:00
/systemd-readahead-collect.service
2013-12-13 23:29:35 +04:00
/systemd-readahead-done.service
2012-06-25 16:24:56 +04:00
/systemd-readahead-replay.service
2013-12-13 23:29:35 +04:00
/systemd-reboot.service
2012-04-24 18:42:42 +04:00
/systemd-remount-fs.service
2014-05-19 00:10:48 +04:00
/systemd-resolved.service
2013-12-13 23:29:35 +04:00
/systemd-rfkill@.service
2012-06-25 16:24:56 +04:00
/systemd-shutdownd.service
2013-12-13 23:29:35 +04:00
/systemd-suspend.service
/systemd-sysctl.service
2014-06-13 15:10:30 +04:00
/systemd-sysusers.service
2013-12-13 23:29:35 +04:00
/systemd-timedated.service
2014-04-29 10:57:51 +04:00
/systemd-timesyncd.service
2013-12-13 23:29:35 +04:00
/systemd-tmpfiles-clean.service
/systemd-tmpfiles-setup-dev.service
/systemd-tmpfiles-setup.service
/systemd-tmpfiles.service
2014-06-13 15:10:30 +04:00
/systemd-udev-hwdb-update.service
2012-04-17 01:32:22 +04:00
/systemd-udev-settle.service
/systemd-udev-trigger.service
2012-07-02 23:35:14 +04:00
/systemd-udevd.service
2013-12-13 23:29:35 +04:00
/systemd-update-utmp-runlevel.service
/systemd-update-utmp.service
update-done: add minimal tool to manage system updates for /etc and /var, if /usr has changed
In order to support offline updates to /usr, we need to be able to run
certain tasks on next boot-up to bring /etc and /var in line with the
updated /usr. Hence, let's devise a mechanism how we can detect whether
/etc or /var are not up-to-date with /usr anymore: we keep "touch
files" in /etc/.updated and /var/.updated that are mtime-compared with
/usr. This means:
Whenever the vendor OS tree in /usr is updated, and any services that
shall be executed at next boot shall be triggered, it is sufficient to
update the mtime of /usr itself. At next boot, if /etc/.updated and/or
/var/.updated is older than than /usr (or missing), we know we have to
run the update tools once. After that is completed we need to update the
mtime of these files to the one of /usr, to keep track that we made the
necessary updates, and won't repeat them on next reboot.
A subsequent commit adds a new ConditionNeedsUpdate= condition that
allows checking on boot whether /etc or /var are outdated and need
updating.
This is an early step to allow booting up with an empty /etc, with
automatic rebuilding of the necessary cache files or user databases
therein, as well as supporting later updates of /usr that then propagate
to /etc and /var again.
2014-06-13 14:43:49 +04:00
/systemd-update-done.service
2013-12-13 23:29:35 +04:00
/systemd-user-sessions.service
/systemd-vconsole-setup.service
2013-12-28 08:54:19 +04:00
/user@.service
