Hello Graham,
I tracked that as well to see if it is actually a zombie process or
not
See the following (ps -fH -u davo)
=== Request to the WSGI is still running (timeout of 30 seconds not
reached yet) ==
UIDPID PPID C STIME TTY TIME CMD
davo 2844 2834 0 11:29
No worries,
thanks !
I will try to investigate more and will post
here if I find the issue or solution.
Davo
On May 13, 10:43 am, Graham Dumpleton graham.dumple...@gmail.com
wrote:
On 13 May 2010 19:37, Davo david.arakel...@gmail.com wrote:
Hello Graham,
I tracked that as well to see
Hi all,
If I have a WSGI running as daemon mode and my python code is:
p = subprocess.Popen(['watch -n 5 echo aaa'],
stdout=subprocess.PIPE, stderr=subprocess.STDOUT,
shell=True).communicate()[0].strip('\n')
The watch goes background and never ends. Even when I kill the wsgi
daemon it still
btimby,
I am aware it will never exit (that's why I tried watch)
The whole issue is I want to prevent users to run long programs. I was
thinking that once the daemon dies or timeouts it will
evantually kill/clean all the children as well.
Sorry for confusion :)
--
You received this message
Thanks for the reply I finally gave up the idea of having a chrooted
environment
I went with the solution to restrict the other directories instead.
I also tried to strace python to see what files/libs are opened so I
can give access too but it ended up
to be some files in /etc /usr and /lib ...
Hi all,
I am running the following setup:
running apache with mod_wsgi and
virtual...
SetEnv PYTHONHOME /home/xxx/usr/local
SetEnv PYTHONPATH /home/xxx/usr/local/lib/python2.6/
WSGIDaemonProcess xxx.com user=daemon group=daemon processes=2
threads=25 chroot=/home/xxx
WSGIProcessGroup
