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
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:
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, 09 Dec 2001
: Re: [Zope-dev] yes, segv11 and Broken pipes
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
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
-
