Xref: utzoo comp.unix.questions:15100 comp.bugs.sys5:1049 comp.unix.microport:3602
Path: utzoo!attcan!uunet!wugate!wuarchive!brutus.cs.uiuc.edu!apple!sun-barr!newstop!sun!athena1!williamt
From: williamt@athena1.Sun.COM (William A. Turnbow)
Newsgroups: comp.unix.questions,comp.bugs.sys5,comp.unix.microport
Subject: Re: ksh and sh
Message-ID: <117087@sun.Eng.Sun.COM>
Date: 21 Jul 89 22:52:53 GMT
Sender: news@sun.Eng.Sun.COM
Reply-To: williamt@sun.UUCP (William A. Turnbow)
Lines: 19

In article <8282@boring.cwi.nl> aeb@cwi.nl (Andries Brouwer) writes:
>These tracked aliases were not invented because they are useful,
>but because they save a few milliseconds on each command that I
>give.
-----------

	Not that I disagree with making it an option, but your above
statement is inaccurate in a networked environment or if you have a
long path.  I have anywhere from 15 to 25 path components, all of which
are remote mounts.  Due to distance, heavy loading or just plain lost
requests, searching all these directories can some times take several
seconds (usually under 1-2 though).  This is only an annoyance at the
interactive level.

	However, when running shell scripts, if your executable that you are
using alot is in one of the later directories, you are talking about
a POTENTIALLY much greater period of time.

-wat-