Xref: utzoo comp.unix.questions:15107 comp.bugs.sys5:1051 comp.unix.microport:3607
Path: utzoo!attcan!uunet!ginosko!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!cwjcc!hal!ncoast!allbery
From: allbery@ncoast.ORG (Brandon S. Allbery)
Newsgroups: comp.unix.questions,comp.bugs.sys5,comp.unix.microport
Subject: Re: ksh and sh
Message-ID: <14286@ncoast.ORG>
Date: 22 Jul 89 15:00:06 GMT
References: <372@trevan.UUCP> <8272@boring.cwi.nl> <11900@ulysses.homer.nj.att.com>
Reply-To: allbery@ncoast.ORG (Brandon S. Allbery)
Followup-To: comp.unix.questions
Organization: Cleveland Public Access UN*X, Cleveland, Oh
Lines: 25

As quoted from <11900@ulysses.homer.nj.att.com> by ekrell@hector.UUCP (Eduardo Krell):
+---------------
| 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
+---------------

Sure there's a way to get ksh to stop tracking:  "set +o trackall".
You must still use "PATH=$PATH" or "hash -r" to zap the current tracked
aliases, but after the "set" you won't have to worry about it any more.

++Brandon
-- 
Brandon S. Allbery, moderator of comp.sources.misc	     allbery@NCoast.ORG
uunet!hal.cwru.edu!ncoast!allbery		    ncoast!allbery@hal.cwru.edu
NCoast Public Access UN*X - (216) 781-6201, 300/1200/2400 baud, login: makeuser
 (Send inquiries to rhg@NCoast.ORG, *not* to me!  I'm just the resident guru.)
* "ncoast" regenerates again!  The 5th "ncoast", coming August 1 (stay tuned) *