In article <7aea1500-aebc-4585-97c3-ba15f5dc7...@n20g2000vba.googlegroups.com>,
msoulier wrote:
>On Mar 25, 10:27=A0am, a...@pythoncraft.com (Aahz) wrote:
>
>> That's a bit bizarre. =A0You're correct that if this is a Python bug, the=
>re
>> will be no fixes available. =A0However, you said earlie
On Mar 25, 10:27 am, a...@pythoncraft.com (Aahz) wrote:
> That's a bit bizarre. You're correct that if this is a Python bug, there
> will be no fixes available. However, you said earlier that this is a
> patched Python, so I'm wondering whether the applied patch is broken.
> Assuming I'm reading
In article <5cffe00b-2cd3-45dc-a674-87466e8ff...@f19g2000vbf.googlegroups.com>,
msoulier wrote:
>On Mar 20, 10:22=A0am, a...@pythoncraft.com (Aahz) wrote:
>>
>> Have you tried dumping core and using gdb to find out more about the
>> process state?
>
>Yeah, just did. I need the debuginfo for prop
On Mar 20, 10:22 am, a...@pythoncraft.com (Aahz) wrote:
> How many processes do you have running? What kind of guarantee do you
One process. No threads, no forking.
> have that there's only one process if you think there should be only one?
> What's on the other side of the socket? If there's n
[posted and e-mailed, please respond to newsgroup]
In article <2961e0af-d99b-4d5e-a280-f521ce7fa...@e10g2000vbe.googlegroups.com>,
msoulier wrote:
>
>I'm using the Python packaged with CentOS 4.7, which is a patched
>2.3.4. Yes, ancient but I can't do anything about it.
That's not ancient -- ma
Hello,
I'm using the Python packaged with CentOS 4.7, which is a patched
2.3.4. Yes, ancient but I can't do anything about it.
The problem is that my long-running process, which talks to PostgreSQL
via Django models, does a lot of reading and writing to and from the
disk and writes to a Unix doma
