Since I have access to my system's own cron service I use *external cron* The issue seems to be that
*/5 * * * * ~/webapps/w2p/web2py/web2py.py -S admin -R scripts/sessions2trash.py & */5 * * * * ~/webapps/w2p/web2py/web2py.py -S mypynex -R scripts/sessions2trash.py & are starting web2py and its cron sub system, which stays resident in memory which is why web2py processes start to pile up. I had a similar issue with this line in my crontab: 19,39,59 * * * * ~/webapps/w2p/apache2/bin/start using the watchdog script Sean wrote, commenting out the first line and adding the second line: #19,39,59 * * * * ~/webapps/w2p/apache2/bin/start */5 * * * * $HOME/bin/watchdog_w2p.sh >> $HOME/logs/user/w2p_watchdog.log 2>&1 Since web2py is already running can't I call the sessions2trash.py script in a similar way as I call the watchdog script. Why call web2py.py? Regards, Annet -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
