Perfectly fine.....it's the recommended way! Apache & co. kill processes that hang up (usually a certain timeout) because normally a page "should" return something in a small timeframe. This feature is useful to free up resources if the code to generate your webpage is too heavy on the machine, and to let the webserver serve other requests.
A scheduler instead is a "never-ending" process (it's sort of the apache process) that manages other processes to do your tasks, in a totally separate environment from apache itself (so apache is free, and your users happy). Having a scheduler "managed" by apache is infact "killing the purpose" of the scheduler. Il giorno venerdì 7 settembre 2012 14:32:09 UTC+2, David Marko ha scritto: > > How to use sheduler when running web2py in apache + mod_wsgi scenario ? Is > it ok to run it as ussual I mean start it separately from apache-wsgi' > python > web2py.py -K myapp:group1:group2,myotherapp:group1' ? No problem with > this? > --
