I'd prefer this wait until after 1.3.27 is released.
--
===
Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/
A society that will trade a little liberty for a little order
will
Aye - no hurry with this one.
On Thu, 26 Sep 2002, Jim Jagielski wrote:
I'd prefer this wait until after 1.3.27 is released.
On Wed, 25 Sep 2002, Sander van Zoest wrote:
On Wed, 25 Sep 2002, Justin Erenkrantz wrote:
On Thu, Sep 26, 2002 at 02:11:59AM +0200, Dirk-Willem van Gulik wrote:
-Makes the wait loop no longer endless - but causes it
to bail out (and emit some warnings ahead of time) after
Now this may be a bit linux specific - but I'd like to get something like
this in; if needed with a #ifdef DIAG or on a per platform basis.
It is just something I've found to come in handy at various times - in
particular on Linux and with lots of heavy PHP or mod_perl.
This patch does two
On Thu, Sep 26, 2002 at 02:48:53AM +0200, Dirk-Willem van Gulik wrote:
I could not agree more.
The original patch used 'time' - but that is expensive to calculate. If
you make a histogram of conseq EINTR over a few weeks you find that
sequences longer than 5-10 are very rare on a healthy
On Thu, Sep 26, 2002 at 03:00:56AM +0200, Dirk-Willem van Gulik wrote:
Well the numbers in that patch seem to work on sol/bsd/linux since 1.3.9
under just about any set of circumstances.
So let's think out of the box then - how can we prevent apache from
spinning *forever* in that while
On Wed, 25 Sep 2002, Justin Erenkrantz wrote:
On Thu, Sep 26, 2002 at 02:11:59AM +0200, Dirk-Willem van Gulik wrote:
- Makes the wait loop no longer endless - but causes it
to bail out (and emit some warnings ahead of time) after
a couple of thousand consequituve EINTRs.
Placing
