[Pkg-systemd-maintainers] Bug#709780: Bug#709780: Bug#709780: Bug#709780: Provide a way to not start a daemon on boot

[Michael Biebl]

Am 09.08.2013 19:18, schrieb Michael Stapelberg:
> Hi Michael,
> 
> Michael Biebl <biebl at debian.org> writes:>
>> Running systemctl enable|disable for a service which has both a native
>> .service file *and* a SysV/LSB init script results in systemctl only
>> acting on the native service.
>>
>> root at pluto:/etc# ls rc?.d/???rsyslog
>> rc0.d/K04rsyslog  rc1.d/K04rsyslog  rc2.d/S01rsyslog  rc3.d/S01rsyslog
>> rc4.d/S01rsyslog  rc5.d/S01rsyslog  rc6.d/K04rsyslog
>>
>> root at pluto:/etc# systemctl disable rsyslog
>> rm '/etc/systemd/system/multi-user.target.wants/rsyslog.service'
>> rm '/etc/systemd/system/syslog.service'
>>
>> root at pluto:/etc# ls rc?.d/???rsyslog
>> rc0.d/K04rsyslog  rc1.d/K04rsyslog  rc2.d/S01rsyslog  rc3.d/S01rsyslog
>> rc4.d/S01rsyslog  rc5.d/S01rsyslog  rc6.d/K04rsyslog
> The issue here is that you are omitting the “.service” suffix. If you
> add that, it will work. I’ll look into fixing this.

Hm, with systemctl disable rsyslog.service, systemctl will no longer act
on the native service file, but only removes the SysV symlinks.
So I don't think it works as expected, yet.

I also noticed, that you are using update-rc.d defaults|remove here, not
update-rc.d enable|disable.
That means, for a service, which has been "disabled", the SysV init
script will be re-enabled after the next package upgrade.

We should consider using update-rc.d enable|disable. Obviously, that
only works, if the symlinks have already been installed via "update-rc.d
defaults"



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20130809/1975da8e/attachment-0002.sig>