Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!uunet!mcsun!Germany.EU.net!unidui!du9ds3!veit From: veit@du9ds3.uni-duisburg.de (Holger Veit) Newsgroups: comp.unix.bsd Subject: Re: binaries are unavailable when moved to /usr/bin until re-logon Date: 23 Sep 92 06:22:03 GMT Organization: Uni-Duisburg FB9 Datenverarbeitung Lines: 29 Message-ID: <veit.717229323@du9ds3> References: <1992Sep21.175158.25399@Saigon.COM> Reply-To: veit@du9ds3.uni-duisburg.de NNTP-Posting-Host: du9ds3.uni-duisburg.de In <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? Did you try the command 'rehash' in the shell after installation? Read the manual page on this. The shells maintain a cache for the locations of programs in the path, so it usually does not search the whole path for a program to be executed, but instead relies on its cache. rehash updates the cache. Holger -- | | / Dr. Holger Veit | INTERNET: veit@du9ds3.uni-duisburg.de |__| / University of Duisburg | "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX | | / Dept. of Electr. Eng. | Sorry, the above really good fortune has | |/ Inst. f. Dataprocessing | been CENSORED because of obscenity"