[clug] Memory Leak In cAosity

[Sam Couter]

Steve Walsh <steve at nerdvana.org.au> wrote:
> I've got a Dual Xeon 2.8 box with 1Gb ECC running cAosity (RHEL knockoff)
> x86-64 with a rather horrific
> memory leak. I can reboot the box and have about 10% memory usage, then
> after about 8 hours it's at 25%, and within 30 hours of a reboot it's at 90%
> where it stays.

You've paid for this memory, why don't you want it to be used? Is it for
decoration?

Linux uses all the memory it can. It's caching stuff so it doesn't need
to read from the disk next time you access it. It also caches stuff that
hasn't yet been written to the disk so it can order writes for better
performance.

If you have some program that's actually leaking memory or allocating
large amounts of memory, 'top' can show you. But what you've described
sounds like intended behaviour.
-- 
Sam "Eddie" Couter  |  mailto:sam at couter.dropbear.id.au
Debian Developer    |  mailto:eddie at debian.org
                    |  jabber:sam at teknohaus.dyndns.org
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.samba.org/archive/linux/attachments/20050804/a2bb09aa/attachment.bin