Bug#803373: systemd: fail to enable/disable services that have no LSB init script

[Luca Bruno]

On 29/10/2015 14:05, Martin Pitt wrote:
> Control: tag -1 moreinfo unreproducible
>
> Hello Luca,
>
> Luca Bruno [2015-10-29 12:29 +0100]:
>> I've put a simple service in /lib/systemd/system. Doing systemctl
>> start/stop on this service works correctly, however enable/disable
>> doesn't work: "Failed to execute operation: No such file or directory".
> Did you systemctl daemon-reload after placing the file there? What's
> the exact file name you are adding and which command do you run? Does
> this involve Alias= or templates? Does your file perhaps refer to a
> nonexisting WantedBy= or RequiredBy=?
>
> I tried to reproduce this here:
>
> # cat << EOF > /lib/systemd/system/foo.service
> [Unit]
> Description=test
> [Service]
> Type=oneshot
> ExecStart=/bin/echo hello
> [Install]
> WantedBy=multi-user.target
> EOF
> # systemctl daemon-reload
> # systemctl enable foo.service
> Created symlink from /etc/systemd/system/multi-user.target.wants/foo.service to /lib/systemd/system/foo.service.
>
> So all as expected. I'm afraid we need a more detailled reproducer.
>
>> The reason is that my systemd service has no LSB init script.
> That should be fine. We do call update-rc.d *if* there is an LSB init
> script, but we have plenty of units even in a default install which
> don't have one (e. g. hwclock-save.service).
>
>> By doing a touch /etc/init.d/servicename then enable/disable works,
>> though update-rc.d will spit out some warning.
> Interesting. So somehow your new unit thinks there is a SysV init
> script and tries to call update-rc.d.
>
>> I can see this behaviour only on debian, so pretty sure it must caused
>> by one of the 200+ patches.
> The vast majority of them are actually ones from 215-stable and
> cherry-picked ones from newer upstream versions, it's not actually
> that bad.
>
> Do you have a chance to try this under testing/unstable? The whole
> SysV init script handling got dramatically simplified there.
>
> Thanks,
>
> Martin
>
I installed a new service on a new jessie and didn't happen. I think it
this bug can be closed for now, I guess it must have been something
weird on my side...
Thanks.

Best regards,