Re: Cleaning up background processes

In article <slrnv3v0m5.17e3.naddy@lorvorc.mips.inka.de>,
Christian Weisgerber  <naddy@mips.inka.de> wrote:

On 2024-05-08, vallor <vallor@cultnix.org> wrote:
>

I'm sorry, but I've waited and nobody said anything, so
I have to ask:  Why couldn't you trap "kill -1 0" INT?

>
There is the cosmetic problem that you'll get termination notices
referring to the new signal ("Hangup"), so I'll go with the less
confusing
>
       trap "kill -TERM 0" INT
>
but yes, it may be as simple as that.  Let me run some tests...

I don't get it.  Is there any significant difference between hitting it with
TERM vs. HUP?  I think either/both will generate the message to which you
allude.

Anyway, to answer the "Can't you just...?" question posed earlier, the
answer is there really is no general answer - one that will work in all
cases, all the time.  Answering the overall thread question is also both
shell- and OS- specific. 

Personally, I'd be happy to have a good, solid solution that was both Linux-
and bash-specific, but it sounds like OP is (unfortunately) running some
version of BSD.

I will expand on this further in my next post.

--

    "This ain't my first time at the rodeo"

is a line from the movie, Mommie Dearest, said by Joan Crawford at a board meeting.