[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Your opinion needed: Should GNU Parallel ignore, kill or wait for ba
From: |
Jan Engelhardt |
Subject: |
Re: Your opinion needed: Should GNU Parallel ignore, kill or wait for background children? |
Date: |
Tue, 24 May 2016 02:03:08 +0200 (CEST) |
User-agent: |
Alpine 2.20 (LSU 67 2015-01-07) |
On Tuesday 2016-05-24 00:46, Ole Tange wrote:
>Should GNU Parallel ignore, kill or wait for background children?
Implementations that are capable of tracking all children ever
created (such as cgroups, as for example used by systemd) have no
reason to ignore, since they know what processes to wait for/to kill.
Whether wait or kill, that's best left as a user option. Even
programs not as controversial as init systems show different default
behavior when it comes to (all kinds of) child "objects".
ssh -L would wait for all tunneled TCP connections to close first,
while ending the initial X client that was started from xinitrc
will cause progression in the xinitrc script and often tear down
the X server, killing everything else connected to it.
- Your opinion needed: Should GNU Parallel ignore, kill or wait for background children?, Ole Tange, 2016/05/23
- Re: Your opinion needed: Should GNU Parallel ignore, kill or wait for background children?, Josef wells, 2016/05/23
- RE: Your opinion needed: Should GNU Parallel ignore, kill or wait for background children?, Cook, Malcolm, 2016/05/23
- Re: Your opinion needed: Should GNU Parallel ignore, kill or wait for background children?,
Jan Engelhardt <=
- Re: Your opinion needed: Should GNU Parallel ignore, kill or wait for background children?, Martin d'Anjou, 2016/05/23