[systemd-devel] Disabling tomcat8

[Tom H]

On Tue, Dec 19, 2017 at 2:34 PM, Reindl Harald <h.reindl at thelounge.net> wrote:
> Am 19.12.2017 um 20:05 schrieb Lennart Poettering:
>> On Mo, 18.12.17 19:40, Cecil Westerhof (cldwesterhof at gmail.com) wrote:


>>> There is a system with tomcat8 installed and enabled. At the moment it is
>>> not used, so I thought it better to disable it.
>>>
>>> When I enter:
>>>      systemctl disable tomcat8.service
>>>
>>> I get:
>>>      tomcat8.service is not a native service, redirecting to
>>> systemd-sysv-install.
>>>      Executing: /lib/systemd/systemd-sysv-install disable tomcat8
>>
>> This means the service in question is not a native systemd service,
>> but a legacy SysV service, that is only hooked in with distro-specific
>> shell glue. If that doesn't work it's not an upstream issue, you need
>> to contact your downstream distribution for help, as they put together
>> the shell script glue
>
> in 2017 it shpuld be a native systemd-unit but from where comes the "vendor
> preset: enabled" in case of a generated unit?

The usual reason for not having a native unit is that you can't force
developers to do that work. Also, some sysvrc scripts are so
convoluted that the developers prefer to let the generator take care
of business.


> Loaded: loaded (/etc/init.d/tomcat8; generated; vendor preset: enabled)

It's standard for generated units:

root at 1604 ~ # systemctl status apparmor.service
● apparmor.service - LSB: AppArmor initialization
   Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled)
   Active: active (exited) since Wed 2017-12-20 08:27:53 EST; 10min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 274 ExecStart=/etc/init.d/apparmor start (code=exited,
status=0/SUCCESS)

Dec 20 08:07:02 1604 systemd[1]: Starting LSB: AppArmor initialization...
Dec 20 08:07:03 1604 apparmor[274]:  * Starting AppArmor profiles
Dec 20 08:27:53 1604 apparmor[274]:    ...done.
Dec 20 08:27:53 1604 systemd[1]: Started LSB: AppArmor initialization.
root at 1604 ~ #