Reply To: antiX-bullseye-a2-runit_x64-full.iso available

[XecureMember]

Brian Masinick wrote:

If the code is inherited though it’s easier to simply add the user instead of having to modify code from an outside source every time an update occurs; this invites repeated maintenance and code regression potential.

I completely agree. Once a decision is made to fix the future antix-runit releases, I will follow it. For now I am informing on the reason of the problem.

An example of what I am talking about. This is /etc/sv/connman/log/run current content:

#!/bin/sh
set -e

NAME=connman
LOG="/var/log/runit/$NAME"

test -d "$LOG" || mkdir "$LOG" && chown -R _runit-log:adm "$LOG"
exec chpst -u _runit-log svlogd -tt "$LOG"

If no new users are created for future versions, the change without a specific user launching the svlogd program would look like this:

#!/bin/sh
set -e

NAME=connman
LOG="/var/log/runit/$NAME"

test -d "$LOG" || mkdir "$LOG"
exec chpst svlogd -tt "$LOG"

Though this is not needed for all services. Some of them, like elogind, has this log/run instructions:

#!/bin/sh

exec logger -p daemon.notice -t runsv-elogind

It is best we can get some input from the developers, so that the small gui-script I am building can follow the same decision.

Attachments:

1. 

   Runit-service-manager.png
   

antiX Live system enthusiast.
General Live Boot Parameters for antiX.