Linda Walsh wrote:
Sure, you could forget the timing part -- and have bash check
for every child, it's reason for exiting and if ENOENT, then check
whatever path the child was just spawned with if you wanted a general
solution for a low-incident problem. It would still be better than
having the parent "poll" each time to see if anything has changed.
----
Why not just have the failed path lookup cause the child to
scan PATH again? That would put the cost in the child and
the parent wouldn't have to change...?
The cost would only be in the child on each execution of
that 'exe' after that -- but could be eliminated if the user
rehash's the parents path.
That would put the cost of a failure case only in the outlier case,
no?
