A VERY simple way to do it would be to use a shell script that basically does this while true do ps aux | grep circle >> logfile done -Justin Chapweske "Being rich is usually better than being stupid." chapwesk@plains.nodak.edu chapwesk@blackbody.cs.ndsu.nodak.edu chapwesk@cx03.sod.cc.ndsu.nodak.edu orasis@205.198.0.31-35 orasis@bog.nodak.edu orasis@ziggy.rrnet.com (rrnet.com 4800) Justin Chapweske@Fargo.nd.us.earth.milkyway http://blackbody.cs.ndsu.nodak.edu/~chapwesk/ On Fri, 8 Mar 1996, Romulus.. Imp of Phoenix Mud wrote: > On Fri, 8 Mar 1996, Naved A Surve wrote: > > > > open another window and type 'ps' > > I was thinking about being able to log the muds memory usage > versus commands executed/etc to find a memory leak that > we have in the muds code. > > I can't watch the thing 24 hours a day looking for when a leak > occurs so I thought if I can find a system call that determines > the muds memory usage then i can log it...and with other logged > commands/etc I can get a hint where to begin looking for the leak. > > Any ideas are welcome... > -- > |\ /| > | \ / | > | \ / | > | \/ | > | | > | | alice@epix.net > Enough Said... > >
This archive was generated by hypermail 2b30 : 12/07/00 PST