Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!dog.ee.lbl.gov!nosc!humu!pilikia!art
From: art@pilikia.pegasus.com (Art Neilson)
Newsgroups: comp.unix.questions
Subject: Re: csh path
Keywords: csh path environment variable
Message-ID: <1991Mar10.053404.29933@pilikia.pegasus.com>
Date: 10 Mar 91 05:34:04 GMT
References: <5965@beryl12.UUCP>
Distribution: comp
Organization: Pilikia, Honolulu
Lines: 20

In article <5965@beryl12.UUCP> mostek@motcid.UUCP (Frank B. Mostek) writes:
>When I add a new image to a bin directory that is included in my path
>csh environment variable, I have to "re-setenv" the path variable in
>order for the new image to be found.
>
>Why?  Is there a way around this?  When I add a new tool, I have to
>tell everyone to re-source their .cshrc file.  But if I update an image
>file, then the re-sourcing is not necessary.

The C shell keeps an internal hash table for finding commands in your $path.
This table is built when you log in, if you add a new executable to a
directory in the path you need you tell the C shell to rebuild it's hash
table.  The easiest way of doing this is via the 'rehash' command.  At the
% prompt, just type 'rehash', and csh will be able to find the new
executables in the path.  Alternatively, you can log out and back in again,
or "re-setenv" the path variable as you have been doing.

-- 
Arthur W. Neilson III		| INET: art@pilikia.pegasus.com
Bank of Hawaii Tech Support	| UUCP: uunet!ucsd!nosc!pilikia!art