Comment by imiric

Comment by imiric 20 hours ago

I've gotten used to runit via Void Linux, and while it does the job of an init system, its UI and documentation leave something to be desired. The way logging is configured in particular was an exercise in frustration the last time I tried to set it up for a service.

I wouldn't mind trying something else that is as simple, but has sane defaults, better documentation, and a more intuitive UI.

kccqzy 14 hours ago

I like using systemd but it also doesn't have great documentation either. I often find myself unable to grok things by only reading the official documentation and I have to resort to reading forum posts, other people's blogposts or Stack Overflow. To me documentation isn't good enough until it doesn't need any third party material.

Reply View 0 replies

nine_k 20 hours ago

Logging in runit seems simple (I don't remember running into problems), but indeed, the documentation leaves much to be desired. Could be a good thing to contribute to Void Handbook.

Reply View 0 replies

cbzbc 19 hours ago

runit doesn't always take care of services it manages in the same way as a proper init . From the man page:

"If runsvdir receives a TERM signal, it exits with 0 immediately"

Reply View 1 reply

Arch-TK 17 hours ago

This is by design.
runsvdir receiving TERM should only happen when stage 2 is triggered to end.
Once that happens, the individual runsv processes are still supervising their individual tasks and can be requested to stop through their respective control sockets. It's how standard stage 3 is implemented.

Reply View | 0 replies