summaryrefslogtreecommitdiff
path: root/units
Commit message (Collapse)AuthorAge
* units: systemd-machined now exits on idle and we shouldn't try to restart it ↵Lennart Poettering2013-12-23
| | | | then
* units: limit caps for bus proxyd and driverd servicesLennart Poettering2013-12-23
|
* bus: send status message from proxyd to systemd about client we are working forLennart Poettering2013-12-21
|
* units: when spawning a getty configure TERM explicitlyLennart Poettering2013-12-18
| | | | | This way we can make use of our logic to automatically determine an appropriate TERM for a specific tty.
* units: run systemd-networkd.service only if CAP_NET_ADMIN capability is aroundLennart Poettering2013-12-18
| | | | | | | | | | | | This has the effect that systemd-networkd won't run in containers without network namespacing wher CAP_NET_ADMIN is (usually) not available. It will still run in containers with network namespacing on (where CAP_NET_ADMIN is usually avilable). We might remove this condition check again if networkd provides services to apps that also are useful in containers lacking network namespacing, however, as long as it doesn't it should be handled like udevd and be excluded in such containers.
* bus: install unit files for new driver serviceLennart Poettering2013-12-17
|
* bus: fix typo in systemd-bus-proxydKay Sievers2013-12-16
|
* units: properly make bus proxy socket of type Accept=yesLennart Poettering2013-12-16
|
* bus: install systemd-bus-proxyd unit files for compatibility with dbus1Lennart Poettering2013-12-13
|
* units: don't run readahead done timers in containersLennart Poettering2013-12-11
| | | | | We don't run the collector in the container either, hence we don't need to stop it either.
* journald: port to sd-event and enable watchdog supportLennart Poettering2013-12-11
|
* event: hook up sd-event with the service watchdog logicLennart Poettering2013-12-11
| | | | | | | | | | | | | Adds a new call sd_event_set_watchdog() that can be used to hook up the event loop with the watchdog supervision logic of systemd. If enabled and $WATCHDOG_USEC is set the event loop will ping the invoking systemd daemon right after coming back from epoll_wait() but not more often than $WATCHDOG_USEC/4. The epoll_wait() will sleep no longer than $WATCHDOG_USEC/4*3, to make sure the service manager is called in time. This means that setting WatchdogSec= in a .service file and calling sd_event_set_watchdog() in your daemon is enough to hook it up with the watchdog logic.
* units: ship busname units for the bus activated services we shipLennart Poettering2013-12-03
|
* units: install busnames.target by defaultLennart Poettering2013-12-03
|
* core: replace OnFailureIsolate= setting by a more generic OnFailureJobMode= ↵Lennart Poettering2013-11-26
| | | | setting and make use of it where applicable
* networkd: use Type=notifyTom Gundersen2013-11-23
| | | | Also start earlier during boot.
* timer: make timer accuracy configurableLennart Poettering2013-11-21
| | | | And make it default to 1min
* man,units: fix installation of systemd-nspawn@.service and add exampleZbigniew Jędrzejewski-Szmek2013-11-09
|
* networkd: add a basic network daemonTom Gundersen2013-11-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | This daemon listens for and configures network devices tagged with 'systemd-networkd'. By default, no devices are tagged so this daemon can safely run in parallel with existing network daemons/scripts. Networks are configured in /etc/systemd/network/*.network. The first .network file that matches a given link is applied. The matching logic is similar to the one for .link files, but additionally supports matching on interface name. The mid-term aim is to provide an alternative to ad-hoc scripts currently used in initrd's and for wired setups that don't change much (e.g., as seen on servers/and some embedded systems). Currently, static addresses and a gateway can be configured. Example .network file: [Match] Name=wlp2s0 [Network] Description=My Network Gateway=192.168.1.1 Address=192.168.1.23/24 Address=fe80::9aee:94ff:fe3f:c618/64
* machinectl: add new command to spawn a getty inside a containerLennart Poettering2013-10-31
|
* Remove FsckPassNo from systemd-fsck-root.serviceThomas Bächler2013-10-19
|
* fstab-generator: Generate explicit dependencies on systemd-fsck@.service ↵Thomas Bächler2013-10-19
| | | | | | | | | instead of using FsckPassNo [tomegun: * order all fsck instances after fsck-root * check for OOM * added notes in the manpages]
* static-nodes: don't call mkdirTom Gundersen2013-10-17
| | | | This is no longer necessary with kmod-15. Bump the requirement.
* rfkill: add new rfkill tool to save/restore rfkill state across rebootsLennart Poettering2013-10-14
| | | | This works analogous to the existing backlight and random seed services
* execute.c: always set $SHELLZbigniew Jędrzejewski-Szmek2013-10-02
| | | | | In e6dca81 $SHELL was added to user@.service. Let's instead provide it to all units which have a user.
* fix lingering references to /var/lib/{backlight,random-seed}Dave Reisner2013-10-02
| | | | This should have been part of ef5bfcf668e6029faa78534dfe.
* logind: run with CAP_SYS_ADMINDavid Herrmann2013-10-01
| | | | | | | | | DRM Master access requires CAP_SYS_ADMIN, yay! Add it to the capability bounding set for systemd-logind. As CAP_SYS_ADMIN actually allows a huge set of actions, this mostly renders the restriction-set useless. Anyway, patches are already pending to reduce the restriction on the kernel side. But these won't really make it into any stable-release so for now we're stuck with CAP_SYS_ADMIN.
* units: Add SHELL environment variableEvan Callicoat2013-10-01
| | | | | | | | With the advent of systemd --user sessions, it's become very interesting to spawn X as a user unit, as well as accompanying processes that may have previously been in a .xinitrc/.xsession, or even just to replace a collection of XDG/GDM/KDM/etc session files with independent systemd --user units. The simplest case here would be to login on a tty, with the traditional /usr/sbin/login "login manager". However, systemd --user (spawned by user@.service) is at the top level of the slice for the user, and does not inherit any environment variables from the login process. Given the number of common applications which rely on SHELL being set in the environment, it seems like the cleanest way to provide this variable is to set it to %s in the user@.service. Ideally in the long-term, applications which rely on SHELL being set should be fixed to just grab it from getpwnam() or similar, but until that becomes more common, I propose this simple change to make user sessions a little bit nicer out of the box.
* kmod-static-nodes: condition execution on modules.devnameDave Reisner2013-09-28
|
* Fix obsolete references to systemd-random-seed-load.serviceEelco Dolstra2013-09-23
| | | | | This service was merged with systemd-random-seed-save.service in c35b956d34bbb8bb208e49e45de2c103ca11911c.
* nspawn: update unit fileLennart Poettering2013-09-17
| | | | | ControlGroup= is obsolete, so let's drop it from the default nspawn unit file.
* Add pam configuration to allow user sessions to work out of the boxZbigniew Jędrzejewski-Szmek2013-09-11
| | | | | | | | | | | | | | | | | | | systemd-logind will start user@.service. user@.service unit uses PAM with service name 'systemd-user' to perform account and session managment tasks. Previously, the name was 'systemd-shared', it is now changed to 'systemd-user'. Most PAM installations use one common setup for different callers. Based on a quick poll, distributions fall into two camps: those that have system-auth (Redhat, Fedora, CentOS, Arch, Gentoo, Mageia, Mandriva), and those that have common-auth (Debian, Ubuntu, OpenSUSE). Distributions that have system-auth have just one configuration file that contains auth, password, account, and session blocks, and distributions that have common-auth also have common-session, common-password, and common-account. It is thus impossible to use one configuration file which would work for everybody. systemd-user now refers to system-auth, because it seems that the approach with one file is more popular and also easier, so let's follow that.
* filesystem targets: disable default dependenciesTom Gundersen2013-09-11
| | | | | | | This means we can use default dependencies on mount units without having to get them automatically ordered before the filesystem targets. Reported-by: Thomas Baechler <thomas@archlinux.org>
* use CAP_MKNOD ConditionCapabilityKhem Raj2013-08-22
| | | | | | | | | | | | Fixes errors seen when booting VMs on QEMU like systemd[1]: kmod-static-nodes.service: main process exited, code=exited, status=203/EXEC systemd[1]: Failed to start Create list of required static device nodes for the current kernel. systemd[1]: Unit kmod-static-nodes.service entered failed state. Make sure that mknod capability is available Signed-off-by: Khem Raj <raj.khem@gmail.com>
* units: disable kmod-static-nodes.service in containersZbigniew Jędrzejewski-Szmek2013-08-20
| | | | | | | | | | | | Fixes https://bugzilla.redhat.com/show_bug.cgi?id=998122. Note: upstream kmod has a patch [1] to exit with a warning if modules.devname is missing. We could use new %v specifier to make this service conditional on the existence of this file, but this could mask a kernel installation error, hence we should let kmod run even if the file doesn't exist. [1] http://git.kernel.org/cgit/utils/kernel/kmod/kmod.git/commit/?id=ae17710117
* udev: replace CAP_MKNOD by writable /sys conditionKay Sievers2013-08-17
|
* units: make fsck units remain after exitZbigniew Jędrzejewski-Szmek2013-08-15
| | | | | | | | Without this, fsck would be re-run if any other service which pulls in a target requiring one of the mounts was started after fsck was done but before the initial transaction was done. https://bugs.freedesktop.org/show_bug.cgi?id=66784
* typo fixes in man and commentsThomas Hindoe Paaboel Andersen2013-08-15
|
* sysctl: allow overwriting of values specified in "later" filesKay Sievers2013-08-15
|
* backlight: instead of syspath use sysname for identifying backlight devicesLennart Poettering2013-08-14
| | | | This makes the description string of the backlight service a bit nicer.
* backlight: add minimal tool to save/restore screen brightness across rebootsLennart Poettering2013-08-14
| | | | | | | | | | As many laptops don't save/restore screen brightness across reboots, let's do this in systemd with a minimal tool, that restores the brightness as early as possible, and saves it as late as possible. This will cover consoles and graphical logins, but graphical desktops should do their own per-user stuff probably. This only touches firmware brightness controls for now.
* core: optionally send SIGHUP in addition to the configured kill signalLennart Poettering2013-07-30
| | | | This is useful to fake session ends for processes like shells.
* tmpfiles-setup: exclude /dev prefixes filesDave Reisner2013-07-24
| | | | Fixes Arch Linux bug: https://bugs.archlinux.org/task/36259
* kmod-static-nodes: remain after exitTom Gundersen2013-07-22
|
* systemd-tmpfiles-setup-dev: remain after exitTom Gundersen2013-07-22
| | | | | | Without this, tmpfiles-setpu-dev would be re-run if any other service, which pulls in basic.target, was started after setup-dev was finished and before basic.target was active.
* machined: run machined at minimal capabilitiesLennart Poettering2013-07-19
|
* units: add references to bus API documentation to logind+machinedLennart Poettering2013-07-19
|
* remove /run/initramfs/root-fsck logicHarald Hoyer2013-07-17
| | | | | | | dracut uses systemd in the initramfs and does not write these files anymore. The state of the root fsck is serialized.
* units: do not special-case getty@tty1.service installationZbigniew Jędrzejewski-Szmek2013-07-13
| | | | | | Since a long while we can use "systemctl enable getty@tty1.service" which does the right thing, so there's no need to abuse Alias= for installation.
* static-nodes: don't hardcode path to mkdirTom Gundersen2013-07-12
|