Re: process substitution and Ctrl-C

[Peter Stephenson <Peter.Stephenson@csr.com>]

On Thu, 19 Aug 2010 14:41:42 +0200
Vincent Lefevre <vincent@vinc17.net> wrote:
> In the following example:
> 
>   { repeat 10 { date >&2; /bin/sleep 1 } } 2>>(cat -n; loop)
> 
> where "loop" is a program that consumes CPU time, is it normal that
> when one interrupts the command with Ctrl-C, the substituted process
> isn't killed? (I can see "loop" taking CPU time.)

Without looking at the code, I wouldn't be at all surprised: unless we did
something special, SIGINT would go only to foreground processes, which
wouldn't include the process substitution.  Logically, you might have
thought that passing the SIGINT as received by the shell on to associated
processes (which are recorded in a part of the job record) should be
possible, but this sort of thing is fairly well down my personal list of
priorities.

-- 
Peter Stephenson <pws@csr.com>            Software Engineer
Tel: +44 (0)1223 692070                   Cambridge Silicon Radio Limited
Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, UK


Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom