zlacker

[return to "Nitro: A tiny but flexible init system and process supervisor"]
1. nine_k+0k[view] [source] 2025-08-22 21:01:36
>>todsac+(OP)
I would like a comparison with runit, which is a very minimal but almost full-fledged init system. I see many similarities: control directories, no declarative dependencies, a similar set of scripts, the same approach to logging. The page mentions runit in passing, and even suggests using the chpst utility from it.

One contrasting feature is parametrized services: several similar processes (like agetty) can be controlled by one service directory; I find it neat.

Another difference is the ability to initiate reboot or shutdown as an action of the same binary (nitroctl).

Also, it's a single binary; runit has several.

◧◩
2. ethers+3b1[view] [source] 2025-08-23 04:08:06
>>nine_k+0k
> no declarative dependencies,

Is that a selling point? Could you explain why?

I've heard plenty of reasons why people find systemd distasteful as an init, but I've not heard much criticism of a declarative design.

◧◩◪
3. petre+qy2[view] [source] 2025-08-23 19:13:19
>>ethers+3b1
> Is that a selling point? Could you explain why?

Because it's stupid easy? I just have to execute shell one liners and set environment variables, no need to read lenghty docs and do stuff the systemd way.

We use runit to supervise our services. It's 100% reliable as opposed to systemd which sometimes fails in mysterious ways.

[go to top]