Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!uwvax!oddjob!gargoyle!ihnp4!cbosgd!osu-eddie!dsacg1!ddmtg1!mzw9022 From: mzw9022@ddmtg1.UUCP (grinder) Newsgroups: comp.unix.questions Subject: Re: $PATH glitch? -- Gould Powernode Message-ID: <19@ddmtg1.UUCP> Date: Mon, 27-Jul-87 15:28:52 EDT Article-I.D.: ddmtg1.19 Posted: Mon Jul 27 15:28:52 1987 Date-Received: Wed, 29-Jul-87 01:45:25 EDT References: <155@dsacng1.UUCP> Organization: Defense Depot Memphis Lines: 28 Keywords: PATH shell environment Summary: problem with PATH In article <155@dsacng1.UUCP>, naa1810@dsacng1.UUCP (Bill Bereza) writes: > I recently experienced what I consider an inconsistency with > my PATH variable. I had appended my bin directory path to the PATH > > I further experimented and found out that I could not execute a > new shell script that I created in my bin directory from any directory > path except when my cwd was my bin directory. > > I also noted that when I logged off and then back on, all my bin > shell scripts would properly execute from any cwd. > When you log on, an internal hash table (which contains the contents of the directories in the PATH variable) is computed for you. If you add new commands you must recompute this internal hash table if you intend to execute these commands from a directory besides the one the new command is located in. One way to do this is to logoff and log back on, since your internal hash table is set up for you at the time of login. Another way to to this is to type in rehash. This will cause your internal hash table to be recomputed while you are in the C shell. -- Valerie Grinder (DEFENSE DEPOT MEMPHIS TENNESEE) 2163 Airways BLVD Memphis Tn 38114 901-775-6849 AV 683-6849 UUCP: {seismo!gould,cbatt!osu-eddie}!dsacg1!ddmtg1!vgrinder