Hi Michael,
Michael Biebl writes:
> a/ For a service with sysv + native service, where the service is
> masked, we still run the update-rc.d call but then fail when trying to
> modify the native service:
>
> root@pluto:/etc# systemctl mask kbd.service
> ln -s '/dev/null' '/etc/systemd/system/kbd.
Am 09.08.2013 20:30, schrieb Michael Stapelberg:
> Hi Michael,
>
> Michael Biebl writes:
>> We should probably add test cases for these different use cases, i.e.
>> - SysV-only services
>> - systemd-only services
>> - services with both SysV and native service files
> That would be good, but it’s
Hi Michael,
Michael Biebl writes:
> We should probably add test cases for these different use cases, i.e.
> - SysV-only services
> - systemd-only services
> - services with both SysV and native service files
That would be good, but it’s not a priority for me currently. The test
matrix is simple e
Am 09.08.2013 19:28, schrieb Michael Biebl:
>
> 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|remo
Am 09.08.2013 19:18, schrieb Michael Stapelberg:
> Hi Michael,
>
> Michael Biebl 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@pluto:/etc# ls rc
Hi Michael,
Michael Biebl 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@pluto:/etc# ls rc?.d/???rsyslog
> rc0.d/K04rsyslog rc1.d/K04rsyslog rc2.d/S
Am 08.08.2013 21:36, schrieb Michael Stapelberg:
> AFAICT, there is nothing we need to change. Please correct me if I’m
> wrong.
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.
Hi Michael,
Michael Biebl writes:
> As discussed on IRC: What this patch does, is forward requests for
> LSB-only services to update-rc.d.
Nope, it forwards all requests to update-rc.d :). The log_info line said
otherwise, but I changed that in
http://anonscm.debian.org/gitweb/?p=pkg-systemd/syst
Am 29.07.2013 22:07, schrieb Michael Stapelberg:
> control: tags -1 + pending
>
> Hi Michael,
>
> Michael Biebl writes:
>> Could you rebase the patch on top of the debian-experimental branch?
> Done, and pushed it to debian-experimental directly.
As discussed on IRC: What this patch does, is fo
control: tags -1 + pending
Hi Michael,
Michael Biebl writes:
> Could you rebase the patch on top of the debian-experimental branch?
Done, and pushed it to debian-experimental directly.
--
Best regards,
Michael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subj
Am 19.07.2013 21:34, schrieb Michael Stapelberg:
> control: tag -1 + patch
>
> Hi Michael,
>
> Michael Biebl writes:
Atm systemctl enable|disable does only operate on native .service files.
Michael Stapelberg has prepared patches to forward such enable requests
to update-rc.d for
control: tag -1 + patch
Hi Michael,
Michael Biebl writes:
>>> Atm systemctl enable|disable does only operate on native .service files.
>>> Michael Stapelberg has prepared patches to forward such enable requests
>>> to update-rc.d for SysV services (and vice versa).
Attached the patch to have it
found 709780 44-11
retitle 709780 Make systemctl disable|enable work for SysV init scripts
found
Am 25.05.2013 18:34, schrieb Vincent Bernat:
> ❦ 25 mai 2013 16:25 CEST, Michael Biebl :
>
Yeah, the interface to use for that is
update-rc.d foo disable|enable
> This does not se
❦ 25 mai 2013 16:25 CEST, Michael Biebl :
>>> Yeah, the interface to use for that is
>>> update-rc.d foo disable|enable
>>>
This does not seem to work with systemd.
>>>
>>> Exactly the same command exists for systemd:
>>> systemctl enable|disable foo.service
>>>
>>> That command creates the
Am 25.05.2013 16:18, schrieb Vincent Bernat:
> ❦ 25 mai 2013 15:53 CEST, Michael Biebl :
>
>>> With classis SysV init, we can prevent a daemon to be started on boot
>>> by replacing the symlink from S* to K* in the appropriate
>>> runlevel.
>>
>> Yeah, the interface to use for that is
>> update-
❦ 25 mai 2013 15:53 CEST, Michael Biebl :
>> With classis SysV init, we can prevent a daemon to be started on boot
>> by replacing the symlink from S* to K* in the appropriate
>> runlevel.
>
> Yeah, the interface to use for that is
> update-rc.d foo disable|enable
>
>> This does not seem to work
Package: systemd
Version: 44-11
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi!
With classis SysV init, we can prevent a daemon to be started on boot
by replacing the symlink from S* to K* in the appropriate
runlevel. This does not seem to work with systemd. Therefore, we
17 matches
Mail list logo
