Re: init script, installed but not activated
Hleb Valoshka <email@example.com> writes:
> On 10/6/15, Antonio Terceiro <firstname.lastname@example.org> wrote:
>> for sysvinit you need to code that manually in the initscript. several
>> packages have their initscripts source /etc/default/$package, and check
>> for some variable that says whether the service should start on boot or
> And that's exactly how it's done currently. But systemd fanboys want to
> remove any control variables from defaults and leave there only
> environment variables.
If you do a bit of historical research, you'll find that Debian was trying
to get rid of that pattern as a bad idea before systemd even existed. It
means you have an init script that the init system thinks is enabled but
that actually is disabled, which causes various other subtle problems,
such as not being able to express reliable dependencies.
The problem with sysvinit was historically that there wasn't a simple user
interface to enable and disable scripts in a way that was preserved across
upgrades, but that was added quite some time ago.
Russ Allbery (email@example.com) <http://www.eyrie.org/~eagle/>