[Supervisor-users] Managing php-cgi - Doesn't auto-restart

[Tom Barrett]

2009/12/14 Chris McDonough <chrism at plope.com>

> Tom Barrett wrote:
>
>> 2009/12/14 Chris McDonough <chrism at plope.com <mailto:chrism at plope.com>>
>>
>>
>>    Please try running supervisor like so:
>>
>>    supervisord -n -edebug
>>
>>    This will run it in the foreground with the debug log printing to
>>    stdout, including child process output, which might give you a clue.
>>
>>
>> How should I simulate the php-cgi process dying? I don't know what
>> constitues an 'unexpected quit'. A simple 'kill <pid>' appears to be an
>> 'expected quit'.
>>
>
> Nobody could know.  I'd just let it run for a while.  Note that you can run
> supervisord in the background but still log at debug level via:
>
> supervisord -edebug
>
> The log message will end up in supervisord.log
>

So there is no way that I can simulate php-cgi going down to see whether
supervisor actually works? Sorry, but that strikes me as borderline useless.
I have, so far, absolutely no evidence that supervisor is any better than
launching programs from the shell and checking them manually.

How do I poke the beast to make it *do* something? Can I set supervisor to
restart php-cgi no matter why it dies? If not, then I give up.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.supervisord.org/pipermail/supervisor-users/attachments/20091214/c60eba5b/attachment.htm