diff options
author | Pádraig Brady <P@draigBrady.com> | 2010-03-15 23:03:30 +0000 |
---|---|---|
committer | Pádraig Brady <P@draigBrady.com> | 2010-03-16 23:10:15 +0000 |
commit | c403c31e8806b732e1164ef4a206b0eab71bca95 (patch) | |
tree | c593bccff037db3c5f332810aec7dfbc33a30683 /NEWS | |
parent | 4edb86215deec3ad7478eb4eca54d563bd3b95c0 (diff) | |
download | coreutils-c403c31e8806b732e1164ef4a206b0eab71bca95.tar.xz |
timeout: add the --kill-after option
Based on a report from Kim Hansen who wanted to
send a KILL signal to the monitored command
when `timeout` itself received a termination signal.
Rather than changing such a signal into a KILL,
we provide the more general mechanism of sending
the KILL after the specified grace period.
* src/timeout.c (cleanup): If a non zero kill delay
is specified, (re)set the alarm to that delay, after
which a KILL signal will be sent to the process group.
(usage): Mention the new option. Separate the description
of DURATION since it's now specified in 2 places.
Clarify that the duration is an integer.
(parse_duration): A new function refactored from main(),
since this logic is now called for two parameters.
(main): Parse the -k option.
* doc/coreutils.texi (timeout invocation): Describe the
new --kill-after option and use @display rather than
@table to show the duration suffixes. Clarify that
a duration of 0 disables the associated timeout.
* tests/misc/timeout-parameters: Check invalid --kill-after.
* tests/misc/timeout: Check a valid --kill-after works.
* NEWS: Mention the new feature.
Diffstat (limited to 'NEWS')
-rw-r--r-- | NEWS | 4 |
1 files changed, 4 insertions, 0 deletions
@@ -17,6 +17,10 @@ GNU coreutils NEWS -*- outline -*- join now accepts the --header option, to treat the first line of each file as a header line to be joined and printed unconditionally. + timeout now accepts the --kill-after option which sends a kill + signal to the monitored command if it's still running the specified + duration after the initial signal was sent. + who: the "+/-" --mesg (-T) indicator of whether a user/tty is accepting messages could be incorrectly listed as "+", when in fact, the user was not accepting messages (mesg no). Before, who would examine only the |