Package: runit Version: 2.1.2-10 Severity: minor hi dmitry,
i just stumbled upon the runscript mechanism in the unreleased version
in git, and noticed two things:
* there is a typo ("unprivilleged" -> "unprivileged") that's probably
easier to change now than when it's shipped, especially since it'd
make its way into user files where it's hard to change later-on
* running nested runsvdirs, in my experience, needs special care that i
did not see taken in the current script: when the outer service is
taken down, the inner runsvdir process is sent the term signal. this
makes it exit immediately, leaving the inner runsv instances running
and hard to re-gain control of.
if a `control/t` file is placed with `#!/bin/sh` / `exec sv -v h .`,
then the runsvdir gets a SIGHUP first, terminates its child processes
and then exits. i think this would be the less surprising behavior for
such scripts.
best regards, and thanks for maintaining runit
(which i'm using from server init to user processes)
chrysn
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages runit depends on:
ii libc6 2.24-17
runit recommends no packages.
runit suggests no packages.
-- no debconf information
--
To use raw power is to make yourself infinitely vulnerable to greater powers.
-- Bene Gesserit axiom
signature.asc
Description: PGP signature
