On Mon, Dec 15, 2014 at 7:52 AM, Benjamin Coddington <bcodding@xxxxxxxxxx> wrote: > Dear Pablo, > > Why are you restarting snmpd between flushing cache and reading > memory values? On a running system you can probably expect the > cache to immediately start to fill after a flush anyway. > y > Ben > > On Mon, 15 Dec 2014, Pablo Silva wrote: > >> Dear Readers: >> >> My boss has entrusted me to analyze why the memory buffers are >> not released a Linux server with Centos 6.4.? >> >> As informs me, the current reading is: >> >> >> [root@bck ~]# free -m >> total used free shared buffers cached >> Mem: 15936 15788 147 0 6746 438 >> -/+ buffers/cache: 8604 7332 >> Swap: 2047 0 2047 >> [root@bck ~]# >> [root@bck ~]# >> [root@bck ~]# echo 3 > /proc/sys/vm/drop_caches && service snmpd >> restart && free -m >> Stopping snmpd: [ OK ] >> Starting snmpd: [ OK ] >> total used free shared buffers cached >> Mem: 15936 509 15426 0 93 16 >> -/+ buffers/cache: 400 15536 >> Swap: 2047 0 2047 >> [root@bck ~]# >> >> I can not find the solution to release the memory buffer and cache >> memory so grateful for any hint for finding the solution to this >> "problem". >> >> -Paul >> See the top entry on googling "why does linux cache memory": http://www.linuxatemyram.com/ -- Trond Myklebust Linux NFS client maintainer, PrimaryData trond.myklebust@xxxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
