On Tuesday 14 February 2006 17:43, Benno Schulenberg wrote:
> Jorge Almeida wrote:
> >     parser error : out of memory error
> >     /bin/sh: line 1:  3831 Segmentation fault
>
> Doesn't look good.  :(
No it doesn't, but there has to be a reason why he's out of memory...  What is 
the output of free, before emerge?  How about after it fails?  Can you give 
the output of the following commands:
cat /proc/sys/vm/swappiness
cat /proc/sys/vm/overcommit_memory
cat /proc/sys/vm/overcommit_ratio

Also try using "vmstat 5" in one window and attempting the emerge in another 
window.

What process is using the most memory right now?  (Check top sorted by 
memory).
> Is this box always on?  Have you tried rebooting?  Maybe loads of
> memory have leaked away.
WHOA!  Stop right there.  Perhaps we should help him diagnose his problem 
before using a shotgun.

> If the RAM has gone bad, to replace it you will have to touch it
> anyway.  So, no harm in trying to wriggle it a bit first.  Touch
> and hold the case before touching the RAM strips.
There is nothing in the information he has presented thus far to show that 
there are memory errors of any type.  He very well may be just running out of 
memory.  It happens.

Send back the extra information and let's get to the bottom of the issue.
-- 
Zac Slade
-- 
gentoo-user@gentoo.org mailing list

Reply via email to