From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1F9ObS-00069S-Dx for garchives@archives.gentoo.org; Wed, 15 Feb 2006 15:30:02 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k1FFSoOC022676; Wed, 15 Feb 2006 15:28:50 GMT Received: from ender.volumehost.net (adsl-69-154-123-202.dsl.fyvlar.swbell.net [69.154.123.202]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k1FFONKX014754 for ; Wed, 15 Feb 2006 15:24:23 GMT Received: from localhost (localhost [127.0.0.1]) by ender.volumehost.net (Postfix) with ESMTP id 04983B710 for ; Wed, 15 Feb 2006 15:24:23 +0000 (UTC) Received: from ender.volumehost.net ([127.0.0.1]) by localhost (ender.volumehost.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 25909-10 for ; Wed, 15 Feb 2006 15:24:20 +0000 (UTC) Received: from ath600 (ip70-178-169-79.ks.ks.cox.net [70.178.169.79]) (using SSLv3 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ender.volumehost.net (Postfix) with ESMTP id B6D43B650 for ; Wed, 15 Feb 2006 15:24:20 +0000 (UTC) From: Zac Slade To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] emerge troubles Date: Wed, 15 Feb 2006 09:24:18 -0600 User-Agent: KMail/1.9.1 References: <7573e9640602141848j2054ebecjb062b6e4c22eb321@mail.gmail.com> In-Reply-To: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200602150924.18823.krakrjak@volumehost.net> X-Virus-Scanned: amavisd-new at volumehost.net X-Archives-Salt: 1177b4ee-d82c-4fe1-a1c5-abb974cfcc24 X-Archives-Hash: 25ce4e7d6fb0f3a17172dc5373bfbb32 On Tuesday 14 February 2006 21:14, Jorge Almeida wrote: > Well, so that was it! I just finished compiling gcc. > I wonder why those limits were set for user root?! > My home computer didn't have such restriction, and I recently made a new > install on the computer that had all this problem, so I'm sure I didn't > do it myself and forgot it... Check /etc/limits to see what the defaults are. I'd also look at any shell scripts that are being sourced during login (/etc/profile ~/.bashrc, etc.). > It's a relief to know it's not hw problem! Memory allocation is one of those things that usually isn't. Normally you'd see physical memory errors as programs randomly crashing (like the kernel, with no PANIC). You also might notice when you start the system up that it is reporting less memory than you have installed. > Thank you, and thanks also to Benno and Zac. Very appreciated. -- Zac Slade -- gentoo-user@gentoo.org mailing list