Return to BSD News archive
Newsgroups: comp.unix.bsd
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!caen!hellgate.utah.edu!fcom.cc.utah.edu!cs.weber.edu!terry
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: binaries are unavailable when moved to /usr/bin until re-logon
Message-ID: <1992Sep22.175228.22803@fcom.cc.utah.edu>
Sender: news@fcom.cc.utah.edu
Organization: Weber State University (Ogden, UT)
References: <1992Sep21.175158.25399@Saigon.COM>
Date: Tue, 22 Sep 92 17:52:28 GMT
Lines: 35
In article <1992Sep21.175158.25399@Saigon.COM> David.Fox@Saigon.COM writes:
>After doing a few rounds of getting source-code to something, compiling it,
>building the binary of it, and then moving it into its proper place (usr/
>bin, or /usr/local/bin) I've noticed that when I attempt to run the command
>once it has been moved - even though it certainly is in the path - that
>the system responds with "Command not found." However, when I relogon, the
>file now is accessible.
>
>Coming from a DOS world, I'm used to having the commands available immediately
>after they've been moved, assuming of course, the directory they are moved to
>is in the path.
>
>This doesn't seem to be the case with 386BSD. Question: is this expected
>behavior?
If you are using csh or a relative:
Lookup of command names is hashed (because of the very slow responsiveness
seen in paces like the DOS world as the entire path is searched and then
the command is run).
Soloution: type "rehash"
Terry Lambert
terry_lambert@gateway.novell.com
terry@icarus.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.
--
-------------------------------------------------------------------------------
"I have an 8 user poetic license" - me
Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------