Andrei Borzenkov wrote:
On 23.04.2023 18:48, Per Jessen wrote:
Another small surprise - unable to restart syslog.
I do not even have syslog.service here. So you probably need to elaborate what "restarting syslog" means.
Hehe, okay :-) With syslog-ng installed: systemctl restart syslog (syslog.service is a symlink to syslog-ng.service)
"Unit var-run.mount" not found. It does in fact not exist. On a 2nd TW system, that unit seems to have been provided by systemd-sysvcompat.
/var/run is symlink to /run since I do not remember how long.
Yeah, I see that too, e.g. on Leap15.2. Looking at the var-run.mount unit, it is a bind mount, but conditional on the mount point not being a symlink .....
If there is still some unit that depends on /var/run being mount point, it probably should be considered a bug in this unit.
This is what it looks like: office24:/etc/postfix # systemctl cat syslog-ng # /usr/lib/systemd/system/syslog-ng.service [Unit] Description=System Logging Service Requires=var-run.mount # Requires=syslog.socket After=var-run.mount network.target Conflicts=rsyslog.service syslogd.service Looking at package systemd-sysvcompat, there doesn't seem to be anything I need and I can live without the "var-run.mount" unit. -- Per Jessen, Zürich (15.2°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes