Lighttpd

lighttpd ignores SIG_USR1, which is inherited trough exec():

http://www.opengroup.org/onlinepubs/000095399/functions/exec.html:

Except for SIGCHLD, signals set to be ignored (SIG_IGN) by the calling process image shall be set to be ignored by the new process image.

I guess resetting the ignored signals to the default behaviour should fix this.

i applied changeset r2582 to lighttpd 1.4.23,
the spawned process still doesn't respond to SIGUSR1
and stopping lighttpd doesn't stop the spawned process.

Could you please try adding a "setsid();" call before the exec call (where the signal(..) calls were added)?

unfortunately, no luck with this :

reset_signals();
setsid();
/* exec the cgi */
execve(arg.ptr[0], arg.ptr, env.ptr);

also note that i got several other spawned processes :

www-data 27248     1  0 16:47 ?        00:00:00 /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf
www-data 27251 27248  1 16:47 ?        00:00:00 /usr/bin/php-cgi
www-data 27255 27251  0 16:47 ?        00:00:00 /usr/bin/php-cgi
www-data 27257 27251  0 16:47 ?        00:00:00 /usr/bin/php-cgi
www-data 27258 27248 32 16:47 ?        00:00:00 /usr/bin/octave -qf /home/dev/WORKSPACES/climelioth/octave/main.m --fcgi
www-data 27259 27248 32 16:47 ?        00:00:00 /usr/bin/octave -qf /home/dev/WORKSPACES/climelioth/octave/main.m --fcgi
www-data 27260 27248  3 16:47 ?        00:00:00 /home/dev/public_html/webkitpdf/webkitpdf-fcgi
www-data 27261 27248 72 16:47 ?        00:00:00 ruby /usr/share/redmine/public/dispatch.fcgi
www-data 27262 27248 69 16:47 ?        00:00:00 ruby /usr/share/redmine/public/dispatch.fcgi

well signal 10 is sigbus. not a proper signal to kill your apps. maybe try 15? which would be SIGTERM.

not on my debian distrib :

kill -l USR1

10

kill -l BUS

7

of course i could use kill-signal 9, but that would not be very graceful.

it is still buggy with the patch, but something strange is happening :
when i start lighttpd, i have two ruby processes launched
if i don't use the ruby webapp (here it's redmine), then stop lighttpd, the two instances are not killed.
if i use the webapp, browse some pages, then stop lighttpd, ONE instance is killed, not the other.

Could you please check if you still can't kill them manually with kill -USR1 ?

There may have been two problems: 1. ignoring the signal and 2. lighty didn't send a signal

i checked again, the answer is no.
i tried on the other fastcgi instances, and it works on them.

i also added logs to see if lighttpd was sending the signal,
and i can confirm that :

kill(proc->pid, host->kill_signal);

Looks like there is/was a problem with ruby-fcgi (different behaviour in ruby and c implementation), see http://dev.rubyonrails.org/ticket/8704 .