void-runit VS snooze

It was merged in January but a release wasn't tagged until recently. I doubt anybody had systemd in mind when choosing the paths; the use of *.d names to describe directories that are "assembled" to form a cohesive configuration pre-dates systemd.

That's a neat change in the void-runit package! Unfortunately this not yet in the official runit-void package. The current version there does not have the shutdown.d folder, so currently I also don't see an easy way to handle this.

Did you edit https://github.com/void-linux/void-runit/blob/master/core-services/02-udev.sh with something like like mdevd -O 4 mdevd-coldplug? which initram if any?

By the way zzz is just a shell script. You can find it here: https://github.com/void-linux/void-runit/blob/master/zzz

and here is more bloated void-runit

Maybe this could be related: https://github.com/void-linux/void-runit/pull/81

Void Linux honors the cache file for boot-time imports. The pool holding any root will have already been imported by the initramfs, but other pools will not be imported by the initramfs unless automatic rootfs detection is used.

Runit has run levels. It scrapes the kernel command-line for a level that matches a service directory.

/u/Niki_Roo is right - better to dispense with the sleep and loop by making it a cron job. (or, for a self-contained alternative tailored to Void, snooze)

There are different things you can do, yes either cron jobs or there is something like snooze written and maintained by a void maintainer which fits into the runit/supervision design. I guess you could say its a similiar user expieriece as timer units if you don't want to run cron jobs. You basically create a service with the timing specifications and snooze will wait and then execute into the command when its time to run, then it will just exit and runit will start the service again and it will continue to sleep until the next scheduled run. There are other similar programs like at(1) and all the common cron implementations are available in the repository, void does not come with a default cron daemon, so its completely up to you.

I'll rather use something like snooze to create runit services for each timed job, which integrates well into supervision/runit and I can use runits logging mechanism. I can use sv to send signals to a running job or to the snooze process to immediately start the job with SIGALRM. I will have features like time files, which allow me to do things like "run the job every 5 minutes, after the job finished" or "once a day" while remembering state between reboots.

Which one you choose will depend on what you need. dcron is the simplest implementation, while cronie and fcron both have more advanced features. You may also be interested in checking out snooze.

Basically it boils down to using a process supervisor called runit and a fancy big brother to the unix sleep command called snooze.