Andreas Schiffler wrote:
I have a problem that I can't explain and don't know exactly how to
debug: the httpd process keeps gobbling up memory over time.
In reply to my own question, I found the cuplrit after some poking
around in frequent restarts of the webserver using:
apachectl
On Sat, 7 Oct 2000, Andreas Schiffler wrote:
Andreas Schiffler wrote:
I have a problem that I can't explain and don't know exactly how to
debug: the httpd process keeps gobbling up memory over time.
In reply to my own question, I found the cuplrit after some poking
around in
I use (/etc/rc.d/init.d/http stop; sleep 2; /etc/rc.d/init.d/http start)
Yeah, it causes a delay, but makes sure the dev box is in a clean state
before I mess it up again with whatever change I just made grin
--M.
On Sat, 07 Oct 2000 12:33:10 -0700, Perrin Harkins wrote:
Andreas Schiffler
Matt Sergeant wrote:
Do you have PerlFreshRestart On ?
If so, don't. Install Apache::Reload and try that instead.
Yeah, its ON.
It seemed like a good thing to do, as per:
http://perl.apache.org/guide/config.html#PerlFreshRestart
and doesn't cause segfaults as per:
Dear mod_perl users,
I have a problem that Ican't explain and don't know exactly how
to debug:the httpd process keeps gobbling up memory over time.
This is what we are running:
Server Version: Apache-AdvancedExtranetServer/1.3.12
(NetRevolution/Linux-Mandrake) mod_perl/1.22 mod_ssl/2.6.4
On Fri, 6 Oct 2000, Andreas Schiffler wrote:
Any ideas where this memory consumption might come from? or how to find
the culprit through some mod_perl code?
Go buy some coffee, get a copy of your local pizza shop's menu next to
your desk, and bring in a sleeping bag. That should help you get
At 09:06 AM 10/06/00 -0400, Andreas Schiffler wrote:
Along with what Matt recommended (although I would have suggested beer,
too), something I did yesterday to track down a leak was to go into every
module I had modified lately and added warn's in both the new() and DESTROY
methods that wrote a
On Fri, 6 Oct 2000, Bill Moseley wrote:
At 09:06 AM 10/06/00 -0400, Andreas Schiffler wrote:
Along with what Matt recommended (although I would have suggested beer,
too), something I did yesterday to track down a leak was to go into every
module I had modified lately and added warn's in
