systemd System and Service Manager
+CHANGES WITH 211:
+
+ * A new unit file setting RestrictAddressFamilies= has been
+ added to restrict which socket address families unit
+ processes gain access to. This takes address family names
+ like "AF_INET" or "AF_UNIX", and is useful to minimize the
+ attack surface of services via exotic protocol stacks. This
+ is built on seccomp system call filters.
+
+ * Two new unit file settings RuntimeDirectory= and
+ RuntimeDirectoryMode= have been added that may be used to
+ manage a per-daemon runtime directories below /run. This is
+ an alternative for setting up directory permissions with
+ tmpfiles snippets, and has the advantage that the runtime
+ directory's lifetime is bound to the daemon runtime and that
+ the daemon starts up with an empty directory each time. This
+ is particularly useful when writing services that drop
+ priviliges using the User= or Group= setting.
+
+ * The DeviceAllow= unit setting now supports globbing for
+ matching against device group names.
+
+ * The systemd configuration file system.conf gained new
+ settings DefaultCPUAccounting=, DefaultBlockIOAccounting=,
+ DefaultMemoryAccounting= to globally turn on/off accounting
+ for specific resources (cgroups) for all units. These
+ settings may still be overridden individually in each unit
+ though.
+
+ * systemd-gpt-auto-generator is now able to discover /srv and
+ root partitions in addition to /home and swap partitions. It
+ also supports LUKS-encrypted partitions now. With this in
+ place automatic discovery of partitions to mount following
+ the Discoverable Partitions Specification
+ (http://www.freedesktop.org/wiki/Specifications/DiscoverablePartitionsSpec)
+ is now a lot more complete. This allows booting without
+ /etc/fstab and without root= on the kernel command line on
+ appropriately prepared systems.
+
+ * systemd-nspawn gained a new --image= switch which allows
+ booting up disk images and Linux installations on any block
+ device that follow the Discoverable Partitions Specification
+ (see above). This means that installations made with
+ appropriately updated installers may now be started and
+ deployed using container managers, completely
+ unmodified. (We hope that libvirt-lxc will add support for
+ this feature soon, too.)
+
+ * systemd-nspawn gained a new --network-macvlan= setting to
+ set up a private macvlan interface for the
+ container. Similar, systemd-networkd gained a new
+ Kind=macvlan setting in .netdev files.
+
+ * systemd-networkd now supports configuring local addresses
+ using IPv4LL.
+
+ * A new tool systemd-network-wait-online has been added to
+ synchronously wait for network connectivity using
+ systemd-networkd.
+
+ * The sd-bus.h bus API gained a new sd_bus_track object for
+ tracking the life-cycle of bus peers. Note that sd-bus.h is
+ still not a public API though (unless you specify
+ --enable-kdbus on the configure command line, which however
+ voids your warranty and you get no API stability guarantee).
+
+ * The $XDG_RUNTIME_DIR runtime directories for each user are
+ now individual tmpfs instances, which has the benefit of
+ introducing separate pools for each user, with individual
+ size limits, and thus making sure that unprivileged clients
+ can no longer negatively impact the system or other users by
+ filling up their $XDG_RUNTIME_DIR. A new logind.conf setting
+ RuntimeDirectorySize= has been introduced that allows
+ controlling the default size limit for all users. It
+ defaults to 10% of the available physical memory. This is no
+ replacement for quotas on tmpfs though (which the kernel
+ still does not support), as /dev/shm and /tmp are still
+ shared resources used by both the system and unprivileged
+ users.
+
+ * logind will now automatically turn off automatic suspending
+ on laptop lid close when more than one display is
+ connected. This was previously expected to be implemented
+ individually in desktop environments (such as GNOME),
+ however has been added to logind now, in order to fix a
+ boot-time race where a desktop environment might not have
+ been started yet and thus not been able to take an inhibitor
+ lock at the time where logind already suspends the system
+ due to a closed lid.
+
+ * logind will now wait at least 30s after each system
+ suspend/resume cycle, and 3min after system boot before
+ suspending the system due to a closed laptop lid. This
+ should give USB docking stations and similar enough time to
+ be probed and configured after system resume and boot in
+ order to then act as suspend blocker.
+
+ * systemd-run gained a new --property= setting which allows
+ initialization of resource control properties (and others)
+ for the created scope or service unit. Example: "systemd-run
+ --property=BlockIOWeight=10 updatedb" may be used to run
+ updatedb at a low block IO scheduling weight.
+
+ * systemd-run's --uid=, --gid=, --setenv=, --setenv= switches
+ now also work in --scope mode.
+
+ * When systemd is compiled with kdbus support, basic support
+ for enforced policies is now in place. (Note that enabling
+ kdbus still voids your warranty and no API compatibility
+ promises are made.)
+
+ Contributions from: Andrey Borzenkov, Ansgar Burchardt, Armin
+ K., Daniel Mack, Dave Reisner, David Herrmann, Djalal Harouni,
+ Harald Hoyer, Henrik Grindal Bakken, Jasper St. Pierre, Kay
+ Sievers, Kieran Clancy, Lennart Poettering, Lukas Nykryn,
+ Mantas Mikulėnas, Marcel Holtmann, Mark Oteiza, Martin Pitt,
+ Mike Gilbert, Peter Rajnoha, poma, Samuli Suominen, Stef
+ Walter, Susant Sahani, Tero Roponen, Thomas Andersen, Thomas
+ Bächler, Thomas Hindoe Paaboel Andersen, Tomasz Torcz, Tom
+ Gundersen, Umut Tezduyar Lindskog, Uoti Urpala, Zachary Cook,
+ Zbigniew Jędrzejewski-Szmek
+
+ -- Berlin, 2014-03-12
+
+CHANGES WITH 210:
+
+ * systemd will now relabel /dev after loading the SMACK policy
+ according to SMACK rules.
+
+ * A new unit file option AppArmorProfile= has been added to
+ set the AppArmor profile for the processes of a unit.
+
+ * A new condition check ConditionArchitecture= has been added
+ to conditionalize units based on the system architecture, as
+ reported by uname()'s "machine" field.
+
+ * systemd-networkd now supports matching on the system
+ virtualization, architecture, kernel command line, host name
+ and machine ID.
+
+ * logind is now a lot more aggressive when suspending the
+ machine due to a closed laptop lid. Instead of acting only
+ on the lid close action it will continuously watch the lid
+ status and act on it. This is useful for laptops where the
+ power button is on the outside of the chassis so that it can
+ be reached without opening the lid (such as the Lenovo
+ Yoga). On those machines logind will now immediately
+ re-suspend the machine if the power button has been
+ accidentally pressed while the laptop was suspended and in a
+ backpack or similar.
+
+ * logind will now watch SW_DOCK switches and inhibit reaction
+ to the lid switch if it is pressed. This means that logind
+ will not suspend the machine anymore if the lid is closed
+ and the system is docked, if the laptop supports SW_DOCK
+ notifications via the input layer. Note that ACPI docking
+ stations do not generate this currently. Also note that this
+ logic is usually not fully sufficient and Desktop
+ Environments should take a lid switch inhibitor lock when an
+ external display is connected, as systemd will not watch
+ this on its own.
+
+ * nspawn will now make use of the devices cgroup controller by
+ default, and only permit creation of and access to the usual
+ API device nodes like /dev/null or /dev/random, as well as
+ access to (but not creation of) the pty devices.
+
+ * We will now ship a default .network file for
+ systemd-networkd that automatically configures DHCP for
+ network interfaces created by nspawn's --network-veth or
+ --network-bridge= switches.
+
+ * systemd will now understand the usual M, K, G, T suffixes
+ according to SI conventions (i.e. to the base 1000) when
+ referring to throughput and hardware metrics. It will stay
+ with IEC conventions (i.e. to the base 1024) for software
+ metrics, according to what is customary according to
+ Wikipedia. We explicitly document which base applies for
+ each configuration option.
+
+ * The DeviceAllow= setting in unit files now supports a syntax
+ to whitelist an entire group of devices node majors at once,
+ based on the /proc/devices listing. For example, with the
+ string "char-pts" it is now possible to whitelist all
+ current and future pseudo-TTYs at once.
+
+ * sd-event learned a new "post" event source. Event sources of
+ this type are triggered by the dispatching of any event
+ source of a type that is not "post". This is useful for
+ implementing clean-up and check event sources that are
+ triggered by other work being done in the program.
+
+ * systemd-networkd is no longer statically enabled, but uses
+ the usual [Install] sections so that it can be
+ enabled/disabled using systemctl. It still is enabled by
+ default however.
+
+ * When creating a veth interface pair with systemd-nspawn the
+ host side will now be prefixed with "vb-" if
+ --network-bridge= is used, and with "ve-" if --network-veth
+ is used. This way it is easy to distinguish these cases on
+ the host, for example to apply different configuration to
+ them with systemd-networkd.
+
+ * The compatibility libraries for libsystemd-journal.so,
+ libsystem-id128.so, libsystemd-login.so and
+ libsystemd-daemon.so do not make use of IFUNC
+ anymore. Instead we now build libsystemd.so multiple times
+ under these alternative names. This means that the footprint
+ is drastically increased, but given that these are
+ transitional compatibility libraries this shouldn't matter
+ much. This change has been made necessary to support the ARM
+ platform for these compatibility libraries, as the ARM
+ toolchain isn't really at the same level as the toolchain
+ for other architectures like x86 and does not support
+ IFUNC. Please make sure to use --enable-compat-libs only
+ during a transitional period!
+
+ Contributions from: Andreas Fuchs, Armin K., Colin Walters,
+ Daniel Mack, Dave Reisner, David Herrmann, Djalal Harouni,
+ Holger Schurig, Jason A. Donenfeld, Jason St. John, Jasper
+ St. Pierre, Kay Sievers, Lennart Poettering, Łukasz Stelmach,
+ Marcel Holtmann, Michael Scherer, Michal Sekletar, Mike
+ Gilbert, Samuli Suominen, Thomas Bächler, Thomas Hindoe
+ Paaboel Andersen, Tom Gundersen, Umut Tezduyar Lindskog,
+ Zbigniew Jędrzejewski-Szmek
+
+ -- Berlin, 2014-02-24
+
CHANGES WITH 209:
* A new component "systemd-networkd" has been added that can
be used to configure local network interfaces statically or
- via DHCP. It is capable of bringing up bridges, VLANs and
- bonding. Currently, no hookups for interactive network
+ via DHCP. It is capable of bringing up bridges, VLANs, and
+ bonding. Currently, no hook-ups for interactive network
configuration are provided. Use this for your initrd,
- container, embedded or server setup if you need a simple,
- yet powerful network configuration solution. This
+ container, embedded, or server setup if you need a simple,
+ yet powerful, network configuration solution. This
configuration subsystem is quite nifty, as it allows wildcard
hotplug matching in interfaces. For example, with a single
configuration snippet, you can configure that all Ethernet
* Add a new tool to save/restore rfkill state on
shutdown/boot.
- * Save/restore state of kbd backlights in addition to display
- backlights on shutdown/boot.
+ * Save/restore state of keyboard backlights in addition to
+ display backlights on shutdown/boot.
* udev learned a new SECLABEL{} construct to label device
nodes with a specific security label when they appear. For
* udev gained a new scheme to configure link-level attributes
from files in /etc/systemd/network/*.link. These files can
- match against MAC address, device path, driver name and type
+ match against MAC address, device path, driver name and type,
and will apply attributes like the naming policy, link speed,
- MTU, duplex settings, WakeOnLan settings, MAC address, MAC
+ MTU, duplex settings, Wake-on-LAN settings, MAC address, MAC
address assignment policy (randomized, ...).
+ * The configuration of network interface naming rules for
+ "permanent interface names" has changed: a new NamePolicy=
+ setting in the [Link] section of .link files determines the
+ priority of possible naming schemes (onboard, slot, mac,
+ path). The default value of this setting is determined by
+ /usr/lib/net/links/99-default.link. Old
+ 80-net-name-slot.rules udev configuration file has been
+ removed, so local configuration overriding this file should
+ be adapated to override 99-default.link instead.
+
* When the User= switch is used in a unit file, also
initialize $SHELL= based on the user database entry.
defining objects on the bus with a simple static const
vtable array of its methods, signals and properties.
- * systemd will not generate nor install static dbus
+ * systemd will not generate or install static dbus
introspection data anymore to /usr/share/dbus-1/interfaces,
as the precise format of these files is unclear, and
nothing makes use of it.
around the route netlink interface of the kernel, similar in
style to "sd-bus.h".
- * A new API "sd-dhcp.h" has been added that provides a small
- DHCPv4 client-side implementation. This is used by
+ * A new API "sd-dhcp-client.h" has been added that provides a
+ small DHCPv4 client-side implementation. This is used by
"systemd-networkd".
* There is a new kernel command line option
- "systemd.restore_state=0|1". When set to "0", none of the systemd tools
- will restore saved runtime state to hardware devices. More
- specifically, the rfkill and backlight states are not
- restored.
+ "systemd.restore_state=0|1". When set to "0", none of the
+ systemd tools will restore saved runtime state to hardware
+ devices. More specifically, the rfkill and backlight states
+ are not restored.
* The FsckPassNo= compatibility option in mount/service units
has been removed. The fstab generator will now add the
necessary dependencies automatically, and does not require
PID1's support for that anymore.
- * journalctl gained a new switch --list-boots, that lists
+ * journalctl gained a new switch, --list-boots, that lists
recent boots with their times and boot IDs.
* The various tools like systemctl, loginctl, timedatectl,
* systemd-run and systemd-analyze also gained support for "-H"
to connect to remote hosts via SSH. This is particularly
- useful for systemd-run since it enables queuing of jobs onto
- remote systems.
+ useful for systemd-run because it enables queuing of jobs
+ onto remote systems.
* machinectl gained a new command "login" to open a getty
login in any local container. This works with any container
that is registered with machined (such as those created by
- libvirt-lxc or nspawn), and which run systemd inside.
+ libvirt-lxc or nspawn), and which runs systemd inside.
* machinectl gained a new "reboot" command that may be used to
trigger a reboot on a specific container that is registered
* systemctl gained a new --job-mode= switch to configure the
mode to queue a job with. This is a more generic version of
- --fail, --irreversible, --ignore-dependencies which are
+ --fail, --irreversible, and --ignore-dependencies, which are
still available but not advertised anymore.
* /etc/systemd/system.conf gained new settings to configure
* PID1 will now export on the bus profile data of the security
policy upload process (such as the SELinux policy upload to
- the kernel) .
+ the kernel).
* journald: when forwarding logs to the console, include
timestamps (following the setting in
sd_session_get_remote_host() to query information about
remote sessions.
- * The udev device database now also carries vendor/product
- information about SDIO devices.
+ * The udev hardware database now also carries vendor/product
+ information of SDIO devices.
* The "sd-daemon.h" API gained a new sd_watchdog_enabled() to
determine whether watchdog notifications are requested by
time, and those which should be run only at boot (for
example, a line that creates /run/nologin).
- * A new API "sd-resolv.h" has been added which provides a simple
+ * A new API "sd-resolve.h" has been added which provides a simple
asynchronous wrapper around glibc NSS host name resolution
calls, such as getaddrinfo(). In contrast to glibc's
getaddrinfo_a(), it does not use signals. In contrast to most
other asynchronous name resolution libraries, this one does
not reimplement DNS, but reuses NSS, so that alternate
host name resolution systems continue to work, such as mDNS,
- LDAP, etc. This API is based on libasyncns, but has been
+ LDAP, etc. This API is based on libasyncns, but it has been
cleaned up for inclusion in systemd.
- * The APIs "sd-journal.h", "sd-login.h", "sd-id128.h" are no
- longer found in individual libraries libsystemd-journal.so,
- libsystemd-login.so, libsystemd-id128.so. Instead, we have
- merged them into a single library libsystemd.so which
- provides all symbols. The reason for this are cyclic
+ * The APIs "sd-journal.h", "sd-login.h", "sd-id128.h",
+ "sd-daemon.h" are no longer found in individual libraries
+ libsystemd-journal.so, libsystemd-login.so,
+ libsystemd-id128.so, libsystemd-daemon.so. Instead, we have
+ merged them into a single library, libsystemd.so, which
+ provides all symbols. The reason for this is cyclic
dependencies, as these libraries tend to use each other's
- symbols. So far, we managed to workaround that by linking a
- copy of a good part of our code into each of these libraries
- again and again, which however makes certain things hard to
- do, like sharing static variables. Also, it substantially
- increases footprint. With this change, there is only one
- library for the basic APIs systemd provides. Also,
- "sd-bus.h", "sd-memfd.h", "sd-event.h", "sd-rtnl.h",
- "sd-resolve.h", "sd-utf8.h" are found in this library as
- well, however are subject to the --enable-kdbus switch (see
- below). Note that "sd-dhcp.h" and "sd-daemon.h" are not part
- of this libraries (the former because it only consumes,
- never provides services of/to other APIs, and the latter
- because it is completely standalone). To make the transition
- from the separate libraries to the unified one easy, we
+ symbols. So far, we've managed to workaround that by linking
+ a copy of a good part of our code into each of these
+ libraries again and again, which, however, makes certain
+ things hard to do, like sharing static variables. Also, it
+ substantially increases footprint. With this change, there
+ is only one library for the basic APIs systemd
+ provides. Also, "sd-bus.h", "sd-memfd.h", "sd-event.h",
+ "sd-rtnl.h", "sd-resolve.h", "sd-utf8.h" are found in this
+ library as well, however are subject to the --enable-kdbus
+ switch (see below). Note that "sd-dhcp-client.h" is not part
+ of this library (this is because it only consumes, never
+ provides, services of/to other APIs). To make the transition
+ easy from the separate libraries to the unified one, we
provide the --enable-compat-libs compile-time switch which
will generate stub libraries that are compatible with the
old ones but redirect all calls to the new one.
- * All the kdbus logic and the new APIs "sd-bus.h",
+ * All of the kdbus logic and the new APIs "sd-bus.h",
"sd-memfd.h", "sd-event.h", "sd-rtnl.h", "sd-resolve.h",
- "sd-utf8.h" is compile-time optional via the
- "--enable-kdbus" switch, and is not compiled in by
- default. To make use of it, you have to explicitly enable
+ and "sd-utf8.h" are compile-time optional via the
+ "--enable-kdbus" switch, and they are not compiled in by
+ default. To make use of kdbus, you have to explicitly enable
the switch. Note however, that neither the kernel nor the
userspace API for all of this is considered stable yet. We
want to maintain the freedom to still change the APIs for
* Also, note that while kdbus is pretty much complete,
it lacks one thing: proper policy support. This means you
- can build a fully working system with all features, however
+ can build a fully working system with all features; however,
it will be highly insecure. Policy support will be added in
one of the next releases, at the same time that we will
declare the APIs stable.
- * When the kernel command line argument "kdbus" is specified,
+ * When the kernel command-line argument "kdbus" is specified,
systemd will automatically load the kdbus.ko kernel module. At
- this stage of development, it is only useful for testing kdbus,
+ this stage of development, it is only useful for testing kdbus
and should not be used in production. Note: if "--enable-kdbus"
- is specified and the kdbus.ko kernel module is available and
+ is specified, and the kdbus.ko kernel module is available, and
"kdbus" is added to the kernel command line, the entire system
runs with kdbus instead of dbus-daemon, with the above mentioned
problem of missing the system policy enforcement. Also a future
which allows running a service with a namespaced /dev
directory that does not contain any device nodes for
physical devices. More specifically, it only includes devices
- such as /dev/null, /dev/urandom and /dev/zero which are API
+ such as /dev/null, /dev/urandom, and /dev/zero which are API
entry points.
* logind has been extended to support behaviour like VT
switching on seats that do not support a VT. This makes
multi-session available on seats that are not the first seat
(seat0), and on systems where kernel support for VTs has
- been disabled at compile time.
+ been disabled at compile-time.
* If a process holds a delay lock for system sleep or shutdown
and fails to release it in time, we will now log its
* Boot-time status output is now enabled automatically after a
short timeout if boot does not progress, in order to give
- the user an indication what he or she is waiting for.
+ the user an indication what she or he is waiting for.
* The boot-time output has been improved to show how much time
remains until jobs expire.
* The KillMode= switch in service units gained a new possible
- value "mixed". If set and the unit is shutdown, then the
+ value "mixed". If set, and the unit is shut down, then the
initial SIGTERM signal is sent only to the main daemon
- process, while the following SIGKILL signal is then sent to
+ process, while the following SIGKILL signal is sent to
all remaining processes of the service.
* When a scope unit is registered, a new property "Controller"
RequestStop() signal to this name when it would like to shut
down the scope. This may be used to hook manager logic into
the shutdown logic of scope units. Also, scope units may now
- be put in a special "abandoned" state in which case the
+ be put in a special "abandoned" state, in which case the
manager process which created them takes no further
responsibilities for it.
marked executable or world-writable.
* systemd-nspawn gained a new "--setenv=" switch to set
- container-wide environment variables. A similar option in
+ container-wide environment variables. The similar option in
systemd-activate was renamed from "--environment=" to
"--setenv=" for consistency.
* systemd-nspawn has been updated to create a new kdbus domain
for each container that is invoked, thus allowing each
container to have its own set of system and user buses,
- independently of the host.
+ independent of the host.
* systemd-nspawn gained a new --drop-capability= switch to run
the container with less capabilities than the default. Both
* systemd-nspawn gained a new --register= switch to control
whether the container is registered with systemd-machined or
- not. This is useful for containers that do not register full
+ not. This is useful for containers that do not run full
OS images, but only specific apps.
* systemd-nspawn gained a new --keep-unit which may be used
- when invoked as only program from a service unit, and
+ when invoked as the only program from a service unit, and
results in registration of the unit service itself in
systemd-machined, instead of a newly opened scope unit.
* systemd-nspawn gained a new --network-interface= switch for
moving arbitrary interfaces to the container. The new
--network-veth switch creates a virtual Ethernet connection
- between host and container. Thew new --network-bridge=
- switch then additionally allows assigning the host side of
- this virtual Ethernet connection to a bridge device.
+ between host and container. The new --network-bridge=
+ switch then allows assigning the host side of this virtual
+ Ethernet connection to a bridge device.
+
+ * systemd-nspawn gained a new --personality= switch for
+ setting the kernel personality for the container. This is
+ useful when running a 32bit container on a 64bit host. A
+ similar option Personality= is now also available in service
+ units.
* logind will now also track a "Desktop" identifier for each
session which encodes the desktop environment of it. This is
* Most systemd client tools will now honour $SYSTEMD_LESS for
settings of the "less" pager. By default, these tools will
- override $LESS to allow certain operations like
- jump-to-the-end work. With $SYSTEMD_LESS, it is possible to
+ override $LESS to allow certain operations to work, such as
+ jump-to-the-end. With $SYSTEMD_LESS, it is possible to
influence this logic.
* systemd's "seccomp" hook-up has been changed to make use of
other things.
* For usage together with SystemCallFilter=, a new
- SystemCallErrorNumber= setting has been introduce that
- allows configuration if a system error number to return on
- filtered syscalls, instead of immediately killing the
+ SystemCallErrorNumber= setting has been introduced that
+ allows configuration of a system error number to return on
+ filtered system calls, instead of immediately killing the
process. Also, SystemCallArchitectures= has been added to
limit access to system calls of a particular architecture
(in order to turn off support for unused secondary
architectures). There is also a global
- SystemcallArchitecture= setting in system.conf now to turn
+ SystemCallArchitectures= setting in system.conf now to turn
off support for non-native system calls system-wide.
+ * systemd requires a kernel with a working name_to_handle_at(),
+ please see the kernel config requirements in the README file.
+
Contributions from: Adam Williamson, Alex Jia, Anatol Pomozov,
Ansgar Burchardt, AppleBloom, Auke Kok, Bastien Nocera,
Chengwei Yang, Christian Seiler, Colin Guthrie, Colin Walters,
Pavlín, Vincent Batts, WaLyong Cho, William Giokas, Yang
Zhiyong, Yin Kangkai, Yuxuan Shui, Zbigniew Jędrzejewski-Szmek
- -- Berlin, 2014-02-xx
+ -- Berlin, 2014-02-20
CHANGES WITH 208:
~ianmdlvl / elogind.git / blobdiff