Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site umcp-cs.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!houxm!houxz!vax135!floyd!cmcl2!seismo!rlgvax!cvl!umcp-cs!chris
From: chris@umcp-cs.UUCP
Newsgroups: net.unix-wizards
Subject: Re: Automatic Csh rehashing?
Message-ID: <7466@umcp-cs.UUCP>
Date: Tue, 12-Jun-84 00:07:56 EDT
Article-I.D.: umcp-cs.7466
Posted: Tue Jun 12 00:07:56 1984
Date-Received: Tue, 12-Jun-84 23:59:15 EDT
References: <960@elsie.UUCP>
Organization: Univ. of Maryland, Computer Science Dept.
Lines: 16

Actually, simply logging in on a loaded system can be quite a pain
when the C shell goes to hash $path.  I've occasionally logged in
and had to wait 5 minutes or more before the ``set path'' completed.
(I have my .cshrc set up to print ``['' as it starts, and ``cshrc]''
after the ``set path''; that's how I know how long it takes.)

Here's my counter-proposal:  don't initialize the hash list all at
once.  Instead, every time a command works (except for those in
``.'' of course), put *that* in the list.  Voila!  No ``rehash''
required (unless you just installed /usr/local/bin/make and want
to get that instead of /usr/bin/make), and no initial startup
delays.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci (301) 454-7690
UUCP:	{seismo,allegra,brl-bmd}!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@maryland