summaryrefslogtreecommitdiff
path: root/units
Commit message (Collapse)AuthorAge
* logind: add infrastructure to keep track of machines, and move to slicesLennart Poettering2013-06-20
| | | | | | | | | | | | | | | | | | | | - This changes all logind cgroup objects to use slice objects rather than fixed croup locations. - logind can now collect minimal information about running VMs/containers. As fixed cgroup locations can no longer be used we need an entity that keeps track of machine cgroups in whatever slice they might be located. Since logind already keeps track of users, sessions and seats this is a trivial addition. - nspawn will now register with logind and pass various bits of metadata along. A new option "--slice=" has been added to place the container in a specific slice. - loginctl gained commands to list, introspect and terminate machines. - user.slice and machine.slice will now be pulled in by logind.service, since only logind.service requires this slice.
* units: add default units for system.slice, user.slice, machine.sliceLennart Poettering2013-06-18
|
* units: cleanup agetty command lineKarel Zak2013-06-04
| | | | | | | | | * baud rate is optional and unnecessary for virtual terminals * term type is optional (default is 'linux' for virtual terminals and 'vt102' for serial lines) * long options are more user-friendly ... all this is supported since util-linux v2.20 (Aug 2011).
* utmp: turn systemd-update-utmp-shutdown.service into a normal runtime serviceLennart Poettering2013-05-16
| | | | | | | | | | With this change systemd-update-utmp-shutdown.service is replaced by systemd-update-utmp.service which is started at boot and stays around until shutdown. This allows us to properly order the unit against both /var/log and auditd. https://bugzilla.redhat.com/show_bug.cgi?id=853104 https://bugs.freedesktop.org/show_bug.cgi?id=64365
* units: rework systemd-random-seed-{load,save}.service to be a single serviceLennart Poettering2013-05-15
| | | | | | That way ordering it with MountsRequiredFor= works properly, as this no longer results in mount units start requests to be added to the shutdown transaction that conflict with stop requests for the same unit.
* systemctl does not expand %u, so revert back to %IAuke Kok2013-05-09
| | | | | The description field is only displayed by systemctl, and it can't expand %u properly (it will always display "root").
* units: add an easy-to-use unit template file systemd-nspawn@.service for ↵Lennart Poettering2013-04-30
| | | | running containers as system services
* units: update user@.service to reflect new user cgroup pathsLennart Poettering2013-04-23
|
* man: link systemd-tmpfiles-setup-dev.serviceUmut Tezduyar2013-04-23
|
* units: rename systemd-static-nodes -> systemd-tmpfiles-setup-devTom Gundersen2013-04-22
| | | | This is really just a special case of systemd-tmpfiles-setup, moreover it could easily create more than static nodes.
* readahead: let readahead run for a little longerLennart Poettering2013-04-17
| | | | | Especially slower systems need more than 10s for starting the session, so let's bump this to 30s.
* bus: rename KDBUS_CMD_FNAME_POLICY_NONE -> KDBUS_CMD_FNAME_POLICY_OPENKay Sievers2013-04-12
|
* tmpfiles: create static device nodes before udev is startedTom Gundersen2013-04-12
| | | | | | | | | | | | | Since v183, the contents of /usr/lib/udev/devices is no longer copied to /dev on boot, rather systemd-tmpfiles should be used instead. However, as systemd-tmpfiles --create is only ran long after udevd has been started, it is no longer possible to use udev rules to assign permissions to the static nodes. This calls systemd-tmpfiles --create early, before udev is started, and restricts the call to /dev, which is known to be mounted already. In the future, this could also take over the creation of static device nodes from systemd-udevd.
* units: fix some left-over mentions of remote-fs-setup.targetLennart Poettering2013-04-09
|
* Do no isolate in case of emergency or severe problemsDr. Tilmann Bubeck2013-04-01
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch changes local-fs.target and systemd-fsck to not use "isolate" when going into emergency. This fixes https://bugzilla.redhat.com/show_bug.cgi?id=810722 The motivation is, that when something wents wrong, we should keep everything as it is, to let the user fix the problem. When isolating we stop a lot of services and therefore change the system heavily so that it gets harder for the user to fix. An example is a crypted partition. When the fsck in a crypted partition fails, it previously used "emergency/start/isolate" which stops cryptsetup. Therefore if the user tries to fsck e.g. /dev/mapper/luks-356c20ae-c7a2-4f1c-ae1d-1d290a91b691 as printed by the failing fsck, then it will not find this device (because it got closed). So please apply this patch to let the user see the failing situation. Thanks! [zj: removed dead isolate param from start_target().] https://bugs.freedesktop.org/show_bug.cgi?id=49463 https://bugzilla.redhat.com/show_bug.cgi?id=810722
* units/user: default.target must be isolatableZbigniew Jędrzejewski-Szmek2013-03-31
| | | | | | ... Activating default unit: default.target Default target could not be isolated, starting instead: Operation refused, unit may not be isolated.
* units: fix network-online.target fieldsLennart Poettering2013-03-29
|
* unit: replace remote-fs-setup.target by network-online.targetLennart Poettering2013-03-29
| | | | https://bugzilla.redhat.com/show_bug.cgi?id=787314
* units: disallow manual starting of passive unitsLennart Poettering2013-03-26
| | | | | | As passive units only are useful for ordering things within the initial transaction there is no point in ever activating them manually, hence refuse it.
* units: downgrade dependency on sockets.target/timers.target/paths.target by ↵Lennart Poettering2013-03-26
| | | | | | | | basic.target There isn't really any need to require any targets but sysinit.target from basic.target, so downgrade sockets.target, paths.target, timers.target.
* units: there is no point in pulling in ordering 'provides'-style targetsLennart Poettering2013-03-25
| | | | | | | | Units such as nss-lookup.target, nss-user-lookup.target, remote-fs-pre.target, local-fs-pre.target, time-sync.target, rpcbind.target are to be pulled in by the implementing services, and that's there only purpose. They should not have any 'active component' otherwise, so let's drop all further deps from these units.
* units: introduce remote-fs-setup.target to pull in dependencies from remote ↵Lennart Poettering2013-03-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | mounts This introduces remote-fs-setup.target independently of remote-fs-pre.target. The former is only for pulling things in, the latter only for ordering. The new semantics: remote-fs-setup.target: is pulled in automatically by all remote mounts. Shall be used to pull in other units that want to run when at least one remote mount is set up. Is not ordered against the actual mount units, in order to allow activation of its dependencies even 'a posteriori', i.e. when a mount is established outside of systemd and is only picked up by it. remote-fs-pre.target: needs to be pulled in automatically by the implementing service, is otherwise not part of the initial transaction. This is ordered before all remote mount units. A service that wants to be pulled in and run before all remote mounts should hence have: a) WantedBy=remote-fs-setup.target -- so that it is pulled in b) Wants=remote-fs-pre.target + Before=remote-fs-pre.target -- so that it is ordered before the mount point, normally.
* Revert "remote-fs.target: want remote-fs-pre.target"Lennart Poettering2013-03-25
| | | | | | | | This reverts commit 6bde0b3220e95a08cefb70846f73b2cf24b7734a. We should not pull in remote-fs-pre.target unconditionally. It's supposed to be pulled in by the implementors of it, rather then its users.
* units: and also, order all early-boot sockets before sockets.targetLennart Poettering2013-03-25
|
* units: order all udev services before sysinit.target, tooLennart Poettering2013-03-25
| | | | | | Not that it would matter much, but let's make things a bit more systematic: early boot services shall order themselves before sysinit.target, and nothing else.
* units: introduce new timers.target and paths.target to hook timer/path units ↵Lennart Poettering2013-03-25
| | | | into for boot
* build-sys: add missing sed substitution for DEBUGTTYKay Sievers2013-03-25
|
* build-sys: configurable debug shell tty pathUmut Tezduyar2013-03-25
|
* udevd: ensure static nodes are created before local-fs mountFrederic Crozat2013-03-23
| | | | | | | static nodes (like /dev/loop-control) are created when systemd-udevd is started and needed to mount loopback devices. Therefore, local-fs-pre.target should be only started after systemd-udevd is started.
* Update user session unit template.Auke Kok2013-03-22
| | | | | | | | | | | While most folks will be using the derivative from user-session-units, I'm updating this one to reflect some of the fixes and things to note about user sessions: - cgroup should be set with "%u" - username instead of %I - set dbus path with %U explicitly too - hint to folks that wish to use MEM_CG features in user sessions - allow unit to be enabled for instances with systemctl enable
* Revert "units: ignore systemd-sysctl on shutdown"Lennart Poettering2013-03-23
| | | | | | | | | | This reverts commit faeffa73a81ab5b59acfadeb571431fb0e42af70. There isn't really much point in dropping the Conflicts= since shutting down this service is basically free as it doesn't have anything running. Also, the patch was incomplete, because shutdown.target was still listed in Before=.
* units: initrd, multi-user - add a few more words to Description=Kay Sievers2013-03-16
|
* units: ignore systemd-sysctl on shutdownUmut Tezduyar2013-03-15
| | | | | No need to try to stop systemd-sysctl on shutdown as this service doesn't have ExecStop= anyways.
* Make initrd.target the default target in the initrdHarald Hoyer2013-03-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | First, rename root-fs.target to initrd-root-fs.target to clarify its usage. Mount units with "x-initrd-rootfs.mount" are now ordered before initrd-root-fs.target. As we sometimes construct /sysroot mounts in /etc/fstab in the initrd, we want these to be mounted before the initrd-root-fs.target is active. initrd.target can be the default target in the initrd. (normal startup) : : v basic.target | ______________________/| / | | sysroot.mount | | | v | initrd-root-fs.target | | | v | initrd-parse-etc.service (custom initrd services) | | v | (sysroot-usr.mount and | various mounts marked | with fstab option | x-initrd.mount) | | | v | initrd-fs.target | | \______________________ | \| v initrd.target | v initrd-cleanup.service isolates to initrd-switch-root.target | v ______________________/| / | | initrd-udevadm-cleanup-db.service | | (custom initrd services) | | | \______________________ | \| v initrd-switch-root.target | v initrd-switch-root.service | v switch-root
* add initrd-fs.target and root-fs.targetHarald Hoyer2013-03-13
| | | | | | | | | | | | | | Instead of using local-fs*.target in the initrd, use root-fs.target for sysroot.mount and initrd-fs.target for /sysroot/usr and friends. Using local-fs.target would mean to carry over the activated local-fs.target to the isolated initrd-switch-root.target and thus in the real root. Having local-fs.target already active after deserialization causes ordering problems with the real root services and targets. We better isolate to targets for initrd-switch-root.target, which are only available in the initrd.
* remote-fs.target: want remote-fs-pre.targetHarald Hoyer2013-03-12
| | | | | | | | | | | | | | | This pulls in remote-fs-pre.target if remote-fs.target is needed. Previously remote-fs-pre.target was not active, if no remote fs was mounted from /etc/fstab. So, every manual remote fs mount was ordered against the inactive remote-fs-pre.target and umount.target. Because remote-fs-pre.target was not active, the remote fs was umounted at umount.target time, which was too late (network already down). Now remote-fs-pre.target is active, even if no remote fs is mounted. On shutdown it is deactivated in the correct order and all manual remote fs mounts also.
* udevd: sort into sysinit instead of basic targetKay Sievers2013-03-12
|
* Update .gitignoreMichael Biebl2013-03-11
| | | | for the changes in 7b40ce553f0ec9487077e53f5bdc46580025901c
* Move udevadm to rootbindirMichael Biebl2013-03-11
| | | | | The udevadm utility is needed during early boot, so move it to rootbindir to support split-/usr configurations.
* build-sys: don't hard-code binary paths in initrd-*.serviceMichael Biebl2013-03-09
| | | | Instead use @bindir@ for udevadm and @rootbindir@ for systemctl.
* units: run systemd-ask-password-console.service after ↵Harald Hoyer2013-03-06
| | | | systemd-vconsole-setup.service
* initrd-parse-etc.servic: force start local-fs.targetHarald Hoyer2013-03-06
|
* Revert "add initrd-fs.target and initrd-fs-pre.target"Harald Hoyer2013-03-06
| | | | This reverts commit 39b83cdab37623a546344622db9bbbc784c15df5.
* Revert "units/initrd-*: require initrd-fs.target rather than local-fs.target"Harald Hoyer2013-03-06
| | | | This reverts commit 7d89ce303fb59743a4392eeb3110c00f100172ca.
* journal: make gatewayd run under its own user IDLennart Poettering2013-03-05
|
* units/initrd-*: require initrd-fs.target rather than local-fs.targetHarald Hoyer2013-03-04
|
* add initrd-fs.target and initrd-fs-pre.targetHarald Hoyer2013-03-04
|
* initrd: add unit files needed for basic systemd-in-initrd supportTom Gundersen2013-03-01
| | | | | | | | | | | | | | | | | | This will: * mount all configured filesystems (typically the rootfs on /sysroot) * reload the configuration to pick up anything from the mounted fs (typically /sysroot/etc/fstab) * mount any newly configured filesystems (typically /usr on /sysroot/usr, if applicable) * shut-down and clean-up any daemons running in the initramfs (typically udevd) * switch-root to /sysroot and start the real init For an example of what files should be included in an initramfs based on this see <https://mailman.archlinux.org/pipermail/arch-projects/2013-February/003628.html>. Cc: Harald Hoyer <harald.hoyer@gmail.com> Cc: Dave Reisner <d@falconindy.com>
* build-sys: keep intermediate filesZbigniew Jędrzejewski-Szmek2013-01-29
| | | | | | | 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.
* service: ignore dependencies on $syslog and $local_fs in LSB scriptsLennart Poettering2013-01-16
| | | | | | | | | | | | | We no longer allow early-boot init scripts, however in late boot the syslog socket and local mounts are established anyway, so let's simplify our dep graph a bit. If $syslog doesn't resolve to syslog.target anymore there's no reason to keep syslog.target around anymore. Let's remove it. Note that many 3rd party service unit files order themselves after syslog.target. These will be dangling dependencies now, which should be unproblematic, however.
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-03 07:12:54 +0000