Deprecated/obsolete systemd unit

[awzeak]

Should I override mentioned systemd units to prevent this warnings in the future or this must be handled by DirectAdmin team?

Jun 20 08:49:06 REDACTED systemd[1]: /etc/systemd/system/spamassassin.service:7: PIDFile= references a path below legacy directory /var/run/, updating /var/run/spamd.pid → /run/spamd.pid; please update the unit file accordingly.
Jun 20 08:49:06 REDACTED systemd[1]: /etc/systemd/system/spamassassin.service:9: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
Jun 20 08:49:06 REDACTED systemd[1]: /etc/systemd/system/spamassassin.service:10: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
Jun 20 08:49:06 REDACTED systemd[1]: /etc/systemd/system/nginx.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/nginx.pid → /run/nginx.pid; please update the unit file accordingly.
Jun 20 08:49:06 REDACTED systemd[1]: /etc/systemd/system/[email protected]:6: ListenStream= references a path below legacy directory /var/run/, updating /var/run/directadmin/userd-1000.sock → /run/directadmin/userd-1000.sock; please update the unit file accordingly.
Jun 20 08:49:06 REDACTED systemd[1]: /etc/systemd/system/[email protected]:6: ListenStream= references a path below legacy directory /var/run/, updating /var/run/directadmin/userd-1006.sock → /run/directadmin/userd-1006.sock; please update the unit file accordingly.

 

[Strator]

Go to /etc/systemd/system/spamassassin.service and replace the following:

StandardOutput=syslog
StandardError=syslog

With:

StandardOutput=journal
StandardError=journal

Whether it'll stick I cannot say, but there's a certain logic that, if the file gets overwritten, it eventually gets overwritten by an update with the correct settings.