[artix-general] question after/post installing (fresh) artix s6 init

[Dudemanguy]

I got a chance to look at those requested scripts.

 >There's a clamav-s6 package providing the clamd "service" for clamav, 
but the freshclam "service" doesn't seem available (providing freshclam 
-d), and it's pretty useful to keep the DB up to date.  Perhaps I can 
write my own freshclamd "service" later.  How to place a bug or request 
for the missing "service"?

This is done and should hopefully work. It seems correct on my machine.

 >As per the cpupower missing "oneshot", not only there's 
cpupower-openrc, arch also offers the cpupower.service, in case you want 
to keep the same services.  On arch the "oneshot" calls a systemd 
script, which in turns set some cpu things up, besides the cpu governor. 
  Maybe you'd like to explore porting it to s6 set of oneshots as well.

I took a closer look at this one and it doesn't seem like it's worth 
providing as a separate script. Basically all it does is parse a config 
file for some variables and then executes a "cpupower frequency-set" and 
"cpupower set" command. This is just a couple of lines in the rc.local 
file mentioned earlier.

 >There's a lm_sensors-s6 package to provide the "oneshot" that 
modprobes the modules found by sensors-detect.  However the sensord 
"service" for monitoring is missing.  Not required at all, but the 
daemon is part of the lm_sensors package.  How to place a bug or request 
for the missing "service"?

Bad news on this one. Sensord (as well as healthd) are forking (i.e. 
bad) daemons with no options to run in the foreground. s6 (as well as 
other process supervision inits like runit) have no way to handle this 
as they expect daemons to run in the foreground (systemd does too 
actually but it has extra code to handle this type). These two can't be 
implemented. You could run a separate sensord command in the 
aforementioned rc.local script to always have it start up on boot, but 
there's no way to supervise it.