summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorPádraig Brady <P@draigBrady.com>2015-05-13 13:41:42 +0100
committerPádraig Brady <P@draigBrady.com>2015-05-13 13:48:56 +0100
commit45b8fe430dced8c489cb64491b8716cffeeca8c3 (patch)
tree7e5858933105e4f797ce545c70aaf531ed02f906 /doc
parent703747f892d3ec4713b97d4bff770a80122cd1ef (diff)
downloadcoreutils-45b8fe430dced8c489cb64491b8716cffeeca8c3.tar.xz
timeout: with --foreground don't send SIGCONT
* src/timeout.c (cleanup): Don't send SIGCONT to the monitored program when --foreground is specified, as it's generally not needed for foreground programs, and can cause intermittent signal delivery issues with monitors like GDB for example. * doc/coreutils.texi (timeout invocation): Mention that SIGCONT is not sent with --foreground. * NEWS: Mention the behavior change.
Diffstat (limited to 'doc')
-rw-r--r--doc/coreutils.texi5
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index 4ae06c30b..a7362b30c 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -16594,7 +16594,10 @@ from the terminal (like Ctrl-C for example)
@end enumerate
Note in this mode of operation, any children of @var{command}
-will not be timed out.
+will not be timed out. Also SIGCONT will not be sent to @var{command},
+as it's generally not needed with foreground processes, and can
+cause intermittent signal delivery issues with programs that are monitors
+themselves (like GDB for example).
@item -k @var{duration}
@itemx --kill-after=@var{duration}