Comment by rahen
12 hours ago
The article and discussion are about runit, why bring systemd into it? Diversity in solutions is a good thing, there’s no need to feel threatened by that.
12 hours ago
The article and discussion are about runit, why bring systemd into it? Diversity in solutions is a good thing, there’s no need to feel threatened by that.
I'm okay with it for comparison's sake.
As a long-time runit user, systemd does far better with sequencing things. With runit you have to have a check executable, and then run 'sv check servicename' in the start script of the service which depends on another.
Least sane systemd hater, try using runit or sysvinit on a production system and come back crying when your runit bash scripts fail all the time
You never addressed GP's point...
This is just a thread about runit, what good is bringing tribal console-war like arguments about systemd to it?
I've had systemd fail/freeze in weird ways very few times. I've had non-systemd init scripts fail zero times.
"My opinions are universal fact and not a skill issue"
2 replies →