Red Hat Bugzilla – Bug 612126
bash can't handle moved binaries well
Last modified: 2014-01-12 19:12:24 EST
Description of problem:
bash uses hash table to speed up searching of binaries in PATH, but when binary is moved, bash reports "not found" instead of trying to search again.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
# cp /bin/grep /usr/bin/grep
# type grep
grep is hashed (/usr/bin/grep)
# rm /usr/bin/grep
bash: /usr/bin/grep: No such file or directory
bash should just remove entry from hash table and look for grep again using PATH
This has been already discussed on the upstream mailing list; see http://firstname.lastname@example.org/msg06799.html
well, that discussion on the upstream mailing list is slightly different.
binary in b
add binary in a
-> b is still used
I understand upstream explanation that it'd made hashtable useless if you have to check path all the time, but this is not the bug I'm describing here, because in that case you still can use some binary. Well, discussion if different binary (mailing list case)
my bug report:
remove item from hash table if execution fails because file was removed and this should be pretty well doable and you'll still be able to use hashtable for better performance. When I got this error, it was because some package moved its binary file to different place which resulted in disappearing from bash completely. It took some time to find out what's happening, because the "only" result I got was /usr/bin/binary = "not found" vs. which binary = /usr/bin/binary
hashtable should be also cleared when PATH variable is changed (don't know if this is not already happening, did no test)
Because this bug is not the same as mentioned in the mailing list and fixing this would not prevent using hashtable for its purpose, I think this bug should be reopened.
One thing you missed; the `checkhash'. Try to enable this option with shopt. Yeah, it is not set by default...