From: Zac Slade <krakrjak@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge troubles
Date: Wed, 15 Feb 2006 09:24:18 -0600 [thread overview]
Message-ID: <200602150924.18823.krakrjak@volumehost.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0602150307530.24756@jmaa.math.ist.utl.pt>
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
next prev parent reply other threads:[~2006-02-15 15:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 10:38 [gentoo-user] emerge troubles Jorge Almeida
2006-02-14 14:50 ` Benno Schulenberg
2006-02-14 18:12 ` Jorge Almeida
2006-02-14 20:43 ` Benno Schulenberg
2006-02-14 21:10 ` Jorge Almeida
2006-02-14 23:43 ` Benno Schulenberg
2006-02-14 23:57 ` Zac Slade
2006-02-15 1:25 ` Jorge Almeida
2006-02-15 1:45 ` Zac Slade
2006-02-15 1:56 ` Richard Fish
2006-02-15 2:14 ` Jorge Almeida
2006-02-15 2:20 ` Richard Fish
2006-02-15 2:21 ` Richard Fish
2006-02-15 2:25 ` Jorge Almeida
2006-02-15 2:48 ` Richard Fish
2006-02-15 3:14 ` Jorge Almeida
2006-02-15 15:24 ` Zac Slade [this message]
2006-02-15 15:37 ` Jorge Almeida
2006-02-15 2:24 ` Jorge Almeida
2006-02-15 2:10 ` Jorge Almeida
2006-02-15 1:51 ` Richard Fish
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200602150924.18823.krakrjak@volumehost.net \
--to=krakrjak@volumehost.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox