On 10 August 2011 07:11, Massimo Di Pierro <massimo.dipie...@gmail.com> wrote:
> On Aug 9, 6:13 pm, Fran <francisb...@gmail.com> wrote:
>> I have problems under Windows with
>> python web2py.py -K app
>> I guess this is due to MultiProcessing
> Can you check whether it is a reporting thing only but it is doing the
> work?

It is not doing the work.
Memory consumption balloons as it keeps respawning over & over.

>> It works fine with:
>> python web2py.py -S app -M -N -R scheduler.py
>> Where that file contains:
>> current._scheduler.worker_loop(heartbeat=20)
>> However I don't get any feedback on status or anything.


>> I'd also love to see it possible to start as a secondary process from core
>> Web2Py
> We could add a command line option to start it before starting web2py.
> What I would like to prevent is using scheduler and cron at the same
> time.
> This would create too many processes.

Fine with having the scheduler flag imply -N
This is indeed logical :)

>> If cron worked in Windows service mode then @reboot would be perfect, but it
>> doesn't so I'd need to freeze a 2nd web2py instance & add a 2nd service
>> wrapper?
> I did not know cron does not work under windows. It used too. Can you
> tell us more? When did it get broken?

It's service mode where it's broken.

https://groups.google.com/d/msg/web2py/WwG6YXteb14/s4WSGcK9l7AJ
https://groups.google.com/d/msg/web2py/OX7pXEGlSGM/TQbp966ZGUUJ

F

Reply via email to