Alternatively, you can execute top and then hit O (capital O, not zero) then pick size as the primary sort key.
--- mike t. ----- Original Message ---- From: jan gestre <[EMAIL PROTECTED]> To: Philippine Linux Users' Group (PLUG) Technical Discussion List <[email protected]> Sent: Tuesday, May 15, 2007 7:32:06 AM Subject: Re: [plug] memory leak On 5/11/07, fooler <[EMAIL PROTECTED]> wrote: ----- Original Message ----- From: jan gestre To: Philippine Linux Users' Group (PLUG) Technical Discussion List Sent: Friday, May 11, 2007 6:11 PM Subject: Re: [plug] memory leak >maximize 16GB? your kidding right? hehe. right now the memory consumption >is 9GB up from 4GB yesterday, we decided to reboot the server coz we could >not determine the culprit. imagine consuming 9GB with no activity, no users >are >using the system. top nor ps could not indicate the application that >consuming >this huge amount of RAM. could you show the output of "top -osize"? fooler. i got this error when i ran top with -osize as argument: # top -osize top: unknown argument 'o' usage: top -hv | -bcisS -d delay -n iterations [-u user | -U user] -p pid [,pid ...] _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
_________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
