|
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !! |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Problem Setting $PATH | greengrass | SUN Solaris | 1 | 04-08-2007 12:40 AM |
| Problem with File path | sandeep_hi | Shell Programming and Scripting | 3 | 06-19-2006 09:21 PM |
| path problem | rajan_ka1 | UNIX for Advanced & Expert Users | 10 | 02-27-2006 06:24 AM |
| path problem | rajan_ka1 | Shell Programming and Scripting | 1 | 02-23-2006 08:58 AM |
| cc path problem - no acceptable path found | kendokendokendo | UNIX for Dummies Questions & Answers | 2 | 09-12-2005 10:52 AM |
Powered by 
|
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
4 Weeks Ago
|
|||||
|
|||||
|
Usually, rebooting is the last measure you should take. Modern shells normally create a lookup table for commands, so that the path doesn't have to be searched every time. If you install a program in a different path, but with the same name, the old lookup entry (hash) still points to the old program.
Depending on your shell, you can make it forget it's lookup entries using 'rehash' or 'hash -r'. And even if that doesn't work, closing the shell and/or opening a new one (logging out and logging in) should have the same effect. |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
Threaded Mode
