Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mandrill!gatech!mcnc!ece-csc!ncrcae!sauron!wescott
From: wescott@sauron.Columbia.NCR.COM (Mike Wescott)
Newsgroups: comp.unix.questions
Subject: Re: Here's /bin/env. (was: environment size question).
Keywords: bug-fix /bin/env 100-variable-limit
Message-ID: <1129@sauron.Columbia.NCR.COM>
Date: 11 Jul 88 20:13:15 GMT
References: <4717@killer.UUCP> <1124@sauron.Columbia.NCR.COM> <249@oha.UUCP>
Reply-To: wescott@sauron.Columbia.NCR.COM (Mike Wescott)
Organization: Entry Level Systems Development, NCR Corp., Columbia, SC
Lines: 14

In article <249@oha.UUCP> tony@oha.UUCP (Tony Olekshy) writes:
> [ Source for /bin/env ]
> #include 
> main(c,a,e) char *a[],*e[]; { while (*e!=0) { puts(*e++); } exit(0); }

That'll work fine if all you want out of /bin/env is to print the environment
but how about the rest of the functionality of env?  It's in the code to
handle the selective addition of environment variables in which the bug occurs.
It's not that difficult of a job, but it's not a one-liner either.


-- 
	-Mike Wescott
	 wescott@ncrcae.Columbia.NCR.COM