On Fri, 20 Feb 2009 11:13:11 +0200, Dalius Dobravolskas <[email protected]> wrote: >On Fri, Feb 20, 2009 at 10:05 AM, Dalius Dobravolskas ><[email protected]> wrote: >> Hello, >> >> On Fri, Feb 20, 2009 at 8:30 AM, Dalius Dobravolskas >> <[email protected]> wrote: >>> 3. Is settimeout actually working? If I run following code (please >>> don't run it on my server): >> OK. Everything is OK in PyPy code. timeout works (at least log >> indicates that). There is something specific about mod_wsgi and Apache >> in this case. >That's what I have found out: >pypy-c when running behind Apache can't be SIGTERMed only SIGKILLed. >That's how I solved problem now (modifed pypy/tool/killsubprocess.py). >I will dig deeper of course but I will do that later.
Check out the sigprocmask Apache sets for itself. Unfortunately, this is inherited by all processes Apache runs, usually leading to surprising behavior, since it prevents the delivery of almost all signals. Jean-Paul _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
