At 18.56 +0200 9/26/2000, Ime Smits wrote:
>Hi,
>
>I wonder if it's possible to somehow alter Apache's internal counter matched
>against MaxRequestPerChild or schedule the launching of a new child from
>withing mod_perl.
>
>The reason I want to do this, is that in the administrator section of my
>website, quite some stuff gets cached from the PostgreSQL backend on a per
>process basis and there is really no use to keep all those caches after the
>administrator hit the logout button.
>
>Plus, I want to be able to terminate a process if some kind cache
>inconsistency is detected. I know it's better to track the origin of that
>inconsistency and fix it there, but I'm using some modules which I did not
>create myself and I'm not planning to dig into 5000+ lines of code I did not
>wrote. What I really would like to do is to just finish the current page,
>dropping a line like "things are getting fishy here", wipe the
>administrator's session cookie and let the child die.
>
>Ime
Can you run the administrative section of your site in a separate server process?
That way, you can tune your MaxClients and MaxRequestsPerChild levels very low for
that server, while preventing your front-end server from allocating excessive chunks
of RAM (and leaving the afformentioned settings optimized.)
Enjoy,
--
David Pisoni -- <[EMAIL PROTECTED]>
Cnation -- <http://www.cnation.com/>
310/228-6900 -- 310/228-6905 (fax)
"The opposite of a correct statement is a false statement. But the opposite of
a profound truth may well be another profound truth." -Niels Bohr, physicist
(1885-1962)
