Messages in this thread | | | Date | Sat, 21 Sep 1996 00:35:26 -0400 (EDT) | From | Jon Lewis <> | Subject | Re: Processes hanging on 2.0.20; not just on Alphas anymore :( |
| |
On Fri, 20 Sep 1996, Joey Hess wrote:
> I had this same problem with apache 1.1.1-2 (a slightly modified debian > version), and 2.0.20. I killed its parent process and kept sending it > kill signals, and after about 5 minutes it either listened to one of them, > or died on its own.
I've seen the rogue Apache 1.1.1 child process live for hours even with my process reaper script sending it a SIGKILL every 5 minutes or myself sending same as fast as I can repeat with command history. This was with 2.0.16 and 2.0.18. Perhaps I'll give 2.0.21 a try after a bit of testing.
BTW...my Apache 1.1.1 is modified to have the kiddies do a setrlimit to limit themselves to 6 minutes CPU time...and even that didn't stop them from living and burning large amounts of CPU.
------------------------------------------------------------------ Jon Lewis <jlewis@fdt.net> | Unsolicited commercial e-mail will Network Administrator | be proof-read for $199/hr. ________Finger jlewis@inorganic5.fdt.net for PGP public key_______
| |