Trap: Difference between revisions
Line 14: | Line 14: | ||
trap 'rm -f ./lock' EXIT | trap 'rm -f ./lock' EXIT | ||
For | Global variables declared before the trap declaration are correctly resolved inside '...' (even if single-quotes are used, the single quote semantics when used in bash command line is different from that in effect here). For example, the following code: | ||
<syntaxhighlight lang='bash'> | |||
a=hello | |||
trap 'echo ${a}' EXIT | |||
</syntaxhighlight> | |||
produces: | |||
<syntaxhighlight lang='text'> | |||
hello | |||
</syntaxhighlight> | |||
"EXIT" in the example above is not a Linux signal. Bash provides this psuedo-signal, which is executed when the script exits; this can be used to make sure that your script executes some cleanup on exit. | "EXIT" in the example above is not a Linux signal. Bash provides this psuedo-signal, which is executed when the script exits; this can be used to make sure that your script executes some cleanup on exit. | ||
For a list of signals that can be handled, see: {{Internal|Linux_Signals|Linux Signals}} | |||
Also see: {{Internal|Handling Signals in bash|Handling Signals in bash}} | Also see: {{Internal|Handling Signals in bash|Handling Signals in bash}} | ||
Revision as of 19:58, 20 December 2019
External
Internal
Overview
Trap is a facility to instruct bash to catch signals and execute code depending on the signal. A common usage in shell scripts is to prevent those scripts to exit untimely when users type keyboard abort sequences, but run cleanup code instead.
Example:
trap 'rm -f ./lock' EXIT
Global variables declared before the trap declaration are correctly resolved inside '...' (even if single-quotes are used, the single quote semantics when used in bash command line is different from that in effect here). For example, the following code:
a=hello
trap 'echo ${a}' EXIT
produces:
hello
"EXIT" in the example above is not a Linux signal. Bash provides this psuedo-signal, which is executed when the script exits; this can be used to make sure that your script executes some cleanup on exit.
For a list of signals that can be handled, see:
Also see:
Behavior on Being Invoked from Sub-Shells
If code is registered with trap
to react to EXIT in a sub-shell, or in a function that is invoked in a sub-shell, then the registered code will be executed when the sub-shell, and not the top-level invoking shell, exists.
The following code:
$(trap 'echo "a" 1>&2' EXIT)
echo "b"
will display:
a
b
Note that the output should be sent to stderr in the trap code - if the output is sent to stdout, the output is lost, even if the code executes.
TODO
Reactive Wait Container
Investigate usefulness in case of a reactive wait container. Also see Docker Concepts - Container Exit.
CMD exec /bin/bash -c "trap : TERM INT; sleep infinity & wait"