On Sat, 2010-05-01 at 18:49 -0700, kevin beckford wrote: > > > On Sat, May 1, 2010 at 6:46 PM, kevin beckford <[email protected]> > wrote: > ? > > > Supervisor is no different than any other program in > this respect. It > needs to be started at startup. There's a sample > Debian start script at > http://svn.supervisord.org/initscripts/debian-norrgard > that might be > helpful. > > > > > > > > > > (Sorry, forgot to cc the list. Damn Gmail.) > > > Great. This is also what I thought. So I'm a bit confused then: > > > If I need to start supervisor with a debian init script, then why > build it in a buildout? Should I not just install supervisor > systemwide, and create the configuration files for the applications in > my buildout? What's the benefit of building supervisord for each > buildout?
I don't know. If you see none, there isn't any. - C _______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
