Wasn't this the problem where asyncore.py is not
catching the operating system's EINTR. I used to
get these all the time, and was able to stop it
using a modified asyncore which loops on an OS
select() call, restarting the call if it catches
EINTR from the OS ... I can send a modified
asyncore.py
"Dirk Datzert" <[EMAIL PROTECTED]> writes:
> Its a Linux 2.2.19. What does IIRC means ?
If I remember correctly. I could fix the problem (or a similar one)
last summer by changing the Linux kernel.
http://mailman.beehive.de/pipermail/zope/2001-June/000590.html
http://mailman.beehive.de/piperma
From: "Dirk Datzert" <[EMAIL PROTECTED]>
> Its a Linux 2.2.19. What does IIRC means ?
IIRC means "If I Recall Correctly", IIRC :-)
And these problems occur also on solaris, so there's nothing linux centric
about them.
/dario
- -
IL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, December 10, 2001 12:28 AM
Subject: Re: [Zope-dev] yes, segv11 and Broken pipes
> "Chris McDonough" <[EMAIL PROTECTED]> writes:
>
> > These failure reports are alarming, but I haven't seen
> > anything li
"Chris McDonough" <[EMAIL PROTECTED]> writes:
> These failure reports are alarming, but I haven't seen
> anything like them, and of course we can't fix what we can't
> find. If anybody can make the problem recur repeatably, we
> can almost certainly fix it.
>
> Sorry,
>
> - C
>
>
> On Sun, 0
These failure reports are alarming, but I haven't seen
anything like them, and of course we can't fix what we can't
find. If anybody can make the problem recur repeatably, we
can almost certainly fix it.
Sorry,
- C
On Sun, 09 Dec 2001 10:03:36 +0100
Dirk Datzert <[EMAIL PROTECTED]> wrote:
>
Hello,
I can report the same failure:
First there is a OSerror signal 11 and from that point on there will be OSerror errno
32 Borken pipe until Zope is restarted.
Our System is:
Zope 2.4.3 (from source 2.4.1 with update 2.4.x_to_2.4.3, python 2.1.1, Apache 1.3.12
is there a solution out ?
R
