On 5/18/09 10:49 AM, Stephan Zeissler wrote:
> Hi everyone,
>
> im new to supervisord but I like it so far :)  I tried to setup a simple
> test setup which raised some questions:
>
> 1) Are priorities really used? I setup 3 programs in a group with
> different priorities and they are started in a different order than
> their priorities suggested:
> 2009-05-18 15:38:46,898 INFO spawned: 'Smtpd' with pid 7439
> 2009-05-18 15:38:46,903 INFO spawned: 'ActiveMQ' with pid 7440
> 2009-05-18 15:38:46,918 INFO spawned: 'Stomp2SmtpTransport' with pid 7441
> ActiveMQ should have been the first (its the first in the config and has
> the lowest priority). As all programs are started at the same time, this
> also could be outputbuffer problem (the pid suggests otherwise).
> If priorities are used, whats their benefit if they seem to be started
> mostly parallel? I (initially) expected supervisord to start the
> processes one after another (Use case: first programm sets up a
> listening socket, next programm connects to it; currently the second
> process is restarted until it gets the connection)

Priorities aren't really very useful.  They just name the order in which things 
are started; they don't imply a dependency order.

> 2) Whats the benefit of groups? I thought of any of these:
> - Control a group with the web/supervisorctl interface:
> start/stop/restart/status<group>
> - If a process in a group dies, the programs in the group should be
> restarted following a given restart strategy (See the use case above)
> I didn't find anything why I should use groups. What did I miss?

You're assuming there's some sort of dependency structure.  There isn't.  A 
group is just a group that can be addressed as a whole.

Others have wanted dependencies, and it's even possible to get them right now 
if 
you use event listeners (in a highly complicated way) but there's nothing easy 
that gets it for you now.

- C
_______________________________________________
Supervisor-users mailing list
[email protected]
http://lists.supervisord.org/mailman/listinfo/supervisor-users

Reply via email to