On Tuesday 14 February 2006 19:25, Jorge Almeida wrote: > $ cat /proc/sys/vm/swappiness > 60 > $ cat /proc/sys/vm/overcommit_memory > 0 > $ cat /proc/sys/vm/overcommit_ratio > 50 That was a long shot, but just wanted to make sure the system was allowing overcommit.
> $ free > total used free shared buffers > cached > Mem: 1035204 968140 67064 0 270248 > 538412 > -/+ buffers/cache: 159480 875724 > Swap: 996020 300 995720 This seems within spec. You have plenty of memory free. > Of course, this is the output of free _after_ the previous failed emerge > attempts. It seems RAM really was caught and not released... I can try > rebooting, but there is the possibility that the box won't boot, and I'm > away... Is there some way to find what's eating RAM? If you don't have physical access to the system, don't reboot it. It's not just a good rule of thumb, it's one you should live by (whenever possible). > > What process is using the most memory right now? (Check top sorted by > > memory). > > $ top > top - 01:21:23 up 22 days, 17:29, 2 users, load average: 0.00, 0.00, > 0.00 Tasks: 120 total, 2 running, 118 sleeping, 0 stopped, 0 zombie > Cpu(s): 0.0% us, 0.0% sy, 0.0% ni, 99.7% id, 0.0% wa, 0.3% hi, 0.0% > si Mem: 1035204k total, 968760k used, 66444k free, 270684k buffers > Swap: 996020k total, 300k used, 995720k free, 538452k cached > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 8291 root 15 0 159m 29m 3056 S 0.0 3.0 5:05.74 X > 24756 jorge 15 0 30592 25m 2576 S 0.0 2.5 0:06.52 pine > 28731 jorge 16 0 20016 14m 14m S 0.0 1.4 0:19.34 imap > 26923 root 15 0 21236 12m 9704 S 0.0 1.2 0:00.39 kdm_greet > 24757 jorge 16 0 8436 6292 5984 S 0.0 0.6 0:01.85 imap > 21961 jorge 16 0 8044 3992 2684 S 0.0 0.4 0:00.15 vim > 8259 root 16 0 5756 2852 1356 S 0.0 0.3 0:50.69 cupsd > 24734 root 16 0 5944 1764 1440 S 0.0 0.2 0:00.01 sshd > 24767 root 16 0 5948 1764 1440 S 0.0 0.2 0:00.01 sshd > 3588 root 15 0 2644 1560 1172 S 0.0 0.2 0:00.11 bash > 24746 jorge 15 0 2924 1472 1164 S 0.0 0.1 0:00.02 bash > 6396 privoxy 15 0 36028 1464 784 S 0.0 0.1 0:07.90 privoxy > 24785 jorge 15 0 2796 1456 1156 S 0.0 0.1 0:00.01 bash > 24799 root 16 0 2664 1456 1156 S 0.0 0.1 0:00.00 bash Well nothing really stands out here.... There are multiple imap processes open, but really you have plenty of memory. Just an absolute blind stab in the dark..... what does df -h give you? Anything interesting in dmesg? And just to make sure we have PLENTY of information here, can we get the end of emerge.log (some context prior to the error message). -- Zac Slade -- gentoo-user@gentoo.org mailing list
