summaryrefslogtreecommitdiff
path: root/units
AgeCommit message (Collapse)Author
2014-04-24networkd-wait-online: improve interoptability and enable by defaultTom Gundersen
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-22remove bus-driverd, the interface is now handled natively by bus-proxydKay Sievers
2014-04-19networkd: order after udev kernel socketTom Gundersen
Otherwise we will not be able to queuery whether devices are initialized on kdbus enabled systems.
2014-03-26bus: provide org.freedesktop.systemd1.busname for systemd --userKay Sievers
2014-03-24networkd: add CapabilityBoundingSetTom Gundersen
2014-03-24units: networkd shouldn't have PrivateTmp= set, since it runs in early-bootLennart Poettering
/tmp is only available in later boot, and we shouldn't create private subdirs in it hence, while we are still in early boot.
2014-03-20unit: turn off mount propagation for udevdLennart Poettering
Keep mounts done by udev rules private to udevd. Also, document how MountFlags= may be used for this.
2014-03-19core: enable PrivateNetwork= for a number of our long running services where ↵Lennart Poettering
this is useful
2014-03-19units: make use of PrivateTmp=yes and PrivateDevices=yes for all our ↵Lennart Poettering
long-running daemons
2014-03-19busname: introduce Activating directiveDaniel Mack
Add a new config 'Activating' directive which denotes whether a busname is actually registered on the bus. It defaults to 'yes'. If set to 'no', the .busname unit only uploads policy, which will remain active as long as the unit is running.
2014-03-13getty: Start getty on 3270 terminals available on Linux on System zHendrik Brueckner
Add the first 3270 terminal device that is associated with the Linux preferred console to the list of virtualization consoles. This is required to automatically start a getty if the conmode=3270 kernel parameter is specified for Linux on z/VM instances. Note that a queued upstream patch also enable the 3270 terminal device if it is associated with the Linux preferred console. How To successfully start agetty on a 3270 terminal, a change in the agetty parameter order is required. Previously, agetty would started like this: /sbin/agetty --keep-baud 3270/tty1 115200,38400,9600 TERM The agetty program interprets the "3270/tty1" as baud rate and fails to start with the "bad speed: 3270/tty1" error message. Fixing this in agetty is more complex rather than reordering the command line parameters like this: /sbin/agetty --keep-baud 115200,38400,9600 3270/tty1 TERM According to agetty sources and "agetty --help", agetty accepts the "tty", "baudrate tty", and "tty baudrate" specifications. P.S. The "tty: Set correct tty name in 'active' sysfs attribute" introduces a change to display the terminal device which is associated with the Linux preferred console. This change helps to let systemd handle this particular case only. Without the changes of this commit, no additional 3270 terminal device can be managed by systemd. https://git.kernel.org/cgit/linux/kernel/git/gregkh/tty.git/commit/?id=723abd87f6e536f1353c8f64f621520bc29523a3
2014-03-08units: remove "AllowUser=root own", the bus owner can always own namesKay Sievers
2014-03-07units: set 'AllowUser=root own' and 'AllowWorld=talk' own for all .busname filesDaniel Mack
2014-03-07units: Do not unescape instance name in systemd-backlight@.serviceThomas Bächler
The instance name is never escaped in the udev rule, but unescaped in the unit. This results in the following error message on Asus boards: Failed to get backlight or LED device 'backlight:eeepc/wmi': No such file or directory
2014-03-06units: don't use the word 'Reboot' for Startup, but simply 'Boot'Lennart Poettering
2014-03-06units: properly capitalize the unit descriptionLennart Poettering
2014-02-25Use /var/run/dbus/system_bus_socket for the D-Bus socketZbigniew Jędrzejewski-Szmek
2014-02-24units/serial-getty@.service: add [Install] sectionZbigniew Jędrzejewski-Szmek
This makes it easier to manually enable and disable specific gettys, and also mirrors getty@.service. http://lists.freedesktop.org/archives/systemd-devel/2014-February/017329.html
2014-02-21install: do not statically enable systemd-networkdJason A. Donenfeld
[tomegun: pruned the commit message as not to contradict the follow-up commit]
2014-02-14units: systemd-logind fails hard without dbusZbigniew Jędrzejewski-Szmek
That is, without --enable-kdbus and kdbus running. With --enable-kdbus things are more complicated, because dbus might be necessary, if kdbus is missing at runtime. If it is not necessary, the socket will be started, which is not imporant, but not the service.
2014-02-11units: make use of nspawn's --keep-unit switch in systemd-nspawn@.serviceLennart Poettering
2014-01-29core: introduce new KillMode=mixed which sends SIGTERM only to the main ↵Lennart Poettering
process, but SIGKILL to all daemon processes This should fix some race with terminating systemd --user, where the system systemd instance might race against the user systemd instance when sending SIGTERM.
2014-01-18networkd: don't hard depend on system busTom Gundersen
We may not have a dbus daemon in the initrd (until we can rely on kdbus). In this case, simply ignore any attempts at using the bus. There is only one user for now, but surely more to come. In order to work reliably in the real root without kdbus, but at the same time don't delay boot when kdbus is in use, order ourselves after dbus.service.
2014-01-17units: drop [Install] section from multi-user.target and graphical.targetLennart Poettering
They were supposed to make it easy to make the default.target a symlink to these targets, but this was never advertised and we have a better command for this now in "systemctl set-default". Since the install section makes the output of "systemctl list-unit-files" confusing (since it makes the units appear as "disabled"), let's drop the sections.
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.