run 'date>>/tmp/top.log;top -b -n 1>>/tmp/top.log' every 5 minutes from
cron and you will have a log you can review after thsi happens again.
Then you can at least determine whether or not it's the kernel leaking
memory, or some other program.
I'm not sure how to get top to sort results by memory usage in batch mode,
but it can be easily done afterwards
hth
charles
On Tue, 17 Oct 2000, Kiran Kumar M wrote:
> > Try running top to see just how much memory is being used. Press "M"
> > (shift-m) which will sort by memory, and look at (typically) the first
> > process, which should be the one consuming the most memory.
>
> It is very clear that there will be memory leak, if I unable to execute
> any of the commands, there is no chance to execute top also.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
