From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12866] New: should we be disabling bash executable path caching?
Date: Fri, 08 May 2020 19:12:15 +0000 [thread overview]
Message-ID: <bug-12866-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=12866
Bug ID: 12866
Summary: should we be disabling bash executable path caching?
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: matthew.weber at rockwellcollins.com
CC: buildroot at uclibc.org
Target Milestone: ---
I'm not sure if there is a use case (yet), maybe with parallel builds if the
host folder contents ends up with per package staging?
https://unix.stackexchange.com/questions/5609/how-do-i-clear-bashs-cache-of-paths-to-executables/218681#218681
We ran into it when we were testing the internal toolchain of buildroot to be
relocatable and the "mv" executable was used to rename the host folder. Then
we used "mv" again to rename the host folder back. For the first "mv" it used
the Buildroot host/bin/mv and then for the second "mv", bash tried to again use
the same instead of continuing to traverse to /bin/mv which was in the path and
the output of "which mv" at that point in the script.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-05-08 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 19:12 bugzilla at busybox.net [this message]
2020-05-09 9:58 ` [Buildroot] [Bug 12866] should we be disabling bash executable path caching? bugzilla at busybox.net
2020-05-11 12:06 ` bugzilla at busybox.net
2020-05-11 12:07 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-12866-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.