From: "H . J . Lu" <hjl@lucon.org>
To: Zack Weinberg <zack@wolery.cumb.org>
Cc: gcc@gcc.gnu.org
Subject: Re: Problems with the cpp change after 2000-06-18
Date: Mon, 03 Jul 2000 10:41:00 -0000 [thread overview]
Message-ID: <20000703104138.A1321@lucon.org> (raw)
In-Reply-To: <20000703102201.F274@wolery.cumb.org>
On Mon, Jul 03, 2000 at 10:22:01AM -0700, Zack Weinberg wrote:
> On Mon, Jul 03, 2000 at 10:09:19AM -0700, H . J . Lu wrote:
> > Hi, Zack,
> >
> > I am not sure if I like the cpp change after 2000-06-18 when cpp keeps
> > so many files open. The problem is on a 4way SMP machie, I can do
> >
> > # make MAKE="make -j 8"
> >
> > in the Linux kernel build. My system file descriptor limit is reached
> > in minutes. Then other processes on my machine start dying. I know you
> > put in a fix so that cpp won't die. But it doesn't help other processes.
> > I think you should put a limit on the number of opened files in cpp.
>
> Try using ulimit -n.
>
I have to build kernel as root. I am not sure "ulimit -n" will help.
H.J.
next prev parent reply other threads:[~2000-07-03 10:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-03 10:09 H . J . Lu
2000-07-03 10:22 ` Zack Weinberg
2000-07-03 10:40 ` Zack Weinberg
2000-07-03 10:41 ` H . J . Lu [this message]
2000-07-03 10:54 ` Zack Weinberg
2000-07-03 15:30 ` H . J . Lu
2000-07-03 16:24 ` Zack Weinberg
2000-07-03 16:35 ` H . J . Lu
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=20000703104138.A1321@lucon.org \
--to=hjl@lucon.org \
--cc=gcc@gcc.gnu.org \
--cc=zack@wolery.cumb.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).