How to deal with software which thinks that '/etc/rc.d/init.d/' is the init directory?

Lockywolf · 06-15-2018, 11:46 PM

Hello, everyone.

Several pieces of software I installed (most notably, the GoldenFrog's VyprVPN and VMWare) place (some of) their init scripts to /etc/rc.d/init.d/

As far as I know (I grepped the rc.d/* tree.), the only file from there actually used by Slackware is 'functions', which is a library of some service-management functions.

How should I deal with such software? I don't really want to write a separate rc.softwarename for every script placed into init.d .

volkerdi · 06-16-2018, 12:40 AM

You could try making a link to it in /etc/rc.d/rc3.d (make the link name start with 'S').

rkelsen · 06-16-2018, 01:19 AM

It doesn't matter where they go... Any scripts you install under /etc/rc.d will not run automatically. They need to be called from another script, for example: /etc/rc.d/rc.local. So instead of calling /etc/rc.d/rc.somescript, you call /etc/rc.d/init.d/somescript.

The simplest option is to use the SysVinit symlink mentioned above, because you can easily package a symlink and have it removed when you uninstall the package.

Darth Vader · 06-16-2018, 06:47 AM

Quote:

Originally Posted by Lockywolf

How should I deal with such software? I don't really want to write a separate rc.softwarename for every script placed into init.d .

It is simple: do not install such software.