Rainer Weikusat via Dng said on Wed, 16 Jul 2025 12:05:15 +0100

>Steve Litt <slitt@???> writes:
>> Rainer Weikusat via Dng said on Tue, 08 Jul 2025 16:30:16 +0100
>>
>>>init.d scripts are config file and as such, supposed to be under user
>>>control. This includes that a user may remove them.
>>
>> Or put exit 0 at the very top.
>
>I used to do that in the past but some woman working for the Mainz
>university computing center convince me of the other method. Her
>arguments where:
>

>    - this render starting the serice manually via init.d script
>          impossible

>

>    - such changes are easily forgotten and possibly, cause a lot
>    of
>          headscratching because of this while the renamed script is
>          visible in the filesystem without having to look at its
>          content

She definitely has a point, and her point reminds me why I'm so glad to
have migrated away from sysvinit. In runit you just put a file called
"down" (without the quotes) in your run directory. You can start it
manually with runsv, and the down file makes what happened obvious.

I'd like to point out, at this juncture, that it's pretty easy to
slowly start switching from sysvinit daemon management to runit deamon
supervision, one daemon at a time. Runit's run scripts change so slowly
that you can just hard code them and leave them.


SteveT

Steve Litt

http://444domains.com