> You should be able to do:
> supervisorctl restart chat
Hello,
Thank you for the idea but I am unable to make it work:
[nginx]# supervisorctl
chat:chat_00 RUNNING pid 783, uptime 3 days, 12:26:29
chat:chat_01 RUNNING pid 784, uptime 3 days, 12:26:29
chat:chat_02 RUNNING pid 781, uptime 3 days, 12:26:29
chat:chat_03 RUNNING pid 782, uptime 3 days, 12:26:29
supervisor> restart chat
chat: ERROR (no such process)
chat: ERROR (no such process)
supervisor> restart chat.toff
chat.toff: ERROR (no such process)
chat.toff: ERROR (no such process)
my supervisord.conf contains the following lines:
131 [fcgi-program:chat]
132 command=/nginx/chat.toff
133 socket=tcp://127.0.0.1:9000
134 process_name=%(program_name)s_%(process_num)02d
135 numprocs=4
136 priority=999
137 autostart=true
138 autorestart=unexpected
139 startsecs=1
140 startretries=3
141 exitcodes=0,2
142 stopsignal=QUIT
143 stopwaitsecs=10
At this point, my sole option is still a shutdown, which ia a bit radical.
Thanks for any help
> You should be able to do:
>
> supervisorctl restart chat
>
> On Wed, Jun 9, 2010 at 12:29 PM, <[email protected]> wrote:
>
>> Hello,
>>
>> How does supervisord handle a new version of a registered process?
>>
>> I have this in my conf file:
>>
>> [fcgi-program:chat]
>> command=/path/chat.toff
>> socket=tcp://127.0.0.1:9000
>> When I have a new version of the chat.toff, what should I do?
>>
>> Right now I am replacing chat.toff with the new version and I run a
>> script
>> containing:
>> supervisorctl shutdown
>> supervisord
>>
>> There has to be better ways!
>>
>> Thank you
>>
>> _______________________________________________
>> Supervisor-users mailing list
>> [email protected]
>> http://lists.supervisord.org/mailman/listinfo/supervisor-users
>>
>
_______________________________________________
Supervisor-users mailing list
[email protected]
http://lists.supervisord.org/mailman/listinfo/supervisor-users
