[web2py] Re: Monitoring scheduler with supervisord

2012-09-20 Thread Yarin
Any luck with this Simone? On Friday, September 14, 2012 12:39:19 PM UTC-4, Niphlod wrote: ok, give me a few hours, I need to get home first :P --

[web2py] Re: Monitoring scheduler with supervisord

2012-09-20 Thread Niphlod
no free time at home to test on every platform, but the code part is done. in a few days. On Thursday, September 20, 2012 6:09:59 PM UTC+2, Yarin wrote: Any luck with this Simone? On Friday, September 14, 2012 12:39:19 PM UTC-4, Niphlod wrote: ok, give me a few hours, I need to get home

Re: [web2py] Re: Monitoring scheduler with supervisord

2012-09-20 Thread Yarin Kessler
You the man On Thu, Sep 20, 2012 at 12:13 PM, Niphlod niph...@gmail.com wrote: no free time at home to test on every platform, but the code part is done. in a few days. On Thursday, September 20, 2012 6:09:59 PM UTC+2, Yarin wrote: Any luck with this Simone? On Friday, September 14,

[web2py] Re: Monitoring scheduler with supervisord

2012-09-14 Thread Yarin
@Niphlod- I was hoping this embedded mode patch was going to become part of the 2.0 implementation. I see you added a -X flag to allow for launching the scheduler alongside an app, but we can't use this in our situation where web2py is running as wsgi under Apache while our scheduler processes

[web2py] Re: Monitoring scheduler with supervisord

2012-09-14 Thread Niphlod
Scheduler is not useful if managed by a webserver, so forget about -X: just like softcron, it is meant to be used when the internal webserver is used, not when web2py is managed by apache co. Having a master starting the actual workers is needed to have multiple workers started with one

[web2py] Re: Monitoring scheduler with supervisord

2012-09-14 Thread Yarin
Right, I was just voting for having the script integrated into web2py outright, so that calling it with maybe a lowercase -k would execute a single scheduler process without spawning subprocesses. On Friday, September 14, 2012 11:57:49 AM UTC-4, Niphlod wrote: Scheduler is not useful if

[web2py] Re: Monitoring scheduler with supervisord

2012-09-14 Thread Niphlod
well, maybe we can support not spawning if -K is followed by one app only. Thoughts ? On Friday, September 14, 2012 6:16:08 PM UTC+2, Yarin wrote: Right, I was just voting for having the script integrated into web2py outright, so that calling it with maybe a lowercase -k would execute a

[web2py] Re: Monitoring scheduler with supervisord

2012-09-14 Thread Yarin
Sure that works for me On Friday, September 14, 2012 12:25:02 PM UTC-4, Niphlod wrote: well, maybe we can support not spawning if -K is followed by one app only. Thoughts ? On Friday, September 14, 2012 6:16:08 PM UTC+2, Yarin wrote: Right, I was just voting for having the script

[web2py] Re: Monitoring scheduler with supervisord

2012-09-14 Thread Niphlod
ok, give me a few hours, I need to get home first :P --

[web2py] Re: Monitoring scheduler with supervisord

2012-08-15 Thread Niphlod
Because web2py let you launch multiple schedulers with web2py.py -K myapp,myapp or web2py.py -K myapp1,myapp2 the actual scheduler process is a subprocess of the main one you launch with web2py.py. If you launch with the external method, as python gluon/scheduler.py -t tasks.py -f etc no

[web2py] Re: Monitoring scheduler with supervisord

2012-08-15 Thread Yarin
The embed-mode script works great and allows us to use Supervisord- Thanks-- On Wednesday, August 15, 2012 11:44:18 AM UTC-4, Niphlod wrote: Because web2py lets you launch multiple schedulers with web2py.py -K myapp,myapp or web2py.py -K myapp1,myapp2 the actual scheduler process is a