[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [External] Changing TERM TERM to HUP TERM

From: Rech, Andrew
Subject: Re: [External] Changing TERM TERM to HUP TERM
Date: Mon, 11 Mar 2019 10:41:04 +0000

Ole, I agree this change would be ideal, inasmuch as any TERM should kill the 
program. But the cost of this breaking change is potentially high in scripts 
running long jobs, and the upshot small - sending two TERM signals is not 
difficult, and the message after the first is clear.

A big advantage, in my opinion, of GNU Parallel is that it is simple to use and 
just works. Echoing Shyam, if you do this, perhaps consider deprecating the 
current behavior first in addition to an announcement.


> On Mar 11, 2019, at 01:33, Gary Johnson <address@hidden> wrote:
> On 2019-03-10, Ole Tange wrote:
>> To stop GNU Parallel today you need to send TERM to make it stop
>> starting new jobs followed by another TERM to kill the running jobs.
>> I am considering changing that to send HUP to stop starting new jobs
>> and TERM to kill running jobs.
>> This will make it easier to kill GNU Parallel:
>> $ bash -c 'parallel -j1 sleep ::: 111 222' &
>> # This would then kill the process group with bash and parallel
>> $ kill -TERM -$!
>> It will make it incompatible with previous versions.
>> What is your opinion?
> A change seems OK, but using HUP for this purpose doesn't seem like
> a good idea.  Its meaning is specified in the signal(7) man page and
> that doesn't seem to match your proposed usage.  How about using
> USR1 or USR2 instead?
> Regards,
> Gary

reply via email to

[Prev in Thread] Current Thread [Next in Thread]