Re: [systemd-devel] [PATCH 2/2] systemctl: Don't skip native units when enabling/disabling SysV init.d scripts

2015-05-28 Thread Dimitri John Ledkov
On 28 May 2015 at 12:31, Lennart Poettering lenn...@poettering.net wrote: On Wed, 27.05.15 15:13, Martin Pitt (martin.p...@ubuntu.com) wrote: Hello, if you have both a systemd unit and a SysV init script with the same name, systemctl {en,dis}able currently diverts to chkconfig and friends

Re: [systemd-devel] [PATCH 2/2] systemctl: Don't skip native units when enabling/disabling SysV init.d scripts

2015-05-28 Thread Lennart Poettering
On Wed, 27.05.15 15:13, Martin Pitt (martin.p...@ubuntu.com) wrote: Hello, if you have both a systemd unit and a SysV init script with the same name, systemctl {en,dis}able currently diverts to chkconfig and friends *only*, without actually enabling/disabling the native unit. This is a

[systemd-devel] [PATCH 2/2] systemctl: Don't skip native units when enabling/disabling SysV init.d scripts

2015-05-27 Thread Martin Pitt
Hello, if you have both a systemd unit and a SysV init script with the same name, systemctl {en,dis}able currently diverts to chkconfig and friends *only*, without actually enabling/disabling the native unit. This is a non-issue for Fedora packages which eliminated init.d scripts, but still an