From: Aryeh Leib Taurog <[email protected]> > I have a bunch of cron jobs that run `supervisorctl start suchandsuch` > and for the most part I make the processes themselves responsible for > exiting at the right time (say, after market close).
This is what I was leaning towards, but it seems a bit unproductive to manage two sets of app configuration, 1 in supervisord and 1 in cron - I would prefer to be able to specify start and stop times in my supervisord config and have it supervise the starting and stopping > I also make the processes responsible for handling changes in start > time due to other factors like daylight savings. The cron jobs start > everything before the earliest time and the processes sleep until the > correct start time for the current date. This is an interesting concept, clever solution to a common problem. Thanks for the input ~Steve
_______________________________________________ Supervisor-users mailing list [email protected] https://lists.supervisord.org/mailman/listinfo/supervisor-users
