On Tue, 2007-03-13 at 08:10 -0700, Ino Pua wrote: > Using just 'ls' or something similar does not trigger the bug. You > have to start a daemon from django in order to trigger it. The > attached views assume cmd to be a command that takes 'start' as a > parameter in order to daemonize it, so for freebsd you might have to > customize the " p = subprocess.Popen([cmdname, 'start'], > stdout=subprocess.PIPE) " line in order to start your daemon.
I suspect this really a Django problem. It sounds like, despite the attempt to daemonize the process, the init script isn't properly shutting down or something and so the process that is executing mod_python and that particular view hasn't finished yet (it still has a child process). One way to check this out would be to check out the state of /proc/<pid>/fd and the like (it sounds like you're on a Linux system) to see if there are file handles to your subprocess command still open. Basically, you need to investigate at the sytsem level and work out why the python function does think its work is done yet. There is nothing really Django specific going on here that I can see, but deeper investigation may prove otherwise. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
