Date: Tue, 11 Mar 1997 12:58:54 -0600 From: Steve Price <sprice@hiwaay.net> To: Stephen McKay <syssgm@devetir.qld.gov.au> Cc: freebsd-bugs@freefall.freebsd.org Subject: Re: bin/2934: sh(1) has problems with $ENV Message-ID: <3325AB6E.41C67EA6@hiwaay.net> References: <199703111410.GAA05084@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Stephen McKay wrote: > > I found the original stuff in -hackers, and just to prove that I'm capable > to having a bet each way on each problem :-) I recreated his real problem: > > Under 2.1.5 (at least; can't check anything else right now): > > $ cat ~/junk > echo Hi from junk > $ export ENV=~/junk > $ echo $ENV > ~/junk > $ sh -c date > Tue Mar 11 20:29:58 EST 1997 > $ ENV=~/junk > $ export ENV > $ echo $ENV > /home/syssgm/junk > $ sh -c date > Hi from junk > Tue Mar 11 20:30:42 EST 1997 > $ > > So, ~ expansion happens differently in the two places. Fix one. > Now this I can reproduce. :) I think I know where this is happening. I will add it to my next group of fixes that I had hoped to get in tonight, but with Peter calling a halt to all non-Lite2 commits... As soon as things cool down I will get in the fix. Steve > Of course, when $ENV processing is removed, this will no longer be a > problem. :-) (Am I the only one to heave when 'sh -c prog' executes > $ENV?) > > Stephen.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3325AB6E.41C67EA6>