Re: [go-nuts] exec.CommandContext wrong behavior

2017-05-16 Thread Peter Waller
On 16 May 2017 at 12:56, wrote: > > [... kill does not kill all the processes ...] Is this normal behavior? It > seems strange. > One moment of enlightenment for me was to discover why CTRL-C at the terminal kills all of the processes, while kill(pid, SIG{whatever}) to the parent process does not

Re: [go-nuts] exec.CommandContext wrong behavior

2017-05-16 Thread Ian Lance Taylor
On Tue, May 16, 2017 at 4:56 AM, wrote: > > I have some code: > > ... > > func RunTimeout(c *exec.Cmd, cnl context.CancelFunc) error { >defer cnl() >if err := c.Start(); err != nil { > return err >} > >return c.Wait() > } > > func main() { >ct

[go-nuts] exec.CommandContext wrong behavior

2017-05-16 Thread yuri . shakhmatov
Hi, all. I have some code: ... func RunTimeout(c *exec.Cmd, cnl context.CancelFunc) error { defer cnl() if err := c.Start(); err != nil { return err } return c.Wait() } func main() { ctx, cnl := context.WithTimeout(context.Background(), 10*time.