X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=NEWS;h=84a43fd5dfc021147c7b1897d47bcc0e7ef7386e;hp=458096c0bec6086e2f94f08cd32ccfc1951f632f;hb=3b187c5cee0a9584d7c31e10f9fe008b94cf6d58;hpb=7e63dd1015c9ac6fc2042e45b0a87a3f9f8b9336

diff --git a/NEWS b/NEWS
index 458096c0b..84a43fd5d 100644
--- a/NEWS
+++ b/NEWS
@@ -56,7 +56,7 @@ CHANGES WITH 217:
         * Route metrics can be specified for DHCP routes added by
           systemd-networkd.
 
-        * The SELinux context of socket-actived services can be set
+        * The SELinux context of socket-activated services can be set
           from the information provided by the networking stack
           (SELinuxContextFromNet= option).
 
@@ -70,7 +70,7 @@ CHANGES WITH 217:
         * Udev rules can now remove tags on devices with TAG-="foobar".
 
         * systemd's readahead implementation has been removed. In many
-          circumstatances it didn't give expected benefits even for
+          circumstances it didn't give expected benefits even for
           rotational disk drives and was becoming less relevant in the
           age of SSDs. As none of the developers has been using
           rotating media anymore, and nobody stepped up to actively
@@ -84,7 +84,7 @@ CHANGES WITH 217:
           virtualization.
 
         * The Password Agent protocol gained support for queries where
-          the user input is shown, useful e.g. for usernames.
+          the user input is shown, useful e.g. for user names.
           systemd-ask-password gained a new --echo option to turn that
           on.
 
@@ -92,8 +92,8 @@ CHANGES WITH 217:
 
                 net.core.default_qdisc = fq_codel
 
-          This selects Fair Queueing Controlled Delay as the default
-          queueing discipline for network interfaces. fq_codel helps
+          This selects Fair Queuing Controlled Delay as the default
+          queuing discipline for network interfaces. fq_codel helps
           fight the network bufferbloat problem. It is believed to be
           a good default with no tuning required for most workloads.
           Downstream distributions may override this choice. On 10Gbit
@@ -129,11 +129,11 @@ CHANGES WITH 217:
           option.
 
         * New kernel command line options mount.usr=, mount.usrflags=,
-          usrfstype= have been added that match root=, rootflags=,
+          mount.usrfstype= have been added that match root=, rootflags=,
           rootfstype= but allow mounting a specific file system to
           /usr.
 
-        * The $NOTIFY_SOCKET is now also passed to control processesof
+        * The $NOTIFY_SOCKET is now also passed to control processes of
           services, not only the main process.
 
         * This version reenables support for fsck's -l switch. This
@@ -152,7 +152,7 @@ CHANGES WITH 217:
           message flag has been added for all of systemd's PolicyKit
           authenticated method calls has been added. In particular
           this now allows optional interactive authorization via
-          PolicyKit for many of PID1's priviliged operations such as
+          PolicyKit for many of PID1's privileged operations such as
           unit file enabling and disabling.
 
         * "udevadm hwdb --update" learnt a new switch "--usr" for
@@ -165,9 +165,23 @@ CHANGES WITH 217:
 
         * Calendar time specifications in .timer units now also
           understand the strings "semi-annually", "quarterly" and
-          "minutely" as shortcuts (in addition to the pre-existing
+          "minutely" as shortcuts (in addition to the preexisting
           "anually", "hourly", ...).
 
+        * systemd-tmpfiles will now correctly create files in /dev
+          at boot which are marked for creation only at boot. It is
+          recommended to always create static device nodes with 'c!'
+          and 'b!', so that they are created only at boot and not
+          overwritten at runtime.
+
+        * When the watchdog logic is used for a service (WatchdogSec=)
+          and the watchdog timeout is hit the service will now be
+          terminated with SIGABRT (instead of just SIGTERM), in order
+          to make sure a proper coredump and backtrace is
+          generated. This ensures that hanging services will result in
+          similar coredump/backtrace behaviour as services that hit a
+          segmentation fault.
+
         Contributions from: Andreas Henriksson, Andrei Borzenkov,
         Angus Gibson, Ansgar Burchardt, Ben Wolsieffer, Brandon L.
         Black, Christian Hesse, Cristian Rodríguez, Daniel Buch,