systemd obsolete / legacy warnigns

[Bussmann, Lars Hendrik, NMD-I2.1]

Hi,

we start testing with SP3 and we noticed some systemd obsolete / legacy warnings.

Apr  6 17:21:43 sles15sp3ucs systemd[1]: /usr/lib/systemd/system/grub2-once.service:13: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
Apr  6 18:13:17 sles15sp3ucs systemd[1]: /usr/lib/systemd/system/mcelog.service:11: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
Apr  6 18:13:17 sles15sp3ucs systemd[1]: /usr/lib/systemd/system/chronyd.service:14: PIDFile= references a path below legacy directory /var/run/, updating /var/run/chronyd.pid → /run/chronyd.pid; please update the unit file accordingly.
Apr  6 18:16:55 sles15sp3vm systemd[1]: /usr/lib/systemd/system/vmtoolsd.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/vmtoolsd.pid → /run/vmtoolsd.pid; please update the unit file accordingly.


I created one bug for chrony ( #1184400 ) but I am unsure if this is the right approach as it looks like an general issue.

When I search through all units of the basesystem and Server-Applications packages if found over 30 further units with the old syntax.
e.g.
/usr/lib/systemd/system/ipmievd.service
/usr/lib/systemd/system/nfs-blkmap.service
/usr/lib/systemd/system/rpc-statd.service
/usr/lib/systemd/system/fancontrol.service
/usr/lib/systemd/system/sssd.service


Maybe there is an build option for systemd or it is possible create an "affects multiple packages" bug?





Kind Regards,
Lars