The existing priority parameter would accomplish the same thing as a new depends parameter, yes? It seems to me like all cases for depends can be mapped to use priority but not vice-versa. With priorities, you can create a config where everything that has the same priority gets started concurrently but each priority level is started after the previous one completes. That would allow you specify which parts of your config need start order dependencies and which don't.
On Wed, Sep 9, 2009 at 2:33 PM, Lennart Regebro <[email protected]> wrote: > 2009/9/9 Lennart Regebro <[email protected]>: > > 2009/9/9 Roger Hoover <[email protected]>: > >> In that blog post, it says there was a way to avoid the need for > >> staggering. Is there a real use case for this? > > > > Yes. > > I forgot to add this: Although I can't come up with something that > wouldn't be better served by the "depends" parameter mentioned by > Chris. > > -- > Lennart Regebro: Python, Zope, Plone, Grok > http://regebro.wordpress.com/ > +33 661 58 14 64 >
_______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
