Le 17/10/20 à 19:05, David Engel a écrit :
On Sat, Oct 17, 2020 at 10:42:30AM +0200, Laurent Bigonville wrote:
This is quite weird, the package already contains a systemd tmpfiles snippet
(/usr/lib/tmpfiles.d/nut-client.conf) that should create the directory
during the boot.
I see the /usr/lib/tmpfiles.d/nut-client.conf now. It's been nearly 5
months since I filed that report so I don't remember any of the
details. It's quite possible, though, that I ran into the problem
right after installing the nut-client package without rebooting. If
that tmpfiles.d file doesn't create the directory until the next boot,
that could explain the problem.
Thanks for the reply, it's really weird, the /run/nut directory should
created on installation (I just tried that in a chroot and the directory
is properly created) and then recreated on reboot as well as /run is
supposed to be on tmpfs
Could you please give me the output of "systemctl list-dependencies
nut-monitor.service"
Here is that output:
From the output, the systemd-tmpfiles-setup.service service is called
before nut-client, so looks like the ordering is OK
Did you try to uninstall the nut-server package and see if everything is
still working? Is /var/run a symlink to /run on your system?
