Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I see a lot of shell scripts that do:
trap cmd 0 1 2 3 13 15 # EXIT HUP INT QUIT PIPE TERM
In every shell I have access to at the moment, all the traps other than 0 are redundant, and cmd will be executed upon receipt of a signal if the trap is simply specified:
trap cmd 0
Is the latter specification sufficient, or do some shells require the other signals to be specified?
I think trap 0 is executed just prior to script termination in all cases, so is useful for cleanup functionality (like removing temporary files, etc). The other signals can have specialized error handling but should terminate the script (that is, call exit).
What you have described, I believe, would actually execute cmd twice. Once for the signal (for example SIGTERM) and once more on exit (trap 0).
I believe the proper way to do this is like the following (see POSIX specification for
trap):This ensures a temporary file is removed upon script completion, and lets you set custom exit statuses on signals.
NOTE: trap 0 is called whether a signal is encountered or not.
If you are not concerned with setting an exit status, trap 0 would be sufficient.