tracing memory problem

2001-09-07 Thread Jon Molin
Hi list, I have a memory leak in a script or module, the problem is that i've resently added many scripts and modules and can't easily isolate the problem. Is there a way besides strace to see what the httpd process is up to? 9869 httpd 0 0 21188 19M 2424 S 0 12.2 3.8 0:13

Re: tracing memory problem

2001-09-07 Thread Stas Bekman
On Fri, 7 Sep 2001, Jon Molin wrote: Hi list, I have a memory leak in a script or module, the problem is that i've resently added many scripts and modules and can't easily isolate the problem. Is there a way besides strace to see what the httpd process is up to? 9869 httpd 0 0

Re: tracing memory problem

2001-09-07 Thread Jon Molin
Stas Bekman wrote: On Fri, 7 Sep 2001, Jon Molin wrote: Hi list, I have a memory leak in a script or module, the problem is that i've resently added many scripts and modules and can't easily isolate the problem. Is there a way besides strace to see what the httpd process is up

Re: tracing memory problem

2001-09-07 Thread Stas Bekman
On Fri, 7 Sep 2001, Jon Molin wrote: Stas Bekman wrote: On Fri, 7 Sep 2001, Jon Molin wrote: Hi list, I have a memory leak in a script or module, the problem is that i've resently added many scripts and modules and can't easily isolate the problem. Is there a way besides

Re: tracing memory problem

2001-09-07 Thread Perrin Harkins
ok, i'll look into that. I've been using RLimitMEM and RLimitCPU One thing to be aware of is that using rlimit will kill your process harshly when it goes over the limit. It's better to use Apache::SizeLimit for basic size control, and use rlimit as a backup safety measure to catch runaway