Yes:
[EMAIL PROTECTED]:~ 10:02am 52 # ps -ef | grep 10312
mailman 10312 22726 0 09:13:19 ? 0:05 /bin/python
/opt/mailman-2.1.9/bin/qrunner --runner=VirginRunner:0:1 -s
This is the error for no such process:
[EMAIL PROTECTED]:~ 10:04am 53 # ./memleak.d 666
dtrace: failed to compile script ./memleak.d: line 3: failed to grab process
666
[EMAIL PROTECTED]:~ 10:04am 54 # ps -ef | grep 666
root 20386 19893 0 10:04:49 pts/1 0:00 grep 666
[EMAIL PROTECTED]:~ 10:04am 55 #
I'm hoping there is a "fresher" script than this 3yr old one I found via the
top google hit for: " dtrace script for memory leak"
The 2nd and third hits are now this thread - gah!
I know memory leaks are a non-trivial problem - but the rate of this one is
so egregious as to require twice daily restarts of mailman - I like the
logic behind checking the alloc/free calls and matching them up...
Any tips appreciated -
Thanks,
Fletcher
On 7/1/08 9:41 AM, "Michael Schuster" <[EMAIL PROTECTED]> wrote:
> Fletcher Cocquyt wrote:
>> Hola, I am trying to isolate the memory leak I suspect in a mailman
>> installation I found:
>> http://blogs.sun.com/sanjeevb/date/200506
>>
>> It gives an error:
>>
>> [EMAIL PROTECTED]:~ 9:21am 65 # ./memleak.d 10312
>> dtrace: failed to compile script ./memleak.d: line 3: probe description
>> pid10312:libc.so.1:malloc:entry does not match any probes
>
> this begs the question:
> is there a process with pid 10312?
>
> Michael
--
Fletcher Cocquyt
Senior Systems Administrator
Information Resources and Technology (IRT)
Stanford University School of Medicine
Email: [EMAIL PROTECTED]
Phone: (650) 724-7485
_______________________________________________
dtrace-discuss mailing list
[email protected]
