|
Home > Archive > Apache Mod-Python > November 2005 > Re: 3.2b5 : mod_python doesn't handle properly signals likeKILL,SEGV...
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: 3.2b5 : mod_python doesn't handle properly signals likeKILL,SEGV...
|
|
|
| for myself, I have not had problems on ubuntu 5.10 amd64.
Nick
Jim Gallacher wrote:
> Michel Jouvin wrote:
>
>
>
> I have no idea what may be going on, but that seems as likely as
> anything else.
>
>
>
> Again, no clue.  . Hopefully some of the bigger brains that hang out
> around here will chime in. I know Indrek Järve tested 3.2.2b on SuSE
> Linux 9.2 (x86-64). Perhaps he or someone else with a 64-bit platform
> could try and reproduce the problem. That would tell us if it's 64-bit
> related or Tru64 related.
>
> I've attached my test script if anyone wants to mess with it. I'm sure I
> don't need to tell you to *not* run it on a production machine. ;)
> You'll likely want to change the PAUSE variable to something less than
> 30 seconds, which is the time between the kill calls. I was testing
> using qemu, and it needs lots of time for things to happen.
>
> usage: ./killchildren <# number of loops>
>
> Jim
>
>
>
|
|
|
|
|