On Tue 18 Mar 2014 01:04:03 Linda Walsh wrote:
> Chet Ramey wrote:
> > Because the execution fails in a child process.  You'd be able to fix it
> > for that process, but would do nothing about the contents of the parent
> > shell's hash table.
> > 
> > The way the option works now is to check the hash lookups and delete
> > anything that is no longer an executable file, then redo the lookup and
> > hash the new value.
> 
> ----
> Wouldn't bash notice that the child exited in <.1 seconds (
> or is it less?

as soon as you talk about trying to time something, you're obviously looking 
at it wrong.  having a system that only works when the cpu/disk is fast and 
idle is a waste of time and bad for everyone.

if bash could rely on real time signals, sigqueue could be used to send a 
signal with attached info (like ENOEXEC) and the parent could look for that.

alternatively, accept that it's not a real problem in practice for the 
majority of people as Chet has pointed out ;).
-mike

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to