On Wed, Nov 07, 2007 at 11:39:55AM -0300, Mario Lobo wrote:
> Hello;
> 
> I'm running a qmailrocks install + DNS server here. Hosting 14 domains and 
> their respective e-mail accounts. Everything seems to be working fine.
> 
> The machine is:
> 
> ------------------------------------------
> FreeBSD 6.2-STABLE #0: Mon Sep 10 14:15:16 BRT 2007
> CPU: Intel(R) Core(TM)2 CPU  6700  @ 2.66GHz (2669.94-MHz K8-class CPU)
>   Origin = "GenuineIntel"  Id = 0x6f6  Stepping = 6
>   Cores per package: 2
> real memory  = 3488481280 (3326 MB)
> avail memory = 3362598912 (3206 MB)
> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
>  cpu0 (BSP): APIC ID:  0
>  cpu1 (AP): APIC ID:  1
> ------------------------------------------
> 
> When I turn the machine on/restart it, it starts off with around 2800 Mb free 
> memory. I know that, in its course of work, a few of those processes do not 
> properly return memory back to the system. The machine was last restarted 
> exactly a week ago (last wednesday). Now 'top' shows me this:
> 
> ------------------------------------------
> last pid: 17204;  load averages:  0.00,  0.04,  0.06   up 5+21:00:50  11:18:58
> 135 processes: 1 running, 132 sleeping, 2 zombie
> CPU states:  0.6% user,  0.0% nice,  0.4% system,  0.2% interrupt, 98.9% idle
> Mem: 379M Active, 1915M Inact, 256M Wired, 119M Cache, 214M Buf, 415M Free
> Swap: 5120M Total, 5120M Free
> ------------------------------------------
> 
> Here are my questions:
> 
> Is this a "normal thing" to happen with memory in just one week?

Yes, it is normal and nothing to worry about.

> Does the  '1915M Inact'  means "zombie memory" (non-returned)?

No.  'Inact[ive]', 'Cache' and 'Free' can all be considered free memory in
slighly different states.
There are differences between them that can be important in some
circumstances, but if you are just trying to determine if you have a memory
leak somewhere they can be lumped together,



> Is there a manual garbage collector i could run?

No.

> What is your advise on what method I could use to precisely track down what 
> program(s) is(are) causing this?

My advice is that you ignore it.  It is nothing to worry about.



-- 
<Insert your favourite quote here.>
Erik Trulsson
[EMAIL PROTECTED]
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to