On czw, paź 22, 2009 at 03:05:32 -0700, Roger Hoover wrote: > > It works like that out of the box? If so, that's great news and it means > > our module can manage every possible program. > > > > I was thinking that the nginx module would keep this mapping. For each fcgi > pool, it would have an nginx backend name (test__foo_) and a supervisor name > (test:foo_). When the module is doing routing stuff, it would use backend > name but when it's spawning and reaping processes, it would use the > supervisor name. Is something like this doable?
Well, everything is ;) but I read your post as saying that supervisord works like that by default. We can certainly add such a feature (would probably allow to specify a printf format given the backend number) but we want to release the module rather soon and add features later, so version 1.0 won't support it. Still, I expect a follow-up version rather soon (some bugs are certain to surface) and we may be able to squeeze this feature there. Best regards, Grzegorz Nosek _______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
