shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-11-07 18:27:04 +03:00
Code
e450032f09
systemd/units/.gitignore

81 lines
2.1 KiB
Plaintext
Raw Normal View History

gitignore: hide some more files
2014-12-10 02:49:35 +03:00
/user@.service.m4
container: spawn a getty instead of a sulogin in a container
2012-04-22 04:15:22 +04:00
/console-getty.service
build-sys: keep intermediate files Sometimes it is useful to look at them, and they don't take up any significant amount of space. Keeping them also avoids the message about files being removed at the end of make run.
2013-01-30 06:17:40 +04:00
/console-getty.service.m4
bus: install systemd-bus-proxyd unit files for compatibility with dbus1
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
units: rename halt/hibernate/kexec/poweroff/reboot/suspend to systed-xxx These service units also execute our own code, hence rename the accordingly and prefix them with systemd-
2012-06-25 16:24:56 +04:00
/rescue.service
bus: install systemd-bus-proxyd unit files for compatibility with dbus1
2013-12-13 23:29:35 +04:00
/serial-getty@.service
units: add system-update-cleanup.service to guard against offline-update loops Note: the name is "system-update-cleanup.service" rather than "system-update-done.service", because it should not run normally, and also because there's already "systemd-update-done.service", and having them named so similarly would be confusing. In https://bugzilla.redhat.com/show_bug.cgi?id=1395686 the system repeatedly entered system-update.target on boot. Because of a packaging issue, the tool that created the /system-update symlink could be installed without the service unit that was supposed to perform the upgrade (and remove the symlink). In fact, if there are no units in system-update.target, and /system-update symlink is created, systemd always "hangs" in system-update.target. This is confusing for users, because there's no feedback what is happening, and fixing this requires starting an emergency shell somehow, and also knowing that the symlink must be removed. We should be more resilient in this case, and remove the symlink automatically ourselves, if there are no upgrade service to handle it. This adds a service which is started after system-update.target is reached and the symlink still exists. It nukes the symlink and reboots the machine. It should subsequently boot into the default default.target. This is a more general fix for https://bugzilla.redhat.com/show_bug.cgi?id=1395686 (the packaging issue was already fixed).
2016-11-29 09:29:02 +03:00
/system-update-cleanup.service
bus: install systemd-bus-proxyd unit files for compatibility with dbus1
2013-12-13 23:29:35 +04:00
/systemd-ask-password-console.service
units: rename halt/hibernate/kexec/poweroff/reboot/suspend to systed-xxx These service units also execute our own code, hence rename the accordingly and prefix them with systemd-
2012-06-25 16:24:56 +04:00
/systemd-ask-password-wall.service
bus: install systemd-bus-proxyd unit files for compatibility with dbus1
2013-12-13 23:29:35 +04:00
/systemd-backlight@.service
/systemd-binfmt.service
coredump: rework coredumping logic This reworks the coredumping logic so that the coredump handler invoked from the kernel only collects runtime data about the crashed process, and then submits it for processing to a socket-activate coredump service, which extracts a stacktrace and writes the coredump to disk. This has a number of benefits: the disk IO and stack trace generation may take a substantial amount of resources, and hence should better be managed by PID 1, so that resource management applies. This patch uses RuntimeMaxSec=, Nice=, OOMScoreAdjust= and various sandboxing settings to ensure that the coredump handler doesn't take away unbounded resources from normally priorized processes. This logic is also nice since this makes sure the coredump processing and storage is delayed correctly until /var/systemd/coredump is mounted and writable. Fixes: #2286
2016-02-08 23:16:08 +03:00
/systemd-coredump@.service
firstboot: add new component to query basic system settings on first boot, or when creating OS images offline A new tool "systemd-firstboot" can be used either interactively on boot, where it will query basic locale, timezone, hostname, root password information and set it. Or it can be used non-interactively from the command line when prepareing disk images for booting. When used non-inertactively the tool can either copy settings from the host, or take settings on the command line. $ systemd-firstboot --root=/path/to/my/new/root --copy-locale --copy-root-password --hostname=waldi The tool will be automatically invoked (interactively) now on first boot if /etc is found unpopulated. This also creates the infrastructure for generators to be notified via an environment variable whether they are running on the first boot, or not.
2014-07-07 17:05:37 +04:00
/systemd-firstboot.service
units: rename fsck@.service to systemd-fsck@.service The rule is that units that encapsulate our own code are prefixed with "systemd-". Since the fsck units invoke our own code, hence add the missing prefix. Since a long long time the fsck units didn't invoke the naked fsck binaries anymore, and it is unlikely that this well ever change. On the opposite: the code in systemd-fsck will probably get more complex over time to handle fsck progress to plymouth forwarding. Same for quotacheck (but not quotaon!)
2012-06-25 15:47:45 +04:00
/systemd-fsck-root.service
bus: install systemd-bus-proxyd unit files for compatibility with dbus1
2013-12-13 23:29:35 +04:00
/systemd-fsck@.service
machine-id-commit: add unit file The unit file only active the machine-id-commit helper if /etc is mounted writable and /etc/machine-id is an independant mount point (should be a tmpfs).
2014-11-24 12:12:06 +03:00
/systemd-machine-id-commit.service
units: rename halt/hibernate/kexec/poweroff/reboot/suspend to systed-xxx These service units also execute our own code, hence rename the accordingly and prefix them with systemd-
2012-06-25 16:24:56 +04:00
/systemd-halt.service
containers: systemd exits with non-zero code When a systemd service running in a container exits with a non-zero code, it can be useful to terminate the container immediately and get the exit code back to the host, when systemd-nspawn returns. This was not possible to do. This patch adds the following to make it possible: - Add a read-only "ExitCode" property on PID 1's "Manager" bus object. By default, it is 0 so the behaviour stays the same as previously. - Add a method "SetExitCode" on the same object. The method fails when called on baremetal: it is only allowed in containers or in user session. - Add support in systemctl to call "systemctl exit 42". It reuses the existing code for user session. - Add exit.target and systemd-exit.service to the system instance. - Change main() to actually call systemd-shutdown to exit() with the correct value. - Add verb 'exit' in systemd-shutdown with parameter --exit-code - Update systemctl manpage. I used the following to test it: | $ sudo rkt --debug --insecure-skip-verify run \ | --mds-register=false --local docker://busybox \ | --exec=/bin/chroot -- /proc/1/root \ | systemctl --force exit 42 | ... | Container rkt-895a0cba-5c66-4fa5-831c-e3f8ddc5810d failed with error code 42. | $ echo $? | 42 Fixes https://github.com/systemd/systemd/issues/1290
2015-09-18 14:37:34 +03:00
/systemd-exit.service
bus: install systemd-bus-proxyd unit files for compatibility with dbus1
2013-12-13 23:29:35 +04:00
/systemd-hibernate.service
/systemd-hostnamed.service
/systemd-hybrid-sleep.service
import: introduce new mini-daemon systemd-importd, and make machinectl a client to it The old "systemd-import" binary is now an internal tool. We still use it as asynchronous backend for systemd-importd. Since the import tool might require some IO and CPU resources (due to qcow2 explosion, and decompression), and because we might want to run it with more minimal priviliges we still keep it around as the worker binary to execute as child process of importd. machinectl now has verbs for pulling down images, cancelling them and listing them.
2015-01-22 05:57:15 +03:00
/systemd-importd.service
bus: install systemd-bus-proxyd unit files for compatibility with dbus1
2013-12-13 23:29:35 +04:00
/systemd-initctl.service
journal-remote: add units and read certs from default locations
2014-03-31 07:08:02 +04:00
/systemd-journal-catalog-update.service
bus: install systemd-bus-proxyd unit files for compatibility with dbus1
2013-12-13 23:29:35 +04:00
/systemd-journal-flush.service
/systemd-journal-gatewayd.service
journal-remote: add units and read certs from default locations
2014-03-31 07:08:02 +04:00
/systemd-journal-remote.service
/systemd-journal-upload.service
bus: install systemd-bus-proxyd unit files for compatibility with dbus1
2013-12-13 23:29:35 +04:00
/systemd-journald.service
units: rename halt/hibernate/kexec/poweroff/reboot/suspend to systed-xxx These service units also execute our own code, hence rename the accordingly and prefix them with systemd-
2012-06-25 16:24:56 +04:00
/systemd-kexec.service
bus: install systemd-bus-proxyd unit files for compatibility with dbus1
2013-12-13 23:29:35 +04:00
/systemd-localed.service
/systemd-logind.service
/systemd-machined.service
/systemd-modules-load.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
journal-remote: add units and read certs from default locations
2014-03-31 07:08:02 +04:00
/systemd-networkd.service
units: make networkd pull in its own .busname unit The daemon requires the busname unit to operate (on kdbus systems), since it contains the policy that allows it to acquire its service name. This fixes https://bugs.freedesktop.org/show_bug.cgi?id=90287
2015-05-15 23:59:24 +03:00
/systemd-networkd.service.m4
bus: install systemd-bus-proxyd unit files for compatibility with dbus1
2013-12-13 23:29:35 +04:00
/systemd-nspawn@.service
/systemd-poweroff.service
/systemd-quotacheck.service
/systemd-random-seed.service
/systemd-reboot.service
remount: consolidate remount-api-vfs and remount-rootfs into one This has the advantage of removing a confusing warning by mount if the root directory is not listed in fstab.
2012-04-24 18:42:42 +04:00
/systemd-remount-fs.service
resolved: add daemon to manage resolv.conf Also remove the equivalent functionality from networkd.
2014-05-19 00:10:48 +04:00
/systemd-resolved.service
resolved: Do not add .busname dependencies, when compiling without kdbus.
2015-03-17 18:37:07 +03:00
/systemd-resolved.service.m4
hibernate-resume: add a tool to write a device node's major:minor to /sys/power/resume. This can be used to initiate a resume from hibernation by path to a swap device containing the hibernation image. The respective templated unit is also added. It is instantiated using path to the desired resume device.
2014-08-27 00:17:44 +04:00
/systemd-hibernate-resume@.service
rfkill: rework and make it listen on /dev/rfkill With this rework we introduce systemd-rfkill.service as singleton that is activated via systemd-rfkill.socket that listens on /dev/rfkill. That way, we get notified each time a new rfkill device shows up or changes state, in which case we restore and save its current setting to disk. This is nicer than the previous logic, as this means we save/restore state even of rfkill devices that are around only intermittently, and save/restore the state even if the system is shutdown abruptly instead of cleanly. This implements what I suggested in #1019 and obsoletes it.
2015-10-01 15:32:48 +03:00
/systemd-rfkill.service
bus: install systemd-bus-proxyd unit files for compatibility with dbus1
2013-12-13 23:29:35 +04:00
/systemd-suspend.service
/systemd-sysctl.service
units: rebuild /etc/passwd, the udev hwdb and the journal catalog files on boot Only when necessary of course, nicely guarded with the new ConditionNeedsUpdate= condition we added.
2014-06-13 15:10:30 +04:00
/systemd-sysusers.service
bus: install systemd-bus-proxyd unit files for compatibility with dbus1
2013-12-13 23:29:35 +04:00
/systemd-timedated.service
timesyncd: add unit and man page
2014-04-29 10:57:51 +04:00
/systemd-timesyncd.service
bus: install systemd-bus-proxyd unit files for compatibility with dbus1
2013-12-13 23:29:35 +04:00
/systemd-tmpfiles-clean.service
/systemd-tmpfiles-setup-dev.service
/systemd-tmpfiles-setup.service
/systemd-tmpfiles.service
systemd-hwdb: introduce new tool This pulls out the hwdb managment from udevadm into an independent tool. The old code is left in place for backwards compatibility, and easy of testing, but all documentation is dropped to encourage use of the new tool instead.
2014-12-16 02:48:24 +03:00
/systemd-hwdb-update.service
udev: install udevd as /usr/lib/systemd/systemd-udevd
2012-04-17 01:32:22 +04:00
/systemd-udev-settle.service
/systemd-udev-trigger.service
units: Rename systemd-udev.service to systemd-udevd.service This naming convention is more inline with other systemd daemon unit names (systemd-logind.service, systemd-localed.service etc) The companion .socket units have also been renamed, however the -trigger and -settle units keep their current name as these are not directly related to daemon process itself.
2012-07-02 23:35:14 +04:00
/systemd-udevd.service
journal-remote: add units and read certs from default locations
2014-03-31 07:08:02 +04:00
/systemd-update-done.service
bus: install systemd-bus-proxyd unit files for compatibility with dbus1
2013-12-13 23:29:35 +04:00
/systemd-update-utmp-runlevel.service
/systemd-update-utmp.service
/systemd-user-sessions.service
/systemd-vconsole-setup.service
fstab-generator: add support for volatile boots This adds support for a new kernel command line option "systemd.volatile=" that provides the same functionality that systemd-nspawn's --volatile= switch provides, but for host systems (i.e. systems booting with a kernel). It takes the same parameter and has the same effect. In order to implement systemd.volatile=yes a new service systemd-volatile-root.service is introduced that only runs in the initrd and rearranges the root directory as needed to become a tmpfs instance. Note that systemd.volatile=state is implemented different: it simply generates a var.mount unit file that is part of the normal boot and has no effect on the initrd execution. The way this is implemented ensures that other explicit configuration for /var can always override the effect of these options. Specifically, the var.mount unit is generated in the "late" generator directory, so that it only is in effect if nothing else overrides it.
2016-12-13 14:45:19 +03:00
/systemd-volatile-root.service
units: .gitignore: units - ignore tmp.mount This is a follow-up to 409c2a13fd656.
2015-10-15 20:28:07 +03:00
/tmp.mount
gitignore: add back user@.service
2013-12-28 08:54:19 +04:00
/user@.service
Copy Permalink