summaryrefslogtreecommitdiff
path: root/units
AgeCommit message (Collapse)Author
2013-04-01Do no isolate in case of emergency or severe problemsDr. Tilmann Bubeck
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
2013-03-31units/user: default.target must be isolatableZbigniew Jędrzejewski-Szmek
... Activating default unit: default.target Default target could not be isolated, starting instead: Operation refused, unit may not be isolated.
2013-03-29units: fix network-online.target fieldsLennart Poettering
2013-03-29unit: replace remote-fs-setup.target by network-online.targetLennart Poettering
https://bugzilla.redhat.com/show_bug.cgi?id=787314
2013-03-26units: disallow manual starting of passive unitsLennart Poettering
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.
2013-03-26units: downgrade dependency on sockets.target/timers.target/paths.target by ↵Lennart Poettering
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.
2013-03-25units: there is no point in pulling in ordering 'provides'-style targetsLennart Poettering
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.
2013-03-25units: introduce remote-fs-setup.target to pull in dependencies from remote ↵Lennart Poettering
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.
2013-03-25Revert "remote-fs.target: want remote-fs-pre.target"Lennart Poettering
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.
2013-03-25units: and also, order all early-boot sockets before sockets.targetLennart Poettering
2013-03-25units: order all udev services before sysinit.target, tooLennart Poettering
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.
2013-03-25units: introduce new timers.target and paths.target to hook timer/path units ↵Lennart Poettering
into for boot
2013-03-25build-sys: add missing sed substitution for DEBUGTTYKay Sievers
2013-03-25build-sys: configurable debug shell tty pathUmut Tezduyar
2013-03-23udevd: ensure static nodes are created before local-fs mountFrederic Crozat
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.
2013-03-22Update user session unit template.Auke Kok
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
2013-03-23Revert "units: ignore systemd-sysctl on shutdown"Lennart Poettering
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=.
2013-03-16units: initrd, multi-user - add a few more words to Description=Kay Sievers
2013-03-15units: ignore systemd-sysctl on shutdownUmut Tezduyar
No need to try to stop systemd-sysctl on shutdown as this service doesn't have ExecStop= anyways.
2013-03-15Make initrd.target the default target in the initrdHarald Hoyer
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
2013-03-13add initrd-fs.target and root-fs.targetHarald Hoyer
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.
2013-03-12remote-fs.target: want remote-fs-pre.targetHarald Hoyer
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.
2013-03-12udevd: sort into sysinit instead of basic targetKay Sievers
2013-03-11Update .gitignoreMichael Biebl
for the changes in 7b40ce553f0ec9487077e53f5bdc46580025901c
2013-03-11Move udevadm to rootbindirMichael Biebl
The udevadm utility is needed during early boot, so move it to rootbindir to support split-/usr configurations.
2013-03-09build-sys: don't hard-code binary paths in initrd-*.serviceMichael Biebl
Instead use @bindir@ for udevadm and @rootbindir@ for systemctl.
2013-03-06units: run systemd-ask-password-console.service after ↵Harald Hoyer
systemd-vconsole-setup.service
2013-03-06initrd-parse-etc.servic: force start local-fs.targetHarald Hoyer
2013-03-06Revert "add initrd-fs.target and initrd-fs-pre.target"Harald Hoyer
This reverts commit 39b83cdab37623a546344622db9bbbc784c15df5.
2013-03-06Revert "units/initrd-*: require initrd-fs.target rather than local-fs.target"Harald Hoyer
This reverts commit 7d89ce303fb59743a4392eeb3110c00f100172ca.
2013-03-05journal: make gatewayd run under its own user IDLennart Poettering
2013-03-04units/initrd-*: require initrd-fs.target rather than local-fs.targetHarald Hoyer
2013-03-04add initrd-fs.target and initrd-fs-pre.targetHarald Hoyer
2013-03-01initrd: add unit files needed for basic systemd-in-initrd supportTom Gundersen
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>
2013-01-29build-sys: keep intermediate filesZbigniew Jędrzejewski-Szmek
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-16service: ignore dependencies on $syslog and $local_fs in LSB scriptsLennart Poettering
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.
2013-01-16service: sysv - remove distribution specific targetsKay Sievers
Systemd should not introduce any new facilities. Distributions which still need to support their non-standard/legacy facilities should add them as patches to their packaging. The following facilities are no longer recognized: $x-display-manager $mail-transfer-agent $mail-transport-agent $mail-transfer-agent $smtp $null This target is no longer available: mail-transfer-agent.target
2013-01-15units: add reference to new wiki page to all api mount unitsLennart Poettering
2013-01-15man: link in API FS documentation from the wikiLennart Poettering
2013-01-15man: link in wiki documentation about network.targetLennart Poettering
2013-01-04units: always use sulogin in rescue.serviceLennart Poettering
sushell makes much less sense than sulogin. If distros want to stick to sushell they should patch this downstream.
2013-01-04units: drop distro specific stuff from unitsLennart Poettering
Since rc-local is now enabled via the SysV compatibility we should only refer to it based on that too.
2013-01-04build-sys: make rc-local support part of SYSV compatLennart Poettering
This also drops automatic selection of the rc local scripts based on the local distro. Distributions now should specify the paths of the rc-local and halt-local scripts on the configure command line.
2012-12-31units: add CAP_DAC_OVERRIDE+CAP_SYS_PTRACE to hostnamed so that detection of ↵Lennart Poettering
virtualization works
2012-12-14Remove frugalware display-manager.serviceTollef Fog Heen
Frugalware are shipping their own .service file now, so stop shipping it here. This effectively reverts 196e3fa74a88a04b0ecec7d3af648287dd088f8a
2012-11-20unit: link up getty configuration from man page and unit filesLennart Poettering
2012-11-16journal: recommend journalctl -x more oftenLennart Poettering
2012-10-31service: drop special HTTP server target, as it is a bad idea anf Fedora ↵Lennart Poettering
specific This was premarily intended to support the LSB facility $httpd which is only known by Fedora, and a bad idea since it lacks any real-life usecase. Similar, drop support for some other old Fedora-specific facilities. Also, document the rules for introduction of new facilities, to clarify the situation for the future.
2012-10-29units: agetty overrides TERMMichal Schmidt
Environment=TERM=... has no effect on agetty who sets it by itself. To really set TERM to a specified value, it has to be given on the command line. https://bugzilla.redhat.com/show_bug.cgi?id=870622
2012-10-28units: teach m4 scripts in units/ about Debian's rc.localRamkumar Ramachandra
This makes the behaviour wrt. to rc[-.]local consistent between various distributions supporting it.