artix/runit-artix
19
0
Fork 0
Code Issues Pull Requests Releases 1 Wiki Activity

Compare commits

base: artix:20200108
Branches Tags
artix:master artix:new-rc
artix:20210904 artix:20210414 artix:20210413 artix:20200905-3 artix:20200905-2 artix:20200905 artix:20200825 artix:20200803 artix:20200108 artix:20200101-1 artix:20200101 artix:20190212 artix:20180730 artix:20180509 artix:20180507 artix:20180506 artix:20180505.3 artix:20180505.2 artix:20180505 artix:20180414 artix:20180327 artix:20180112 artix:20180108 artix:20171208 artix:20170818
...
compare: artix:20200803
Branches Tags
artix:master artix:new-rc
artix:20210904 artix:20210414 artix:20210413 artix:20200905-3 artix:20200905-2 artix:20200905 artix:20200825 artix:20200803 artix:20200108 artix:20200101-1 artix:20200101 artix:20190212 artix:20180730 artix:20180509 artix:20180507 artix:20180506 artix:20180505.3 artix:20180505.2 artix:20180505 artix:20180414 artix:20180327 artix:20180112 artix:20180108 artix:20171208 artix:20170818

3 Commits
20200108 ... 20200803

Author SHA1 Message Date
Érico Rolim
c75de34303 ctrlaltdel: trigger a reboot properly. 
/run/runit/{stopit,reboot} should have their perms set to 100 by
ctrlaltdel, before runit signals itself with SIGCONT, in order to
trigger a reboot. This script can be changed by a user to perform
different actions. The comments in it explain what each file is for.

Patch created for Void, imported to Artix.
 2020-08-03 23:01:04 +07:00
Érico Rolim
6453301c3b 3: remove /run/runit/reboot handling. 
runit uses the permissions in the /etc/runit/reboot file to determine
whether it's going to perform a halt or reboot action. This conditional
in 3 meant that touching the reboot file, even with 000 perms, would
lead to a reboot, which goes agains what is expected according to the
runit documentation.

Patch made for Void, imported to Artix.
 2020-08-03 23:00:29 +07:00
Érico Rolim
454078d6a0 1: only create /run/runit directory. 
The 100 permission in /run/runit/stopit made it so that signaling runit
with SIGCONT would shut the system down. To achieve the correct
behavior, we should create the stopit and reboot files with 000 perms,
and allow their permissions to be set correctly by calls to `init 0` or
`init 6` or by /etc/runit/ctrlaltdel.

Patch created for Void, imported to Artix.
 2020-08-03 22:59:27 +07:00
3 changed files with 6 additions and 6 deletions
Expand all files Collapse all files

3
script/1.in
View File

@@ -6,6 +6,7 @@ PATH=/usr/bin:/usr/sbin
run_sysinit
install -m100 /dev/null @RUNDIR@/stopit
install -m000 /dev/null @RUNDIR@/stopit
install -m000 /dev/null @RUNDIR@/reboot
status "Initialization complete"

4
script/3.in
View File

@@ -19,10 +19,6 @@ if [ -x @RCDIR@/rc.shutdown ] && grep -qv '^#' @RCDIR@/rc.shutdown; then
fi
[ -x @SYSCONFDIR@/rc.local ] && @SYSCONFDIR@/rc.local
if [ -e @RUNDIR@/reboot ]; then
chmod 100 @RUNDIR@/reboot
fi
run_shutdown
if [ -e @RUNDIR@/reboot ]; then

5
script/ctrlaltdel.in
View File

@@ -3,8 +3,11 @@
PATH=/usr/bin:/usr/sbin
MSG="System is going down..."
# We check for this file after receiving a SIGCONT to move to stage3
chmod 100 @RUNDIR@/stopit
# We check for this file in stage3 to halt or reboot
touch @RUNDIR@/reboot
chmod 100 @RUNDIR@/reboot
# Proceed with shutdown process
echo "$MSG" | wall