Source: runit Version: 2.1.2-35 Severity: important Dear Maintainer,
as in policy 9.3.3. Interfacing with init systems rc.d should not be called directly, but invoke-rc.d should be used. This allows one to control environment with policy-rc.d hack. Unfortunatelly runit does not follow this rule, this lead to some unexpected issues: e.g. I want to run several process inside docker container (or other limited environment): - I disable rc.d scripts with policy-rc.d - create /etc/sv config for daemons - set runit as entrypoint But, unexpectedly, runit starts my other process with /lib/runit/run_sysv_scripts -- System Information: Debian Release: 10.2 APT prefers stable-updates APT policy: (670, 'stable-updates'), (670, 'stable'), (630, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-0.bpo.2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
