zsh-workers
 help / color / mirror / code / Atom feed
From: mason@primenet.com.au (Geoff Wing)
To: zsh-workers@sunsite.auc.dk
Subject: Re: export limit in zsh and other shells?
Date: 3 Jun 1999 03:43:17 GMT	[thread overview]
Message-ID: <slrn7lbuel.jpd.mason@coral.primenet.com.au> (raw)
In-Reply-To: <199906030250.TAA19950@news.idiom.com>

Nik Gervae <nik@linna.com> typed:
:Here at PDI we use a TON of environment variables to control many aspects of
:our animation jobs. Just today a user came to me complaining that when he
:loaded *all* of these variables into his zsh session he got output like
:this:
:  % ls
:  zsh: arg list too long: ls
:I did a little research and have discovered that just about every shell we
:have here--sh, bash, csh, tcsh, and zsh--exhibit this behavior when presented
:with a couple hundred exported/environment variables. Many of these variables
:are strings, by the way, so I suspect this might cause some kind of memory
:buffer overrrun. Don't quote me on that, though.

And all the shells spew out the same message.  It's an operating system
limit on argument lists.  Some systems may let you alter this while up
(though I don't know of any), some need a kernel recompile (I've a vague
memory of doing this on my system once though I would have to rework out
how), some don't let you alter it at all.

My NetBSD system has a read-only value (queried with 4.4BSD-based ``sysctl''):
	% sysctl kern.argmax
	kern.argmax = 262144
which is described as "The maximum bytes of argument to execve(2)."

Regards,
-- 
Geoff Wing   <gcw@pobox.com>            Mobile : (Australia) 0413 431 874
Work URL: http://www.primenet.com.au/   Ego URL: http://pobox.com/~gcw/


  reply	other threads:[~1999-06-03  3:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-03  2:49 Nik Gervae
1999-06-03  3:43 ` Geoff Wing [this message]
1999-06-03  4:13   ` Bart Schaefer

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=slrn7lbuel.jpd.mason@coral.primenet.com.au \
    --to=mason@primenet.com.au \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).