In what order should I send signals to gracefully shutdown processes?

by

SIGTERM tells an application to terminate. The other signals tell the application other things which are unrelated to shutdown but may sometimes have the same result. Don’t use those. If you want an application to shut down, tell it to. Don’t give it misleading signals.

Some people believe the smart standard way of terminating a process is by sending it a slew of signals, such as HUP, INT, TERM and finally KILL. This is ridiculous. The right signal for termination is SIGTERM and if SIGTERM doesn’t terminate the process instantly, as you might prefer, it’s because the application has chosen to handle the signal. Which means it has a very good reason to not terminate immediately: It’s got cleanup work to do. If you interrupt that cleanup work with other signals, there’s no telling what data from memory it hasn’t yet saved to disk, what client applications are left hanging or whether you’re interrupting it “mid-sentence” which is effectively data corruption.

For more information on what the real meaning of the signals is, see sigaction(2). Don’t confuse “Default Action” with “Description”, they are not the same thing.

SIGINT is used to signal an interactive “keyboard interrupt” of the process. Some programs may handle the situation in a special way for the purpose of terminal users.

SIGHUP is used to signal that the terminal has disappeared and is no longer looking at the process. That is all. Some processes choose to shut down in response, generally because their operation makes no sense without a terminal, some choose to do other things such as recheck configuration files.

SIGKILL is used to forcefully remove the process from the kernel. It is special in the sense that it’s not actually a signal to the process but rather gets interpreted by the kernel directly.

Don’t send SIGKILL. – SIGKILL should certainly never be sent by scripts. If the application handles the SIGTERM, it can take it a second to cleanup, it can take a minute, it can take an hour. Depending on what the application has to get done before it’s ready to end. Any logic that “assumes” an application’s cleanup sequence has taken long enough and needs to be shortcut or SIGKILLed after X seconds is just plain wrong.

The only reason why an application would need a SIGKILL to terminate, is if something bugged out during its cleanup sequence. In which case you can open a terminal and SIGKILL it manually. Aside from that, the only one other reason why you’d SIGKILL something is because you WANT to prevent it from cleaning itself up.

Even though half the world blindly sends SIGKILL after 5 seconds it’s still horribly wrong thing to do.

More Related Contents:

  1. Why can’t I use job control in a bash script?
  2. Run a shell script and immediately background it, however keep the ability to inspect its output
  3. Signals received by bash when terminal is closed
  4. How to send a signal SIGINT from script to script?
  5. What does `kill -0 $pid` in a shell script do?
  6. Echo newline in Bash prints literal \n
  7. In the shell, what does ” 2>&1 ” mean?
  8. ssh breaks out of while-loop in bash [duplicate]
  9. Remove a fixed prefix/suffix from a string in Bash
  10. I just assigned a variable, but echo $variable shows something else
  11. Bash how do you capture stderr to a variable? [duplicate]
  12. How to use aliases defined in .bashrc in other scripts?
  13. Should aliases go in .bashrc or .bash_profile? [duplicate]
  14. How to read user input into a variable in Bash?
  15. How to provide password to a command that prompts for one in bash?
  16. Deleting lines from one file which are in another file
  17. source command not found in sh shell
  18. How to check if a file contains a specific string using Bash
  19. How to enter ssh password using bash? [duplicate]
  20. What is a unix command for deleting the first N characters of a line?
  21. How do I escape slashes and double and single quotes in sed?
  22. How can I get a recursive full-path listing, one line per file?
  23. How to suppress variable substitution in bash heredocs
  24. How to pipe stdout while keeping it on screen ? (and not to a output file)
  25. How to wait for an open port with netcat?
  26. run bash command in new shell and stay in new shell after this command executes
  27. How to produce cartesian product in bash?
  28. Read n lines at a time using Bash
  29. Missing Carriage Return in Docker for Mac Containers
  30. How do I kill a backgrounded/detached ssh session?

Leave a Comment