[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: init script, installed but not activated

On Tue, Oct 6, 2015 at 3:16 PM, Antonio Terceiro <terceiro@debian.org> wrote:
> On Tue, Oct 06, 2015 at 10:47:28PM +0300, Hleb Valoshka wrote:
>> Hi all.
>> I'm packaging web server for ruby called unicorn. The package installs
>> sysv init script, I want to make it installed but not activated
>> because unicorn itself is useless, user should configure it and
>> activate it with "update-rc.d unicorn enable". Or it may installed as
>> dependency for rainbows, so it's clear that it should not run.
>> So I need something like "dh_systemd_enable --no-enable", existing
>> options for dh_installinit like "--no-start" or
>> "--update-rcd-params=..." does not work such way, so we need to
>> introduce workarounds in postinstall script.
>> Any suggestions?
> 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
> not.

I believe that practice is now frowned upon since update-rc.d has a
disable verb.


Reply to: