Package: runit
Version: 2.1.2-17
Severity: normal
Dear Maintainer,
When using the "single" kernel parameter, sulogin is started in stage 1.
Signals only work in stage 2, and so reboot and shutdown commands don't work.
In order to rectify this problem, I implemented Void Linux's solution, where
custom runsvdirs can be created in stage 2. This way, if "single" is used,
stage 2 will start services in /etc/runit/runsvdir/single. An sulogin service,
which is also provided by Void, is needed in the single folder. A relative
symlink from /etc/runit/runsvdir/default to /etc/runit/runsvdir/current is
also needed for the runsvchdir command to switch runsvdirs. Currently, this
problem effects all debian releases.
-- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: runit-init (via /sbin/init)
Versions of packages runit depends on:
ii libc6 2.27-8
ii runit-helper 2.7.3
Versions of packages runit recommends:
ii runit-init 2.1.2-17
runit suggests no packages.
-- Configuration Files:
/etc/runit/1 changed:
PATH=/sbin:/usr/sbin:/bin:/usr/bin
run_sysv_scripts () {
initdir="${1}"
for script in "$initdir/S"* ; do
path=$(realpath "$script")
name=$(basename "$path")
# Special case for wicd. Runscript is called "wicd-daemon",
# to match binary package name.
[ -d "/etc/sv/$name" ] && continue
[ -d "/etc/sv/$name-daemon" ] && continue
"$script" start
done
unset path name initdir
}
run_sysv_scripts '/etc/rcS.d'
touch /run/runit.stopit
chmod 0 /run/runit.stopit
run_sysv_scripts '/etc/rc2.d'
/etc/runit/2 changed:
PATH=/sbin:/usr/sbin:/bin:/usr/bin
runlevel=default
for arg in $(cat /proc/cmdline); do
if [ -d /etc/runit/runsvdir/"$arg" ]; then
echo "Runlevel detected: '$arg' (via kernel cmdline)"
runlevel="$arg"
fi
done
runsvchdir "${runlevel}"
exec env - PATH=$PATH
runsvdir -P /etc/service 'log:
...........................................................................................................................................................................................................................................................................................................................................................................................................'
-- no debconf information
