Xref: utzoo comp.unix.questions:15012 comp.bugs.sys5:1036 comp.unix.microport:3590
Path: utzoo!utgpu!watmath!att!bellcore!texbell!texsun!sun-barr!apple!bionet!agate!ucbvax!ulysses!hector!ekrell
From: ekrell@hector.UUCP (Eduardo Krell)
Newsgroups: comp.unix.questions,comp.bugs.sys5,comp.unix.microport
Subject: Re: ksh and sh
Message-ID: <11900@ulysses.homer.nj.att.com>
Date: 18 Jul 89 21:51:50 GMT
References: <372@trevan.UUCP> <8272@boring.cwi.nl>
Sender: netnews@ulysses.homer.nj.att.com
Reply-To: ekrell@hector.UUCP (Eduardo Krell)
Organization: AT&T Bell Laboratories
Lines: 20

In article <8272@boring.cwi.nl> aeb@cwi.nl (Andries Brouwer) writes:

>I have been bitten several times, especially when installing new
>versions of system software, by the fact that ksh does not
>search the PATH for each command, but remembers where the command
>was. (I.e., some commands, sometimes all commands,
>are tracked aliases. There is an option to make all commands
>tracked aliases, but none to switch off this `feature'.)

I believe all you have to do is change the value of $PATH to
force ksh into unbinding all the tracked aliases. I use

PATH=$PATH

which doesn't change the value of $PATH, but makes ksh throw
away the old bindings.
    
Eduardo Krell                   AT&T Bell Laboratories, Murray Hill, NJ

UUCP: {att,decvax,ucbvax}!ulysses!ekrell  Internet: ekrell@ulysses.att.com