Path: ...!weretis.net!feeder8.news.weretis.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Martijn Dekker <martijn@inlv.demon.nl>
Newsgroups: comp.unix.shell
Subject: Re: Cleaning up background processes
Date: Sun, 19 May 2024 20:34:41 +0100
Lines: 15
Message-ID: <lav2ihFjo73U1@mid.individual.net>
References: <slrnv3fm5e.jrj.naddy@lorvorc.mips.inka.de>
 <20240505214609.114@kylheku.com> <v1ah87$l0a8$1@news.xmission.com>
 <v1gpdq$3me9$1@dont-email.me> <v1h0hk$7rkr$1@dont-email.me>
 <ptg1hk-7n3.ln1@ID-313840.user.individual.net> <v1l5k7$1c28l$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net ABZJ8202ZOkKopcE3pR39AA4zJixGPP1h0VbgSlkJ1mE5SguQ=
Cancel-Lock: sha1:E4bQ+Cj9M7HMSM/gTZ4GgeKuh/8= sha256:q8AQOr1jYjXLj3eT7zzmnfsfPmGTXTzkVLUCpUT+sk8=
User-Agent: Mozilla Thunderbird
Content-Language: en-GB
In-Reply-To: <v1l5k7$1c28l$1@dont-email.me>
Bytes: 1595

Op 10-05-2024 om 13:57 schreef Janis Papanagnou:
> BTW, I'm astonished about the "undefined results" for KILL/STOP. Yes,
> on OS-level they cannot be caught but why undefined behavior on shell
> level; what is the reason or practical rationale for that?

I suspect it was to allow the shell to error out on an attempt to trap those 
signals. As far as I know, yash is the only shell that actually does that.

-- 
||    modernish -- harness the shell
||    https://github.com/modernish/modernish
||
||    KornShell lives!
||    https://github.com/ksh93/ksh