[no subject]

It is certainly possible to _add_ a module or _remove_ a module, but
change out the kernel with out a reboot (unless 2-kernel-monte is
available, I have not been able to find this :(  ). So the actual data
stream for top is not tamper-able easily. Thus a known good
statically-linked top would give access to the running system and show
the _real_ processes that are running.

If top shows no malicious files, it's time to take some snapshots over
time to plot which app is failing.

#!/bin/sh
echo date >> /tmp/top.txt
top -b -n 1 -c >> /tmp/top.txt
echo "###############" >>/tmp/top.txt
echo >>/tmp/top.txt
echo >>/tmp/top.txt

Run as a cron every minute for an hour.

If you want, you can now mash/mangle the data into a nice plot using
some perl and gnplot (or a spreadsheet).


On Mon, 2004-04-19 at 11:56, Geoffrey wrote:
> Dow Hurst wrote:
> > How can we find the process that is soaking the memory?  How do you 
> > manipulate /proc to find out the originating process that owns the 
> > memory being used?  I know IRIX had tools to look at memory and see 
> > which processes owned what part of memory.  Does Linux?
> > 
> > Seems if you knew what was leaking you would have a major part of the 
> > battle won.
> 
> I believe we mentioned top, but he noted that doesn't give him anything. 
>   That's what concerns me.  If it doesn't show, is it being hidden for a 
> reason???
-- 
James P. Kinney III          \Changing the mobile computing world/
CEO & Director of Engineering \          one Linux user         /
Local Net Solutions,LLC        \           at a time.          /
770-493-8244                    \.___________________________./
<a  rel="nofollow" href="http://www.localnetsolutions.com";>http://www.localnetsolutions.com</a>

GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics)
&lt;jkinney at localnetsolutions.com&gt;
Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part



</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00782" href="msg00782.html">[ale] diagnosis</a></strong>
<ul><li><em>From:</em> dcorbin at machturtle.com (David Corbin)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00645" href="msg00645.html">[ale] diagnosis</a></strong>
<ul><li><em>From:</em> dcorbin at machturtle.com (David Corbin)</li></ul></li>
<li><strong><a name="00738" href="msg00738.html">[ale] diagnosis</a></strong>
<ul><li><em>From:</em> dhurst at kennesaw.edu (Dow Hurst)</li></ul></li>
<li><strong><a name="00749" href="msg00749.html">[ale] diagnosis</a></strong>
<ul><li><em>From:</em> esoteric at 3times25.net (Geoffrey)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00768.html">[ale] [OT] earthlink - results</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00770.html">[ale] (no subject) SPAM talk...</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00761.html">[ale] diagnosis</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00782.html">[ale] diagnosis</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00769"><strong>Date</strong></a></li>
<li><a href="threads.html#00769"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>