3

I use MX Linux, which uses SysV init. Some softwares (like mullvad-vpn in my case) made for SystemD have their daemons not launching on startup. I can launch it with sudo service mullvad-daemon start but I can't find how to have it to be automatically launched on startup. It's possible to launch MX Linux with SystemD and the process does automatically start in that case. The file /etc/rc2.d/K01mullvad-daemon exists, do I have to make any changes to it ? How do I have it to automatically start when using SysV ?

1 Answers1

1

Since it's present in an /etc/rc?.d/ folder, your daemon is already integrated with sysVinit. All you need to do is tell sysVinit to turn it on at that runlevel.

The critical info on why it's doing what you're seeing can be found in /etc/rc2.d/README, at least on my machine:

To disable a service in this runlevel, rename its script in this directory so that the new name begins with a 'K' and a two-digit number, and run 'update-rc.d defaults' to reorder the scripts according to dependencies.

As you can see, your daemon fits in that category. Re-enabling is slightly later in the README:

To re-enable the service, rename the script back to its original name beginning with 'S' and run update-rc.d again.

Orion
  • 131
  • 3