On Tue, Apr 24, 2012 at 11:30 AM, Bob Corsaro <[email protected]> wrote: > it does pick up new processes, but not changed processes. any other > solution?
from supervisord POV, a program is only changed if the program config changed. in our org, we put versions in the paths to the current running version of a command. supervisord is set to watch /data/local/*/etc/supervisord.d/*.conf that path expands out to the current program.conf for every supervise'd program. > > > On Tue, Apr 24, 2012 at 2:26 PM, David Birdsong <[email protected]> > wrote: >> >> On Tue, Apr 24, 2012 at 11:00 AM, Bob Corsaro <[email protected]> wrote: >> > I'm using chef to manage configuration and supervisor to manage >> > processes on >> > nodes. Currently, when chef changes a supervisor conf file in >> > /etc/supervisor/conf.d, it issues a supervisorctl reload. The problem I >> > have >> > with this method is that it restarts every process. Is there a way I can >> > get >> > supervisor to reread the config files and only reload the processes that >> > have changed? I've tried supervisorctl reread and it doesn't seem to do >> > anything. >> >> as mentioned, 'update' will only affect programs with an updated config. >> >> if you needed something more granular to update a single program by name, >> do: >> >> supervisorctl reread >> supervisorctl stop <program> >> supervisorctl remove <program> >> supervisorctl add <program> >> supervisorctl start <program> # optional step if autostart=True >> >> > _______________________________________________ >> > Supervisor-users mailing list >> > [email protected] >> > http://lists.supervisord.org/mailman/listinfo/supervisor-users >> > > > _______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
