From: "James Stevenson" <mail-lists@stev.org>
To: "Samuel Flory" <sflory@rackable.com>, "Eric Weigle" <ehw@lanl.gov>
Cc: "Linux kernel mailing list \(lkml\)" <linux-kernel@vger.kernel.org>
Subject: Re: Safety of -j N when building kernels?
Date: Wed, 22 May 2002 21:03:08 +0100 [thread overview]
Message-ID: <002501c201cb$b25a0cb0$0501a8c0@Stev.org> (raw)
In-Reply-To: <20020522165320.GC18059@lanl.gov> <3CEBE38A.8020808@rackable.com>
> The only major issue I've seen is the build may fail if you run out
> of file handles, or other resources. The build will fail with an
> "unable to fork" error. When I was at VA Linux I often compiled kernel
> for use with a make -j 16, or -j 8. I seem to remember having to play
> with ulimit, and /proc/?/file-max to get enough file handles.
>
>
> PS- You should also consider logging the output of your compile to a
> file. As your other jobs will continue for sometime before the make
> fails. Often preventing you from easily finding the actual compile error.
of course you should only really need to log the stderr or redirect stderr
to somewhere you can see it.
next prev parent reply other threads:[~2002-05-22 22:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 16:53 Safety of -j N when building kernels? Eric Weigle
2002-05-22 17:24 ` William Park
2002-05-22 17:31 ` Fernando [Quatro]
2002-05-22 18:29 ` Samuel Flory
2002-05-22 20:03 ` James Stevenson [this message]
2002-05-22 23:32 ` Keith Owens
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='002501c201cb$b25a0cb0$0501a8c0@Stev.org' \
--to=mail-lists@stev.org \
--cc=ehw@lanl.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=sflory@rackable.com \
/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