APLawrence - Information and Resources for Unix and Linux Systems, Bloggers and the self-employed
RSS Feeds Get APLawrence.com by RSS














Front Loading Commands


This is the answer to Front Loading Commands

The bash shell maintains a table of commands you have used so that it can execute them more quickly without looking them up in $PATH. You can see the current list and the number of times you have used the command just by typing "hash".

If you type "ls", the shell remembers where it found it, and won't look in $PATH again until you reset $PATH or you explicitly type "hash -r". So, if this administrator probably did something like this:

# PATH=/specialstuff:$PATH
# ls
# cp mynewls /specialstuff/ls
 

The first command reset the hash table. However, he then ran "ls" - he probably forgot what he called his version and needed to see it before he could give the right copy command. The hash was reset by setting $PATH, so bash had to search each directory again to find "ls", but since there was not yet any "ls" in /specialstuff, bash found the system /bin/ls again. Bash put /bin/ls into its hash table so that it wouldn't have to search $PATH yet again. The cp put ls into /specialstuff, but nothing told bash to update its hash, so as far as it was concerned, the version in /bin was still the right one to use. The "which" command looks through $PATH, but doesn't look in the hash table (it probably should), so it confused things even more.



Comments?



Click here to add your comments



Don't miss responses! Subscribe to Comments by RSS or by Email

Click here to add your comments


If you want a picture to show with your comment, go get a Gravatar



Auto FTP Manager

Have you tried Searching this site?

Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.

Publishing your articles here

Jump to Comments



Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.


My Troubleshooting E-Book will show you how to solve tough problems on Linux and Unix systems!


book graphic unix and linux troubleshooting guide


 I sell and support
 Kerio Mail server




pavatar.jpg

This post tagged:





Unix/Linux Consultants

Skills Tests

Guest Post Here