On Tue, Feb 22, 2022 at 02:36:23PM +0100, Lorenzo wrote:
> > On Mon, 19 Apr 2021 09:45:53 +0200
> > Andras Korn <korn-debb...@elan.rulez.org> wrote:
> >
> > > Additionally, the documentation as it is now is clear and
> > > straightforward, with few special cases; while the actual behaviour
> > > of runsv, while I agree it can make sense, is more difficult to
> > > explain clearly.
>
> --- ./runsv.8-orig 2022-01-03 03:00:49.000000000 +0100
> +++ ./runsv.8 2022-02-22 01:12:29.438824451 +0100
> @@ -185,16 +185,18 @@
> .IR u .
> On command
> .I d
> -first
> +first the service receives the TERM signal, subject to the
> .I service\fR/control/t
> -is checked, and then
> -.I service\fR/control/d.
> +check, then the service receives a CONT signal and finally
> +.I service\fR/control/d
> +is checked.
> On command
> .I x
> -first
> +first the service receives the TERM signal, subject to the
> .I service\fR/control/t
> -is checked, and then
> -.I service\fR/control/x.
> +check, then the service receives a CONT signal and finally
> +.I service\fR/control/x
> +is checked.
> The control of the optional log service cannot be customized.
> .SH SIGNALS
> If
>
>
> I'm not fully satisfied but it should at least make clear that you
> can't prevent a TERM with control/[dx]..
> Still doesn't tell that control/c is disregarded and that for
> control/[dx] checked only means exists and is executable.
Thanks for keeping tabs on this!
Unfortunately it's been so long that I have trouble reconstructing what the
actual behaviour (as opposed to the documented one) is, and I don't have
time to reread the source code just now.
However, if there were a natural-language explanation or flowchart, I think
I could summarize it succinctly in a manner appropriate for the man page,
within a day.
Alas, that's all the help I can offer at the moment.
András
--
Well, to be Frank, I'd have to change my name.
