Re: [BUG] Bash not reacting to Ctrl-C

[Chet Ramey]

On 2/9/11 4:39 PM, Oleg Nesterov wrote:

> If /bin/true gets SIGINT - everything is fine. With this particular
> test-case the problem is: ^C race race with true/false/whatever
> doing exit(any_exit_code). In this case the shell "ignores" the
> signal.

Yes, there is a race condition there.  That's what was preventing the
shell from `reacting' to the /bin/true loop case.  The question of
whether the shell should leave a SIGINT to the disposition of the
foreground process is not up for debate.

Chet
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/