On 19/11/15 12:43, Marc Haber wrote:
> Will this also work if a package does not come with a sysvinit init
> script
Not in the same way. That's the deb-systemd-invoke code path, which
still respects policy-rc.d, but does not actually use invoke-rc.d to do it.
> or the sysvinit init script is
Hi,
just talking into the wild here.
On Mon, Nov 09, 2015 at 06:07:24PM +0100, Evgeni Golov wrote:
> That said, back to the original topic. I agree with Patrick that we need
> a flexble way to tell "the system" whether we want to start a specific
> service on installation or not. The mentioned
On 19/11/15 11:51, Marc Haber wrote:
> Disclaimer: I do not know whether the new nice systemd world still
> honors invoke-rc.d mechanisms.
It does. There are two code paths:
invoke-rc.d is run by the maintainer scripts of packages with a sysvinit
script (regardless of whether they have a
On Thu, Nov 19, 2015 at 12:35:02PM +, Simon McVittie wrote:
> invoke-rc.d is run by the maintainer scripts of packages with a sysvinit
> script (regardless of whether they have a corresponding systemd unit or
> not), and by various other Debianisms like logrotate hooks. It runs
> policy-rc.d.
4 matches
Mail list logo
