systemd-journal-flush.service: remove "trigger" from description

[elogind.git] / NEWS

diff --git a/NEWS b/NEWS
index f4afcf6e06d2c91653dd4fca8ca8ef3ccd095986..96f0dd79f933eedd33d3a91e124f6e8ee72675e7 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -7,6 +7,11 @@ CHANGES WITH 217:
           show log timestamps in the UTC timezone. journalctl now also
           accepts -n/--lines=all to disable line capping in a pager.
 
           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
         * 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


@@ -76,7 +81,7 @@ CHANGES WITH 217:
           rotating media anymore, and nobody stepped up to actively
           maintain this component of systemd it has now been removed.
 
           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.
 
           Discard options specified for swaps in /etc/fstab are now
           respected.
 


@@ -174,6 +179,14 @@ CHANGES WITH 217:
           and 'b!', so that they are created only at boot and not
           overwritten at runtime.
 
           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,
         Contributions from: Andreas Henriksson, Andrei Borzenkov,
         Angus Gibson, Ansgar Burchardt, Ben Wolsieffer, Brandon L.
         Black, Christian Hesse, Cristian Rodríguez, Daniel Buch,


@@ -1963,8 +1976,8 @@ CHANGES WITH 207:
           certain paths from operation.
 
         * journald will now automatically flush all messages to disk
           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,
 
         Contributions from: Andrew Cook, Brandon Philips, Christian
         Hesse, Christoph Junghans, Colin Walters, Daniel Schaal,