# sv check mpd
ok: run: mpd: (pid 1223) 561s
# sv check upmpdcli                                         
ok: run: upmpdcli: (pid 2054) 202s
# pstree
runit─┬─runsvdir─┬─runsv─┬─svlogd
      │          │       └─upmpdcli───13*[{upmpdcli}]
      │          └─runsv─┬─mpd───2*[{mpd}]
      │                  └─svlogd
      ├─sshd───sshd───sshd───mksh───pstree
      └─udevd───udevd
#

I followed the instructions in this thread:

• create /etc/sv/$service/log and the associated (executable) run files

• symlink the service directory to /etc/service/

• copy & divert the /etc/init.d/ script

• symlink /usr/bin/sv to /etc/init.d/

Here are the service run files if anybody's interested:

$ cat /etc/sv/mpd/run                                       
#!/bin/sh -e
if ! [ -d /run/mpd ]; then
        mkdir /run/mpd
        chmod 0755 /run/mpd
        chown -R mpd /run/mpd
fi
exec chpst -u mpd mpd --stdout --no-daemon /etc/mpd.conf
$ cat /etc/sv/upmpdcli/run                                  
#!/bin/sh -e
exec chpst -u upmpdcli upmpdcli -c /etc/upmpdcli.conf
$

The log run files are as described earlier (also executable).

sv status /etc/sv/*
run: /etc/sv/acpid: (pid 1849) 895s; run: log: (pid 1847) 895s
run: /etc/sv/acpi-fakekey: (pid 1820) 895s; run: log: (pid 1819) 895s
run: /etc/sv/cron: (pid 1815) 895s; run: log: (pid 1814) 895s
run: /etc/sv/dbus: (pid 1825) 895s; run: log: (pid 1824) 895s
run: /etc/sv/elogind: (pid 1829) 895s; run: log: (pid 1821) 895s
run: /etc/sv/getty-tty1: (pid 1816) 895s
run: /etc/sv/getty-tty2: (pid 1813) 895s
run: /etc/sv/getty-tty3: (pid 1826) 895s
run: /etc/sv/getty-tty4: (pid 1830) 895s
run: /etc/sv/getty-tty5: (pid 1835) 895s
run: /etc/sv/getty-tty6: (pid 1831) 895s
warning: /etc/sv/getty-ttyS0: unable to open supervise/ok: file does not exist
run: /etc/sv/haveged: (pid 1823) 895s; run: log: (pid 1822) 895s
run: /etc/sv/lightdm: (pid 1828) 895s; run: log: (pid 1827) 895s
run: /etc/sv/openntpd: (pid 1818) 895s; run: log: (pid 1817) 895s
run: /etc/sv/tor: (pid 1833) 895s; run: log: (pid 1832) 895s

had one service error with acpi-fakekey,

worked around it with :

diff runscript-collection/acpi-fakekey/run /etc/sv/acpi-fakekey/run
10c10
< exec $DAEMON -f
---
> exec /usr/sbin/acpi_fakekeyd -f 

another problem i have since migrating elogind/dbus/lightdm scripts to /etc/sv : /etc/init.d/connman doesn't start anymore during boot.. needs to be restarted after boot. so looking to find/create a runit script for connman..

Thanks for the thorough reply. I'm ok with using the scripts in rcS.d - it works fine that way. I might play around with the more advanced configs later.

I was thinking ahead to the future. Sysvinit scripts are disappearing at an alarming rate, and I worry that they won't all land in the new orphan-sysvinit-scripts package.

[ also looking at the other thread  https://dev1galaxy.org/viewtopic.php?id=3628&p=2 ]
The getty-run package ships with a getty-S0 on serial that is disabled by default. Enabling it is usually enough for other virtualization environment like Qemu or Docker, but I've never run Xen so I don't know.. is the getty on hvc0 a requirement for Xen, or anyway a commonly required feature?
If that is the case I can ship a getty on hvc0 too so that the only thing left to do is to enable it.
Let me know!

I would not claim to be an expert on Xen, but I do believe that it is necessary to get hvc0 working in order to be able to log in when running Paravirtualised

https://wiki.xenproject.org/wiki/Xen_Co … ms#Console

So, your suggestion sounds good to me.

Geoff

xinomilo wrote:

btw, antix did some work on runit : https://www.antixforum.com/forums/topic … lseye-iso/
seems to use antix's own packages, not the debian way of mixing sysvinit/runit..
haven't seen it yet in action, will  be trying the latest iso in the following days :
https://www.antixforum.com/forums/topic … available/

antiX has had runit ISO's available for about a year now. It's blazing fast.

As soon as I have some extra time I'll try to provide scripts for those too, except udevd because I'm not 100% sure that it's safe to do all stage 3 with udev not running

Lorenzo

Update:  I forked live-config to create live-config-runit which sets up console autologin in the live session. The code for that is in /lib/live/config/0190-runit. It works, but I did not replace the live-config init script with runscripts.

Today I tried making runscripts for live-config. It's set up as a one-shot, and it runs, but it does not run early enough. A comment in the init script says it must start before mountkernfs and in my sysvinit system, there is rcS.d/S01live-config which starts before S02mountkernfs. That link is not present in the runit system.

If it really need to run that early it need to be a script in /etc/rcS.d/ so keeping the sysvinit scripts is the most straightforward thing to do.
In case the sysvinit comment is wrong, and it can be run later, like after all the stuff in rcS.d, but before certain services (like gettys and login manager) you have two options:

• ship as a sysv script, but in runlevel 2, and make sure that a runscript with the same name in /etc/sv/ never exists.
     This way it is granted that your script runs before any native runscript (look at the code in stage 2)

• have it as a oneshot runscript -- you need to convert the script into a proper runscript, and then have the gettys and the
     login manager depends on that service. IMHO it doesn't worth the effort to have runscripts for services where there is nothing
     to supervise (no longrun) as you are adding (uneeded?) complexity to achieve the same result as with a plain sysv script.
     Anyway if someone is curious and wants to experiment, in runit, to do a oneshot, have a line in the run file that does
      ' sv one yourservicename'   otherwise your service will keep restarting when it's done which is pointless.
      Also you need to design some kind of readiness protocol, the easy way is to touch a file into run at the very end of your runscript, like
      ' touch /run/myservice.ok', then write the check file to test for the existence of myservice.ok and exit nonzero if it doesn't exists.
      Then make all services that you want to run after yourservice depends on yourservice with a line like
      ' sv start yourservicename  &&  sv check yourservicename  || exit 1 '
      As you see, if it's not for playing, the sysvinit script it's likely the option you want to chose

Hope the above answer your questions, it case it doesn't just ask again
Lorenzo

Are you using runit under SysVinit or are you using runit-init. With the latter you need to do some setting up of getty. When I do that in a VM under Xen, I have to set up a getty on hvc0 for the console.

Geoff

Hi,

[ also looking at the other thread  https://dev1galaxy.org/viewtopic.php?id=3628&p=2 ]
The getty-run package ships with a getty-S0 on serial that is disabled by default. Enabling it is usually enough for other virtualization environment like Qemu or Docker, but I've never run Xen so I don't know.. is the getty on hvc0 a requirement for Xen, or anyway a commonly required feature?
If that is the case I can ship a getty on hvc0 too so that the only thing left to do is to enable it.
Let me know!

Thanks,
Lorenzo

Today I tried making runscripts for live-config. It's set up as a one-shot, and it runs, but it does not run early enough. A comment in the init script says it must start before mountkernfs and in my sysvinit system, there is rcS.d/S01live-config which starts before S02mountkernfs. That link is not present in the runit system.

/etc/runit/1 contains:

/lib/runit/run_sysv_scripts '/etc/rcS.d'

So, /lib/runit/run_sysv_scripts will start the init scripts linked in rcS.d.
If the init script is not executable, then live-config does not run until the desktop comes up, so autologin does not happen, and you get a login screen. I've been making the init scripts non-executable, mainly to make it easier to see which ones are managed by runit when I look in /etc/init.d.

Is there another way in runit to make a script run first? I know a runscript can state what must be started before it, but I haven't seen a way to get to say what it must start before. (everything, in this case).

'update-service --remove live-config && chmod +x /etc/init.d/live-config' set it back to the way it was. Now autologin works again in the live-isos I make.

AntiX has:
bluetooth, connman, ntp, ofono, rpcbind, rsync,
rsyslog, smartmontools, tlp, udevd, ufw

btw, antix did some work on runit : https://www.antixforum.com/forums/topic … lseye-iso/
seems to use antix's own packages, not the debian way of mixing sysvinit/runit..
haven't seen it yet in action, will  be trying the latest iso in the following days :
https://www.antixforum.com/forums/topic … available/

antiX has had runit ISO's available for about a year now. It's blazing fast.

sendkey ctrl-alt-f2 worked. Thanks!

Also forgot to meniton - if you make a new runlevel and decide to change its name, don't change it while you are in that runlevel, and pay attention to the symlinks in /etc/runit/runsvdir. My system was unbootable because of a dead symlink for default that pointed to the old name.

Geoff