Re: memory leakage in system?

2001-02-21 Thread Nate Amsden
Jeff Davis wrote: > Thanks to both of the people who have responded so far. I am glad to > know it is working fine. I never noticed that much use of ram on any of > my other systems ( I probably never checked ), so it had me worried :) it gets worse then that. i freak out quite often when i see m

Re: memory leakage in system?

2001-02-21 Thread Jeff Davis
Alexis Roda wrote: Jeff Davis wrote: I have in my server 256MB RAM, of which about 220MB is used. Here is a command I ran: # cat /proc/meminfo total:used:free: shared: buffers: cached: Mem: 261832704 232955904 28876800 76492800 162164736 41222144 Swap: 320774144 192512 320

memory leakage in system?

2001-02-21 Thread Jeff Davis
I have in my server 256MB RAM, of which about 220MB is used. Here is a command I ran: # cat /proc/meminfo total:used:free: shared: buffers: cached: Mem: 261832704 232955904 28876800 76492800 162164736 41222144 Swap: 320774144 192512 320581632 MemTotal:255696 kB MemFree:

Re: Memory leakage

2001-01-04 Thread kmself
on Wed, Jan 03, 2001 at 09:36:38PM -0500, D-Man ([EMAIL PROTECTED]) wrote: > On Wed, Jan 03, 2001 at 06:05:13PM -0800, kmself@ix.netcom.com wrote: > > > > > $ fuser -v bigfile # show process(es) using bigfile > > $ fuser -vk bigfile # kill process(es) using bigfi

Re: Memory leakage

2001-01-03 Thread D-Man
On Wed, Jan 03, 2001 at 06:05:13PM -0800, kmself@ix.netcom.com wrote: > > $ fuser -v bigfile# show process(es) using bigfile > $ fuser -vk bigfile # kill process(es) using bigfile > $ fuser -v bigfile# verify the kill worked > $ cat /

Re: Memory leakage

2001-01-03 Thread kmself
on Wed, Jan 03, 2001 at 09:06:16PM -0500, Antonio Rodriguez ([EMAIL PROTECTED]) wrote: > > > kmself@ix.netcom.com wrote: > > > > > > Try the following on each of your mounted partitions, starting at the > > mount point: > > > > $ du -sx * | sort -nr | cat -n | less > > > > ...which will

Re: Memory leakage

2001-01-03 Thread Antonio Rodriguez
kmself@ix.netcom.com wrote: > > Try the following on each of your mounted partitions, starting at the > mount point: > > $ du -sx * | sort -nr | cat -n | less > > ...which will list out your largest directories, with usage sumarized, > in size order. Track down where the storage seems t

Re: Memory leakage

2001-01-03 Thread kmself
on Wed, Jan 03, 2001 at 04:44:45PM -0500, Antonio Rodriguez ([EMAIL PROTECTED]) wrote: > > > kmself@ix.netcom.com wrote: > > > > on Wed, Jan 03, 2001 at 06:34:09AM -0500, Antonio Rodriguez ([EMAIL > > PROTECTED]) wrote: > > > In a case of permanent memory loss (hard disk), w/o apparent reason,

Re: Memory leakage

2001-01-03 Thread Antonio Rodriguez
kmself@ix.netcom.com wrote: > > on Wed, Jan 03, 2001 at 06:34:09AM -0500, Antonio Rodriguez ([EMAIL > PROTECTED]) wrote: > > In a case of permanent memory loss (hard disk), w/o apparent reason, > > "Memory loss" and "hard disk" don't make sense. Memory in the sense of storage space, in the ha

Re: Memory leakage

2001-01-03 Thread kmself
on Wed, Jan 03, 2001 at 06:34:09AM -0500, Antonio Rodriguez ([EMAIL PROTECTED]) wrote: > In a case of permanent memory loss (hard disk), w/o apparent reason, "Memory loss" and "hard disk" don't make sense. Are you talking about memory (RAM) issues, or have you lost data or partitions on you hard

Memory leakage

2001-01-03 Thread Antonio Rodriguez
In a case of permanent memory loss (hard disk), w/o apparent reason, i.e., of about 1 gb, where to look for reasons and fixes? The only running program besides the kernel, and x11 was rsnyc.