From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Nik Gervae <nik@linna.com>, zsh-workers@sunsite.auc.dk
Subject: Re: export limit in zsh and other shells?
Date: Thu, 3 Jun 1999 04:13:18 +0000 [thread overview]
Message-ID: <990603041318.ZM2604@candle.brasslantern.com> (raw)
In-Reply-To: <199906030250.TAA19950@news.idiom.com>
In-Reply-To: <slrn7lbuel.jpd.mason@coral.primenet.com.au>
On Jun 2, 7:49pm, Nik Gervae wrote:
} Subject: export limit in zsh and other shells?
}
} 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
On Jun 3, 3:43am, Geoff Wing wrote:
} Subject: Re: export limit in zsh and other shells?
}
} And all the shells spew out the same message. It's an operating system
} limit on argument lists.
}
} % sysctl kern.argmax
} kern.argmax = 262144
} which is described as "The maximum bytes of argument to execve(2)."
The important point to note here is that "argument to execve(2)" includes
both the `argv' and `envp' arrays. Although passed to execve() as two
pointers (char*[]), when the kernel prepares a new process image for
execution it copies the entirety of both arrays into a contiguous chunk
of memory. The `argmax' kernel parameter in Geoff's example sets the
size of that chunk.
In short, you may have to find a different way to control your animations.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
prev parent reply other threads:[~1999-06-03 4:13 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
1999-06-03 4:13 ` Bart Schaefer [this message]
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=990603041318.ZM2604@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=nik@linna.com \
--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).