John E. Leon Guerrero wrote: > if a job hangs (due to database locking for instance), then a mod_perl child > will hang as well (absent some additional watchdog-type program.) if enough > jobs hang to the point that we hit MaxClients, then it is too late to use > /server-status to see what jobs hung. > > does anyone have a quick way to indentify the jobs that are currently > running? i thought of getting a core and using gdb but i was hoping to find > a faster way. it would be nice if we could reserve a couple of children for > administrative emergencies such as this.
You probably want: Apache::Watchdog::RunAway __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
