home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!uwm.edu!ogicse!das-news.harvard.edu!endor!adam
- From: adam@endor.uucp (Adam Shostack)
- Newsgroups: comp.unix.shell
- Subject: Re: too many values in environment
- Message-ID: <1992Dec23.211503.8335@das.harvard.edu>
- Date: 23 Dec 92 21:15:03 GMT
- Article-I.D.: das.1992Dec23.211503.8335
- References: <BzoDt8.K3A@nit.pactel.com>
- Sender: usenet@das.harvard.edu (Network News)
- Organization: Aiken Computation Lab, Harvard University
- Lines: 21
-
- In article <BzoDt8.K3A@nit.pactel.com> eric@nit.pactel.com (Eric Pederson) writes:
- >I am running SunOS 4.1.x and C-shell. According to TFM, the maximum
- >amount of space that argv[] and envp[] may take up is returned
- >by sysconf(2). On my machine the value is 1 megabyte. However, my
- >shell doesn't want to accept more than 100 environment variables.
- >Since I am running some applications that require a zillion variables
- >to be set before I run them, this limitation is a pain.
-
- I know you found that printenv fixes this, but I wanted to add that
- you can avoid setting all those variables. Put ~/bin at the start
- of your path and fill it will short shell scripts that set the
- environment variables you need and then call the main program. Its
- slightly slower than setting them all at startup, but I find it
- convineint not to set 600 zillion environment variables in my .login.
-
- Adam
-
- Adam Shostack adam@das.harvard.edu
-
- What a terrible thing to have lost one's .sig. Or not to have a .sig
- at all. How true that is.
-