Hi,

I'm sending this mail after a brief discussion about an upcoming Nginx
web server module we're sponsoring. Its purpose is to manage processes
by communicating with supervisord in response to varying load. I have a
question about program groups: AFAIK program names have to be globally
unique, so referring to a group member by its unqialified _program_ name
should be sufficient, no? As it stands, in a config like this:

[program:cat0]
command = /bin/cat

[program:cat1]
command = /bin/cat

I can start, restart etc. the programs by calling them "cat0" and "cat1"
in the XMLRPC interface. But if I add:

[group:herd]
programs = cat0,cat1

I now need to call them "herd:cat0" and "herd:cat1", which prevents me
from managing them using my Nginx module (it has some restrictions on
allowed program names). Is there a design decision behind this? Or is
this subject to change before 3.0 final comes out?

Best regards,
 Grzegorz Nosek
_______________________________________________
Supervisor-users mailing list
[email protected]
http://lists.supervisord.org/mailman/listinfo/supervisor-users

Reply via email to