Systemd service files

[Ralf Mardorf]

On Fri, 15 Sep 2017 10:48:18 -0400, J Doe wrote:
>When adding commonly used packages (Apache 2.4.x), I noticed that some
>of these packages have incomplete systemd service files.  In the case
>of Apache there is a systemd stub that then calls an init.d shim
>script.  As a result, on reboot, systemd shows a load failure (I am
>assuming from the incomplete service file), for Apache, but Apache is
>successfully started.  Controlling Apace post-boot is possible using
>the legacy apachectl command.

Hi,

those packages unlikely contain incomplete "systemd service files". Much
likely those packages contain plain init scripts and
systemd-sysv-generator generates systemd units. I guess with "systemd
service files" you mean "systemd units".

>-- Is the fact that not all packages
>have systemd service files due to the fact that 16.04 LTS is the first
>version of server to have systemd and systemd service files are slowly
>being added ?

No, 16.04 is not the first release using systemd by default.

https://wiki.ubuntu.com/SystemdForUpstartUsers

>-- Is there a rough timeline as to when most major pacakages will have
>systemd service files (ie: 18.04 LTS, etc.) ?

Ubuntu's hybrid approach is disgusting, however, init scripts usually
work, too.

http://manpages.ubuntu.com/manpages/xenial/man8/systemd-sysv-generator.8.html

Apart from this there's also
https://packages.ubuntu.com/xenial/amd64/systemd-sysv/filelist ,
something I'm using even on a clean systemd distro without
systemd-sysv-generator.

Instead of guessing consider to take a look at log files and at least
consider to post the load failure systemd does show. It might be my
broken English, but I even don't understand what fails to load, if
seemingly everything starts as expected.

Regards,
Ralf