themselves. More specifically, if the administrator wants to
change one value for a service file foobar.service he can
now do so by dropping in a configuration snippet into
- /etc/systemd/systemd/foobar.service.d/*.conf. The unit logic
+ /etc/systemd/system/foobar.service.d/*.conf. The unit logic
will load all these snippets and apply them on top of the
main unit configuration file, possibly extending or
overriding its settings. Using these drop-in snippets is
- generally nicer than the two earler options for changing
- unit files locally: copying the files form
+ generally nicer than the two earlier options for changing
+ unit files locally: copying the files from
/usr/lib/systemd/system/ to /etc/systemd/system/ and editing
them there; or creating a new file in /etc/systemd/system/
that incorporates the original one via ".include". Drop-in
snippets into these .d/ directories can be placed in any
- directory systems looks for units in, and the usual
+ directory systemd looks for units in, and the usual
overriding semantics between /usr/lib, /etc and /run apply
for them too.
* Most unit file settings which take lists of items can now be
- reset by assigning the empty strings to them. For example,
+ reset by assigning the empty string to them. For example,
normally, settings such as Environment=FOO=BAR append a new
environment variable assignment to the environment block,
each time they are used. By assigning Environment= the empty
string the environment block can be reset to empty. This is
particularly useful with the .d/*.conf drop-in snippets
- mentioned above, since this allows resetting list settings
- from vendor unit files via these drop-ins.
+ mentioned above, since this adds the ability to reset list
+ settings from vendor unit files via these drop-ins.
* systemctl gained a new "list-dependencies" command for
listing the dependencies of a unit recursively.
- * Inhibitors are now honoured and listed by "systemctl
+ * Inhibitors are now honored and listed by "systemctl
suspend", "systemctl poweroff" (and similar) too, not only
GNOME. These commands will also list active sessions by
other users.
for all units. More specifically, you can now use a command
like "systemctl set-cgroup-attr foobar.service cpu.shares
2000" to alter the CPU shares a specific service gets. These
- settings are stores persistently on disk, and thus allow the
+ settings are stored persistently on disk, and thus allow the
administrator to easily adjust the resource usage of
services with a few simple commands. This dynamic resource
- management logic is also available to other services via the
+ management logic is also available to other programs via the
bus. Almost any kernel cgroup attribute and controller is
supported.
* systemd-vconsole-setup will now copy all font settings to
- all open VTs, where it previously applied them only to the
- foreground VT.
+ all allocated VTs, where it previously applied them only to
+ the foreground VT.
* libsystemd-login gained the new sd_session_get_tty() API
call.
- * This release drops support with a few
- legacy/distribution-specific LSB facility names when parsing
- init scripts: $x-display-manager, $mail-transfer-agent,
+ * This release drops support for a few legacy or
+ distribution-specific LSB facility names when parsing init
+ scripts: $x-display-manager, $mail-transfer-agent,
$mail-transport-agent, $mail-transfer-agent, $smtp,
$null. Also, the mail-transfer-agent.target unit backing
this has been removed. Distributions which want to retain
- compatibility with this should carry the burden for support
- this themselves and patch support for these back in if they
- really need to. Also, the facilities $syslog and $local_fs
- are now ignored, since systemd does not support early-boot
- LSB init scripts anymore, and these facilities are implied
- anyway for normal services. syslog.target has also been
- removed hence.
-
- * There ar new bus calls on PID1's Manager object for
- canceling jobs, and removing snapshot units. Previously,
+ compatibility with this should carry the burden for
+ supporting this themselves and patch support for these back
+ in, if they really need to. Also, the facilities $syslog and
+ $local_fs are now ignored, since systemd does not support
+ early-boot LSB init scripts anymore, and these facilities
+ are implied anyway for normal services. syslog.target has
+ also been removed.
+
+ * There are new bus calls on PID1's Manager object for
+ cancelling jobs, and removing snapshot units. Previously,
both calls were only available on the Job and Snapshot
objects themselves.
bind mount specific directories from the host into the
container.
- * nspawn will not mount its own devpts file system instance
- into the container, in order not to leaker pty devices from
+ * nspawn will now mount its own devpts file system instance
+ into the container, in order not to leak pty devices from
the host into the container.
* systemd will now read the firmware boot time performance
- from the EFI variables, if the used boot loader supports
- this, and take it into account for boot performance analysis
- via "systemd-analyze". This is currently supported only in
- conjunction with Gummiboot, but could be supported by other
- boot loaders too. For details, see:
+ information from the EFI variables, if the used boot loader
+ supports this, and takes it into account for boot performance
+ analysis via "systemd-analyze". This is currently supported
+ only in conjunction with Gummiboot, but could be supported
+ by other boot loaders too. For details see:
http://www.freedesktop.org/wiki/Software/systemd/BootLoaderInterface
* A new generator has been added that automatically mounts the
EFI System Partition (ESP) to /boot, if that directory
- exists, is empty, and no other partition has been configured
- to be mounted there.
+ exists, is empty, and no other file system has been
+ configured to be mounted there.
* logind will now send out PrepareForSleep(false) out
unconditionally, after coming back from suspend. This may be
* "systemctl unlock-sessions" has been added, that allows
unlocking the screens of all user sessions at once, similar
how "systemctl lock-sessions" already locked all users
- sessions. This is backed by a new D-Bus call
- UnlockSessions().
+ sessions. This is backed by a new D-Bus call UnlockSessions().
* "loginctl seat-status" will now show the master device of a
seat. (i.e. the device of a seat that needs to be around for
configuration of files and directories (with wildcards) that
shall be excluded from automatic cleanup ("aging").
- * udev permission rules are now only applied for "add" rules,
- no longer for "change" events.
+ * udev default rules set the device node permissions now only
+ at "add" events, and do not change them any longer with a
+ later "change" event.
* The log messages for lid events and power/sleep keypresses
now carry a message ID.
* udevadm hwdb gained a new --root= parameter to change the
root directory to operate relative to.
- * logind will now issue a sync() request to the kernel early
- at shutdown, so that dirty buffers are flushed to disk early
+ * logind will now issue a background sync() request to the kernel
+ early at shutdown, so that dirty buffers are flushed to disk early
instead of at the last moment, in order to optimize shutdown
times a little.
* Operations such as "systemctl start" can now be executed
with a new mode "--irreversible" which may be used to queue
operations that cannot accidentally be reversed by a later
- job queuing. This is by default use to make shutdown
+ job queuing. This is by default used to make shutdown
requests more robust.
* The Python API of systemd now gained a new module for
http://www.freedesktop.org/wiki/Specifications/BootLoaderSpec
* Boot time console output has been improved to provide
- animated boot time output.
+ animated boot time output for hanging jobs.
* A new tool systemd-activate has been added which can be used
to test socket activation with, directly from the command
* journalctl gained a new "--reverse" (or -r) option to show
journal output in reverse order (i.e. newest line first).
+ * journalctl gained a new "--pager-end" (or -e) option to jump
+ to immediately jump to the end of the journal in the
+ pager. This is only supported in conjunction with "less".
+
* journalctl gained a new "--user-unit=" option, that works
similar to "--unit=" but filters for user units rather than
system units.
* The journal files are now owned by a new group
"systemd-journal", which exists specifically to allow access
to the journal, and nothing else. Previously, we used the
- "adm" group for that, which however possible covers more
+ "adm" group for that, which however possibly covers more
than just journal/log file access. This new group is now
already used by systemd-journal-gatewayd to ensure this
daemon gets access to the journal files and as little else
up for /var/log/journal to give "adm" and "wheel" read
access to it, in addition to "systemd-journal" which owns
the journal files. We recommend that packaging scripts also
- add read access to "adm", "wheel" to /var/log/journal, and
+ add read access to "adm" + "wheel" to /var/log/journal, and
all existing/future journal files. To normal users and
administrators little changes, however packagers need to
ensure to create the "systemd-journal" system group at
* systemd-detect-virt will now also detect xen PVs
- * The pstore file system is now mounted by default, if it is available.
+ * The pstore file system is now mounted by default, if it is
+ available.
+
+ * In addition to the SELinux and IMA policies we will now also
+ load SMACK policies at early boot.
Contributions from: Adel Gadllah, Aleksander Morgado, Auke
Kok, Ayan George, Bastien Nocera, Colin Walters, Daniel Buch,