This might sound "stupid". but I use the include files in the supervisord.conf and make supervisor to lookup for *.ini file, so if I want a process to be "ignored" by supervisor I rename the file to file.ino
That's the only way I've come up to handle a manual add to a process I'm "debugging " On Thursday, August 14, 2014, Jonathan Vanasco <supervis...@2xlp.com> wrote: > This might be a bit of an edge case, not sure. I'm wondering how others > handle this. > > We shut down one of the processes run by supervisord during an extended > deployment ( i.e. `supervisorctl stop process`) > > Part of the maintenance window included updating some packages on the > server and provisioning some new resources for the VPS. a reboot got > triggered. > > on reboot, supervisod started up and then did what we'd normally want it > to -- start all the processes. except we didn't want this process started > -- as it had been purposefully shut off before the reboot. > > Does anyone have tips/tricks for persisting an "off" across reboots? > _______________________________________________ > Supervisor-users mailing list > Supervisor-users@lists.supervisord.org <javascript:;> > https://lists.supervisord.org/mailman/listinfo/supervisor-users >
_______________________________________________ Supervisor-users mailing list Supervisor-users@lists.supervisord.org https://lists.supervisord.org/mailman/listinfo/supervisor-users
