The one "leak" process per hour coincident is "coincidently" matching the one run per hour of admin/cron/expire_sessions.py
That really raises my concern, cause I just gonna use cron as a trick to touch my app's cache frequently. :-/ By the way, which os is Mike Ellis using? I did not observe same problem on web2py 1.81.5, binary package, on Windows XP. No increasing process, just the file handlers may slightly increased by one or two per minute. But, file handlers will become stable after a total 20-or- so increase, within half an hour. So perhaps situation is not that bad. (Tips: to shorten the test time, I change the crontab time gap to minimal one minute.) Regards, Iceberg On Jul 29, 6:15am, mdipierro <mdipie...@cs.depaul.edu> wrote: > There clearly is a problem with the cron processes. > > Massimo > > On Jul 28, 4:10 pm, MikeEllis <michael.f.el...@gmail.com> wrote: > > > > > Update: (Summarizes a couple of emails exchanged with Massimo) > > > Yesterday I found that my instance of web2py appeared be "leaking" > > processes at about 1 per hour. Massimo suggested running with -N to > > disable cron. I started two instances this way -- one under winpdb > > and another directly. They've been running almost 24 hours now and > > neither has added any processes. As noted earlier, my app has nothing > > in crontab. The admin and examples apps have the crontabs that are "as > > shipped" in v1.85. > > > Cheers, > > Mike > > > On Jul 27, 12:17 pm, Jonathan Lundell <jlund...@pobox.com> wrote: > > > > On Jul 27, 2010, at 9:01 AM, Michael Ellis wrote: > > > > > Thanks for the info about sloth. I may try it later. It was pretty > > > > easy to get what I needed with ipython: > > > > > procs = !ps ax | grep "web2py" > > > > pids = [r[0] for r in procs.fields()[0:-2]] > > > > for p in pids: > > > > print p > > > > !lsof | grep $p | wc > > > > Also: sudo launchctl limit maxfiles > > > > I see 256 by default. The second limit is the "hard limit", beyond which > > > you can't configure (unlimited in this case).
