From: Kiril Vidimce <vkire@pixar.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: max arguments for exec
Date: Wed, 26 Sep 2001 20:23:24 -0700 [thread overview]
Message-ID: <Pine.SGI.4.21.0109262017410.36450-100000@eclipse> (raw)
In-Reply-To: <8237.1001557672@kao2.melbourne.sgi.com>
On Thu, 27 Sep 2001, Keith Owens wrote:
> On Wed, 26 Sep 2001 14:25:05 -0700 (PDT),
> Kiril Vidimce <vkire@pixar.com> wrote:
> >Is there any way to reconfigure the kernel at runtime to change the
> >limit for arguments passed during an exec? I guess I am looking for
> >something similar to systune ncargs under IRIX. I found this thread
> >in the archives:
> >
> >http://uwsg.iu.edu/hypermail/linux/kernel/0003.0/0160.html
> >
> >The only suggestion was to patch and recompile the kernel. I looked
> >into sysctl and I couldn't find an appropriate argument to tweak.
>
> It is controlled by MAX_ARG_PAGES in include/linux/binfmts.h. Change
> and recompile the kernel, it is not dynamically tunable in Linux.
Yeah, I know, but we would like to avoid building a custom kernel.
If we do end up going this route, I wonder if there is a limit for
MAX_ARG_PAGES. Any idea? I think 128 pages (512K) would be sufficient
for our needs.
KV
--
___________________________________________________________________
Studio Tools vkire@pixar.com
Pixar Animation Studios http://www.pixar.com/
next prev parent reply other threads:[~2001-09-27 3:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 21:25 Kiril Vidimce
2001-09-27 2:27 ` Keith Owens
2001-09-27 3:23 ` Kiril Vidimce [this message]
2001-09-27 8:18 ` Ingo Molnar
2001-09-27 8:13 ` [patch] exec-argsize-2.4.10-A3 Ingo Molnar
2001-09-27 15:34 ` Linus Torvalds
2001-09-27 15:48 max arguments for exec Carl Spalletta
2001-09-27 16:53 ` Kiril Vidimce
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=Pine.SGI.4.21.0109262017410.36450-100000@eclipse \
--to=vkire@pixar.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®