Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: "kill -STOP" as noticed in ksh93u+ gitlab
- X-seq: zsh-workers 52631
- From: Stephane Chazelas <stephane@xxxxxxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Cc: Zsh hackers list <zsh-workers@xxxxxxx>
- Subject: Re: "kill -STOP" as noticed in ksh93u+ gitlab
- Date: Wed, 28 Feb 2024 05:39:34 +0000
- Archived-at: <https://zsh.org/workers/52631>
- In-reply-to: <CAH+w=7Z+L_HoC4AkTzxZSn9WtwK6b9MUZgpOds-cMh+iU2J7oA@mail.gmail.com>
- List-id: <zsh-workers.zsh.org>
- Mail-followup-to: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>, Zsh hackers list <zsh-workers@xxxxxxx>
- References: <CAH+w=7ai29H+yFvKCwHeALRRykDbH+M3=QZsM2eHjf15shX-Jw@mail.gmail.com> <20240227070502.ek5ocpwxm6cpp5gz@chazelas.org> <CAH+w=7Z+L_HoC4AkTzxZSn9WtwK6b9MUZgpOds-cMh+iU2J7oA@mail.gmail.com>
2024-02-27 18:04:34 -0800, Bart Schaefer:
[...]
> Changing the "kill" command doesn't (in zsh at least) affect the
> "suspend" command.
>
> schaefer[592] Src/zsh -f -o login
> % suspend
> suspend: can't suspend login shell
> % suspend -f
>
> zsh: suspended Src/zsh -f -o login
> schaefer[593] fg
> [1] + continued Src/zsh -f -o login
> % kill -STOP $$
> kill: kill 605210 failed: operation not permitted
> %
[...]
I can't reproduce that on Ubuntu 22.04. The wording of that
error suggests it's the system blocking the kill() with EPERM.
> I think this is more to prevent accidental stoppage?
I'm still of the opinion that "kill pid" is low level enough an
interface to kill() that it should not be interfered with, but
that's not a strong opinion by any measure.
If we're blocking kill -s STOP $$, should we also block kill -s
STOP 0 and kill -s STOP -1?
--
Stephane
Messages sorted by:
Reverse Date,
Date,
Thread,
Author