On Wed, 25 Sep 2002, Justin Erenkrantz wrote: > to let the OS tell us when something has gone afoul rather than > trying to second-guess it when the error only means "You were > interrupted - try again." So, I don't think there is a metric > that can work (without fail) for this case. -- justin 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 loop when something has gone astray ? DW
- [PATCH] Alerting when fnctl is going bad Dirk-Willem van Gulik
- Re: [PATCH] Alerting when fnctl is going ... Justin Erenkrantz
- Re: [PATCH] Alerting when fnctl is go... Dirk-Willem van Gulik
- Re: [PATCH] Alerting when fnctl i... Justin Erenkrantz
- Re: [PATCH] Alerting when fnc... Dirk-Willem van Gulik
- Re: [PATCH] Alerting whe... Justin Erenkrantz
- UDP ? Gregory (Grisha) Trubetskoy
- Re: UDP ? rbb
- Re: [PATCH] Alerting when fnctl is go... Sander van Zoest
- Re: [PATCH] Alerting when fnctl i... Jim Jagielski
- Re: [PATCH] Alerting when fnc... Dirk-Willem van Gulik
- Re: [PATCH] Alerting when fnctl i... Scott Hess