Re: Watchdog code for Apache

2005-06-06 Thread Nick Kew
Jeff Trawick wrote: On 6/4/05, Nick Kew [EMAIL PROTECTED] wrote: It also seems better for the watchdog code to run in Apache's master process than to fork off a separate process. ... My current thinking is to use ap_wait_or_timeout and: create a hook that runs there Agreed. I've

Watchdog code for Apache

2005-06-04 Thread Nick Kew
A little while back, I hacked up a quickdirty experimental watchdog module. It forks a watchdog process in the pre_mpm hook, which then watches the scoreboard and kills any process in which some request has taken more than some predefined time. Currently this is limited to killing processes,

Re: Watchdog code for Apache

2005-06-04 Thread Jeff Trawick
On 6/4/05, Nick Kew [EMAIL PROTECTED] wrote: It also seems better for the watchdog code to run in Apache's master process than to fork off a separate process. ... My current thinking is to use ap_wait_or_timeout and: create a hook that runs there * go through the scoreboard looking for

Re: Watchdog code for Apache

2005-06-04 Thread Graham Leggett
Nick Kew wrote: A little while back, I hacked up a quickdirty experimental watchdog module. It forks a watchdog process in the pre_mpm hook, which then watches the scoreboard and kills any process in which some request has taken more than some predefined time. Depends on what taken more

Re: Watchdog code for Apache

2005-06-04 Thread Stas Bekman
Nick Kew wrote: A little while back, I hacked up a quickdirty experimental watchdog module. It forks a watchdog process in the pre_mpm hook, which then watches the scoreboard and kills any process in which some request has taken more than some predefined time. Also check: