systemd System and Service Manager
+CHANGES WITH 218:
+
+ * If compiled with --enable-xkbcommon, systemd-localed will
+ verify x11 keymap settings by compiling the given keymap. It
+ will spew out warnings if the compilation fails. This
+ requires libxkbcommon to be installed.
+
CHANGES WITH 217:
* journalctl gained the new options -t/--identifier= to match
show log timestamps in the UTC timezone. journalctl now also
accepts -n/--lines=all to disable line capping in a pager.
+ * journalctl gained a new switch, --flush, that synchronously
+ flushes logs from /run/log/journal to /var/log/journal if
+ persistent storage is enabled. systemd-journal-flush.service
+ now waits until the operation is complete.
+
* Services can notify the manager before they start a reload
(by sending RELOADING=1) or shutdown (by sending
STOPPING=1). This allows the manager to track and show the
* A helper binary and a service have been added which can be
used to resume from hibernation in the initramfs. A
generator will parse the resume= option on the kernel
- command-line to trigger resume.
+ command line to trigger resume.
* A user console daemon systemd-consoled has been
added. Currently, it is a preview, and will so far open a
rotating media anymore, and nobody stepped up to actively
maintain this component of systemd it has now been removed.
- * Swap units can use Discard= to specify discard options.
+ * Swap units can use Options= to specify discard options.
Discard options specified for swaps in /etc/fstab are now
respected.
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
and should not be used in production. Note: if "--enable-kdbus"
certain paths from operation.
* journald will now automatically flush all messages to disk
- as soon as a message of the log priorities CRIT, ALERT or
- EMERG is received.
+ as soon as a message at the log level CRIT, ALERT or EMERG
+ is received.
Contributions from: Andrew Cook, Brandon Philips, Christian
Hesse, Christoph Junghans, Colin Walters, Daniel Schaal,