We would like to use supervisor in the following scenario: each customer has a pair of processes started for them on signup. These processes run continually while the customer is paying for the service. As they stop paying, the processes are stopped.
The nature of this service is such that these processes have long-lived socket connections. It appears supervisor is excellently suited to handle this scenario, except for one thing: there seems to be no way of telling supervisor to reload its configuration short of restarting it, which means restarting all its supervised processes - in our use case an unacceptable proposition, as it would terminate all the customer socket connections. Would it be feasible to implement a reload config operation? Ideally, we would like to have an include /etc/supervisor.d/*.conf which is reread on reload and only services which have had their configuration changed would be restarted (or stopped if they are no longer in the conf). -- Anders Qvist, Open End AB Tel: +46 31 7490887 _______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
