On Tue, Apr 15, 2008 at 2:51 PM, Mike Naberezny <[EMAIL PROTECTED]> wrote:
> Noah Gift wrote: > > > +1 on Cron replacement. I might even be persuaded to help at some point > > this year time depending. I like the idea of Python replacing Cron too. > > > > > One thing that hasn't been mentioned is that Supervisor already has the > ability to periodically notify an eventlistener subprocess using the TICK_* > events. http://supervisord.org/manual/3.0a4/events.html#id931965 > > A good example of this is the memmon.py program that ships with > Supervisor. It uses the TICK_* events to periodically check the memory usage > of a process. It then uses supervisor.childutils to get an XML-RPC > connection to Supervisor to restart processes as needed. > > You could implement a scheduling program by writing an eventlistener > subprocess in the same way as memmon.py instead of modifying the Supervisor > core. I like this approach because it is in-line with what we've done with > memmon.py. > > If there's demand for this functionality and it is implemented well, I > can't see why we wouldn't package it as an accessory program like memmon.py. > > Regards, > Mike sounds very interesting. Sorry I meant to respond earlier, but yes, I have had paying consulting jobs where I had to deal with Python and cron at the same time, and it was a PITA to have manage, Bash, cron, and the Python code I wrote and make it all work at exactly the same time. If it lives in one spot, it is much easer to write tests for. In fact, I got burned with a very subtle bug, as it was just about impossible to test the code under those conditions. > > > -- > Mike Naberezny > Maintainable Software > http://maintainable.com >
_______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
