On Thu, Nov 6, 2008 at 5:40 PM, Alvaro Lopez Ortega <[EMAIL PROTECTED]> wrote:
>> Please, give a look to "contrib/cherokee". I think we must send
>> signals to "cherokee" instead "cherokee-worker".
>
> You are completely right Antonio. The init.d script ought not to send
> signals to cherokee-worker, nor check its PID file.
>
> I haven't had time to check where the problem is, although I'm certain that
> cherokee-worker has nothing to do with it.
>From start-stop-daemon manpage:
-K, --stop
Checks for the existence of a specified process. If
such a process exists, start-stop-daemon sends it the signal
specified
by --signal, and exits with error status 0. If such a
process does not exist, start-stop-daemon exits with error status 1 (0
if --oknodo is specified). If --retry is specified, then
start-stop-daemon will check that the process(es) have terminated.
So we must send SIGTERM signal, and the init script included in Ubuntu
package don't do it. "--retry" is a good param too.
The problem here is that Ubuntu init script doesn't send any signal to
"cherokee", don't wait until it finishes and remove the PIDFILE. So,
when it is running and the script has deleted the PIDFILE.
Then, cherokee status check that PIDFILE not exits and print that
cherokee is not running, but this is not truth... :)
I hope you understand what I mean with poor English.. ;)
--
Saludos:
Antonio Pérez
ATENCIÓN: Antes de imprimir este mensaje valora si verdaderamente es necesario.
De esta forma contribuimos a la preservación del Medio Ambiente.
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
