On Tue, 2006-08-29 at 08:27 +0300, Janno Sannik wrote: > Running it on production end. Everything works as expected, but > processors tend to die off and it ends with apache not serving any > requests. restart of apache will fix that.
Processes should die out after a certain (configured) amount of inactivity, but if more requests come in, new processes are supposed to be spawned. It shouldn't ever "run out", is that what appears to be happening? > I would also like to report some weird thing about this. 3 days ago > peruser "hanged" just like it sometimes does. Did a restart and 2 hours > later same thing happened. Some really buggy client? It seems that when apache+peruser stops responding, it's usually because a client is connected to the multiplexer but not issuing a request. Configuring several multiplexers, via multiple Multiplexer configuration directives. I configured my setup to have three of them, and since then apache almost never stops responding like that. It should also make apache a little more responsive, but I haven't done any benchmarks. -- Sean Gabriel Heacock Telana Internet Services http://www.telana.com/ _______________________________________________ Peruser mailing list [email protected] http://www.telana.com/mailman/listinfo/peruser
