On Tue, Sep 20, 2011 at 10:25 AM, Cody Robertson <[email protected]> wrote: > On 9/20/2011 1:13 PM, Izzy Alanis wrote: >> >> Is there no 'disabled' state for programs managed by supervisor? >> >> In windows services, you have "Manual", "Automatic" and "Disabled" >> startup types. >> In linux, you have chkconfig --del<name> to disable a service. >> >> I know there's the autorun setting for a program, but from an >> operator's perspective, if you know enough to start and stop programs >> from supervisorctl, I'd like to be able to disable the services there >> too, rather than have the operator go in an manually edit config >> files. >> >> I thought for a minute that supervisorctl remove<program> might do >> what I wanted, but... I'm not really sure what that does (other than >> maybe force supervisor to forget about that program for a while. It >> certainly doesn't survive a restart). >> > > I haven't tested this but perhaps using the "stop" function and then > "remove"?
that won't survie a restart. edit the supervisord.conf for your program and change autostart=false supervisorctl reread # should give you a preview of what's to come supervisorctl stop <program_name> supervisorctl remove <program_name> supervisorctl add <program_name> when you want re-enable, edit the config and repeat. there's probably a way to do this through the xmlrpc interface, but i edit program.conf files programmatically for other reasons. > > -- > supervisor> help stop > stop <name> Stop a process > stop <gname>:* Stop all processes in a group > stop <name> <name> Stop multiple processes or groups > stop all Stop all processes > -- > _______________________________________________ > 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
