Martin Cracauer wrote: > > OK, the problem is real. > > BTW, its worse: > > #! /bin/sh > hash -v > PATH=/sbin:/bin > PATH=/foo:/bar:/bin ls > hash -v > ls > > => coredump It seems to me that when there's a PATH= assignment you don't want to add anything to the cache or alternatively, clear the cache after execution of the command having a PATH= assignment. -- Marcel Moolenaar mailto:[EMAIL PROTECTED] SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- sh(1) broken caching [was: Re: Broken sh(1)?] Marcel Moolenaar
- Re: sh(1) broken caching [was: Re: Broken s... Martin Cracauer
- Re: sh(1) broken caching [was: Re: Brok... Marcel Moolenaar
- Re: sh(1) broken caching [was: Re: Brok... Mike Smith
- Re: sh(1) broken caching [was: Re: Broken s... Martin Cracauer
- Re: sh(1) broken caching [was: Re: Brok... Marcel Moolenaar
- Re: sh(1) broken caching [was: Re: ... Martin Cracauer
- Re: sh(1) broken caching [was: ... Marcel Moolenaar
- Re: sh(1) broken caching [... Martin Cracauer
- Re: sh(1) broken caching [was: Re: Broken s... Martin Cracauer
- Re: sh(1) broken caching [was: Re: Brok... David O'Brien
- Re: sh(1) broken caching [was: Re: ... Martin Cracauer
- Re: sh(1) broken caching [was: ... Brian Fundakowski Feldman
- Re: sh(1) broken caching [... Martin Cracauer
- Re: sh(1) broken cachi... Brian Fundakowski Feldman
- Re: sh(1) broken c... Martin Cracauer