axkibe/lsyncd — Issue #101: When SIGTERM is received, lsyncd shouldn't exit-code with 0, but with 143
Author: brainstorm
Created: 2011-11-21 15:50:11+00:00
State: open

@b97pla and I just realized that supervisord[1], our process monitor, didn't respawn lsyncd properly when killed with SIGTERM since 0 means "all right, normal exit":

"The return code 0 means a normal exit. If there was a SIGTERM, $? would be set to 143 (128 + signal number)"

See the following thread for more info:

http://unix.stackexchange.com/questions/10231/when-does-the-system-send-a-sigterm-to-a-process

[1] http://supervisord.org/