Yeah, I've figured this out already. I thought sysv initscripts are handled by systemd-sysv-generator in 13.2 (as they are in recent Tumbleweed), but there's no such thing in systemd 210. 2015-03-30 14:32 GMT+03:00 Per Jessen <per@computer.org>:
Andrei Dziahel wrote:
Now that's officially weird. Can you file a bug?
What would you expect "systemctl cat apparmor.service" to say? apparmor is a sysvinit service - if I use systemctl cat on e.g. ntpd which is systemd native, I get proper output:
office34:~ # systemctl cat ntpd.service # /usr/lib/systemd/system/ntpd.service [Unit] Description=NTP Server Daemon Documentation=man:ntpd(1) After=nss-lookup.target Conflicts=systemd-timesyncd.service Wants=network.target After=network.target
[Service] Type=forking PIDFile=/var/run/ntp/ntpd.pid ExecStart=/usr/sbin/start-ntpd start RestartSec=11min Restart=always
[Install] WantedBy=multi-user.target
-- Per Jessen, Zürich (10.5°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- Regards, Andrei Dziahel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org