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. thanks, jlg John Leon Guerrero -- http://www.live365.com