timeout: Run a command with a time limittimeout runs the given command and kills it if it is
still running after the specified time interval. Synopsis:
timeout [option] duration command [arg]…
command must not be a special built-in utility (see Special built-in utilities).
The program accepts the following options. Also see Common options. Options must precede operands.
Return the exit status of the managed command on timeout, rather than a specific exit status indicating a timeout. This is useful if the managed command supports running for an indeterminate amount of time.
Don’t create a separate background program group, so that
the managed command can use the foreground TTY normally.
This is needed to support two situations when timing out commands,
when not invoking timeout from an interactive shell.
In this mode of operation, any children of command will not be timed out. Also SIGCONT will not be sent to 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).
Ensure the monitored command is killed by also sending a ‘KILL’ signal.
The specified duration starts from the point in time when
timeout sends the initial signal to command, i.e.,
not from the beginning when the command is started.
This option has no effect if either the main duration
of the timeout command, or the duration specified
to this option, is 0.
This option may be useful if the selected signal did not kill the command, either because the signal was blocked or ignored, or if the command takes too long (e.g. for cleanup work) to terminate itself within a certain amount of time.
Send this signal to command on timeout, rather than the default ‘TERM’ signal. signal may be a name like ‘HUP’ or a number. See Signal specifications.
Diagnose to standard error, any signal sent upon timeout.
duration is a floating point number in either the current or the C locale (see Floating point numbers) followed by an optional unit:
‘s’ for seconds (the default) ‘m’ for minutes ‘h’ for hours ‘d’ for days
A duration of 0 disables the associated timeout. The actual timeout duration is dependent on system conditions, which should be especially considered when specifying sub-second timeouts.
Exit status:
124 if command times out, and --preserve-status is not specified 125 iftimeoutitself fails 126 if command is found but cannot be invoked 127 if command cannot be found 137 if command ortimeoutis sent the KILL(9) signal (128+9) the exit status of command otherwise
In the case of the ‘KILL(9)’ signal, timeout returns with
exit status 137, regardless of whether that signal is sent to command
or to timeout itself, i.e., these cases cannot be distinguished.
In the latter case, the command process may still be alive after
timeout has forcefully been terminated.
Examples:
# Send the default TERM signal after 20s to a short-living 'sleep 1'. # As that terminates long before the given duration, 'timeout' returns # with the same exit status as the command, 0 in this case. timeout 20 sleep 1 # Send the INT signal after 5s to the 'sleep' command. Returns after # 5 seconds with exit status 124 to indicate the sending of the signal. timeout -s INT 5 sleep 20 # Likewise, but the command ignoring the INT signal due to being started # via 'env --ignore-signal'. Thus, 'sleep' terminates regularly after # the full 20 seconds, still 'timeout' returns with exit status 124. timeout -s INT 5s env --ignore-signal=INT sleep 20 # Likewise, but sending the KILL signal 3 seconds after the initial # INT signal. Hence, 'sleep' is forcefully terminated after about # 8 seconds (5+3), and 'timeout' returns with an exit status of 137. timeout -s INT -k 3s 5s env --ignore-signal=INT sleep 20