It was my understanding that Python's GC frees any resources not explicitly freed, and cron runs jobs in a try/except/finally block and rolls back any uncommitted transactions.
I have reproduced the issue with the three running sequentially, and in every case, the logs indicate that my functions exit, meaning that the rollback (I'm committing) and GC actions should occur, or at the very least, the OS should close/release stuff when the crom process exits. Hmmm.. This is going to be interesting to track down. On Wed, Jul 6, 2011 at 5:56 AM, Massimo Di Pierro < massimo.dipie...@gmail.com> wrote: > Yes that is the problem wit cron issue. If one of the processes locks > a resource, cron does not know about it and keeps spawning processes > as scheduled. The new processes find the resource locked and freeze of > crash but use ram. This is not a bug because cron is not supposed to > know what the tasks do. This is a general logic problem with cron. > Using one single background process that loops and sleeps is much > safer. > > Massimo > > On Jul 6, 1:34 am, ron_m <ron.mco...@gmail.com> wrote: > > Sounds like some kind of race condition between the cron scripts because > it > > doesn't happen every time. Is there any chance the 3 cron scripts are > > dependent on each other in some way such as a file passed between or > sharing > > a database. If there is any relationship between the cron scripts would > it > > be possible to make a single script that just runs the 3 scripts > > sequentially and use that as your cron script. Do the scripts access the > > database and the database happens to be SQLite which locks for the > duration > > of an access/ > > > > Without seeing some code and more details determining the cause is a > guess. > > > > Ron > -- John Duddy jdu...@gmail.com
