I wrote some code that might help you out: it in the thread:http://groups.google.com/group/django-users/browse_frm/thread/b36f4ca10a424161/c5131410e5d548b1Depending on how you spawn a process, it can either wait for each, or become a child process.Calling the daemonize method with the appropriate p
Well, limited success. I was able to get the code working through
closing the django db connection just after I'd forked my processes,
but it seems that what I thought I was doing wasn't really what I
thought I was doing.
Essentially I wanted to be able to run multiple tasks simultaneously. I
tho
Thanks, that's very helpful, and sounds very likely to be the problem.
I'll give it a try and see what I can come up with...
May take a little while but I'll post back once I have a resolution one
way or the others.
Cheers, Tom
--~--~-~--~~~---~--~~
You received
I think I had this problem, at least it feels very familiar, and I do
some process forking.
I think that the problem is using the same connection more than once.
I think that the cursor is being closed and then being used again.
I took the habit of creating a new cursor and specifically clos
Hi Folks,
I know this topic has been brought up a few times, but I have a
slightly different issue here (I think).
I have a backend process that runs a number of commands. It connects to
the database (via the ORM) to check it's queue and then executes jobs.
All fine and dandy.
My problem is tha
5 matches
Mail list logo
