Bug 612126
Summary: | bash can't handle moved binaries well | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Michal Hlavinka <mhlavink> |
Component: | bash | Assignee: | Roman Rakus <rrakus> |
Status: | CLOSED NOTABUG | QA Contact: | BaseOS QE - Apps <qe-baseos-apps> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 6.0 | CC: | ovasik, tsmetana |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-07-23 12:39:50 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Michal Hlavinka
2010-07-07 11:28:04 UTC
This has been already discussed on the upstream mailing list; see http://www.mail-archive.com/bug-bash@gnu.org/msg06799.html well, that discussion on the upstream mailing list is slightly different. mailing list: PATH=a:b:... 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... |