This is working to remove both warnings.
I'm 99% sure the real problem is that upsmon is trying to do things that are
now systemd's job.
You can see the "kill" log even there which suggests upsmon remains derp.
# Trying to fix these warnings:
#nut-monitor.service: Can't open PID file
Christi Scarborough wrote:
> Jun 14 11:29:51 yaga systemd[1]: /lib/systemd/system/nut-monitor.service:6:
> PIDFile= references path below legacy directory /var/run/, updating
> /var/run/nut/upsmon.pid → /run/nut/upsmon.pid; please update the unit file
> accordingly.
> Jun 14 11:32:46 yaga
Package: nut-client
Version: 2.7.4-8
Severity: normal
File: nut
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Installing of nut-client on the host system - I believe the problem is also
present in a full NUT
3 matches
Mail list logo