summaryrefslogtreecommitdiff
path: root/units
AgeCommit message (Collapse)Author
2014-01-16sd-dhcp-client/networkd: add transient hostname supportTom Gundersen
2014-01-08Improve messages about user mode a bitZbigniew Jędrzejewski-Szmek
2014-01-08pam_systemd: export DBUS_SESSION_BUS_ADDRESSKay Sievers
2014-01-08bus-driverd: support user modeKay Sievers
2014-01-08bus-proxyd: support --user bus addressKay Sievers
2014-01-07bus-proxyd: --user -- add Accept=yes to socketKay Sievers
2014-01-07core: --user -- add basic.target an sort against it like --system doesKay Sievers
2014-01-07bus-proxyd: fix socket pathKay Sievers
2013-12-30tmpfiles: rename --unsafe to --bootZbigniew Jędrzejewski-Szmek
As suggested by Kay, it is better to describe what is done, not what might happen.
2013-12-28gitignore: add back user@.serviceMarc-Antoine Perennou
2013-12-27build-sys: fix generation of user@.serviceZbigniew Jędrzejewski-Szmek
2013-12-27units: user@.service: fix user bus pathMantas Mikulėnas
2013-12-24tmpfiles: introduce the concept of unsafe operationsZbigniew Jędrzejewski-Szmek
Various operations done by systemd-tmpfiles may only be safely done at boot (e.g. removal of X lockfiles in /tmp, creation of /run/nologin). Other operations may be done at any point in time (e.g. setting the ownership on /{run,var}/log/journal). This distinction is largely orthogonal to the type of operation. A new switch --unsafe is added, and operations which should only be executed during bootup are marked with an exclamation mark in the configuration files. systemd-tmpfiles.service is modified to use this switch, and guards are added so it is hard to re-start it by mistake. If we install a new version of systemd, we actually want to enforce some changes to tmpfiles configuration immediately. This should now be possible to do safely, so distribution packages can be modified to execute the "safe" subset at package installation time. /run/nologin creation is split out into a separate service, to make it easy to override. https://bugzilla.redhat.com/show_bug.cgi?id=1043212 https://bugzilla.redhat.com/show_bug.cgi?id=1045849
2013-12-24man,units: tmpfiles.d(5) cleanupZbigniew Jędrzejewski-Szmek
Condition for /lib (necessary for split /usr) was missing from the unit. Some changes which were done in tmpfiles.d(5) were not carried over to systemd-tmpfiles(1). Also use markup where possible.
2013-12-23units: systemd-machined now exits on idle and we shouldn't try to restart it ↵Lennart Poettering
then
2013-12-23units: limit caps for bus proxyd and driverd servicesLennart Poettering
2013-12-21bus: send status message from proxyd to systemd about client we are working forLennart Poettering
2013-12-18units: when spawning a getty configure TERM explicitlyLennart Poettering
This way we can make use of our logic to automatically determine an appropriate TERM for a specific tty.
2013-12-18units: run systemd-networkd.service only if CAP_NET_ADMIN capability is aroundLennart Poettering
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.
2013-12-17bus: install unit files for new driver serviceLennart Poettering
2013-12-16bus: fix typo in systemd-bus-proxydKay Sievers
2013-12-16units: properly make bus proxy socket of type Accept=yesLennart Poettering
2013-12-13bus: install systemd-bus-proxyd unit files for compatibility with dbus1Lennart Poettering
2013-12-11units: don't run readahead done timers in containersLennart Poettering
We don't run the collector in the container either, hence we don't need to stop it either.
2013-12-11journald: port to sd-event and enable watchdog supportLennart Poettering
2013-12-11event: hook up sd-event with the service watchdog logicLennart Poettering
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.
2013-12-03units: ship busname units for the bus activated services we shipLennart Poettering
2013-12-03units: install busnames.target by defaultLennart Poettering
2013-11-26core: replace OnFailureIsolate= setting by a more generic OnFailureJobMode= ↵Lennart Poettering
setting and make use of it where applicable
2013-11-23networkd: use Type=notifyTom Gundersen
Also start earlier during boot.
2013-11-21timer: make timer accuracy configurableLennart Poettering
And make it default to 1min
2013-11-09man,units: fix installation of systemd-nspawn@.service and add exampleZbigniew Jędrzejewski-Szmek
2013-11-09networkd: add a basic network daemonTom Gundersen
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
2013-10-31machinectl: add new command to spawn a getty inside a containerLennart Poettering
2013-10-19Remove FsckPassNo from systemd-fsck-root.serviceThomas Bächler
2013-10-19fstab-generator: Generate explicit dependencies on systemd-fsck@.service ↵Thomas Bächler
instead of using FsckPassNo [tomegun: * order all fsck instances after fsck-root * check for OOM * added notes in the manpages]
2013-10-17static-nodes: don't call mkdirTom Gundersen
This is no longer necessary with kmod-15. Bump the requirement.
2013-10-14rfkill: add new rfkill tool to save/restore rfkill state across rebootsLennart Poettering
This works analogous to the existing backlight and random seed services
2013-10-02execute.c: always set $SHELLZbigniew Jędrzejewski-Szmek
In e6dca81 $SHELL was added to user@.service. Let's instead provide it to all units which have a user.
2013-10-02fix lingering references to /var/lib/{backlight,random-seed}Dave Reisner
This should have been part of ef5bfcf668e6029faa78534dfe.
2013-10-01logind: run with CAP_SYS_ADMINDavid Herrmann
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.
2013-10-01units: Add SHELL environment variableEvan Callicoat
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.
2013-09-28kmod-static-nodes: condition execution on modules.devnameDave Reisner
2013-09-23Fix obsolete references to systemd-random-seed-load.serviceEelco Dolstra
This service was merged with systemd-random-seed-save.service in c35b956d34bbb8bb208e49e45de2c103ca11911c.
2013-09-17nspawn: update unit fileLennart Poettering
ControlGroup= is obsolete, so let's drop it from the default nspawn unit file.
2013-09-11Add pam configuration to allow user sessions to work out of the boxZbigniew Jędrzejewski-Szmek
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.
2013-09-11filesystem targets: disable default dependenciesTom Gundersen
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>
2013-08-22use CAP_MKNOD ConditionCapabilityKhem Raj
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>
2013-08-20units: disable kmod-static-nodes.service in containersZbigniew Jędrzejewski-Szmek
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
2013-08-17udev: replace CAP_MKNOD by writable /sys conditionKay Sievers