Hello!
On 9.4 (maybe in previous releases too) it seems that nut.target unit file is missing from the ‘nut-client’ package and when the nut-monitor service is enabled, the following is received and the service won’t be started on boot (however the service starts fine manually):
$ systemctl enable nut-monitor
Created symlink /etc/systemd/system/nut.target.wants/nut-monitor.service → /usr/lib/systemd/system/nut-monitor.service.
Unit /usr/lib/systemd/system/nut-monitor.service is added as a dependency to a non-existent unit nut.target.
The nut.target unit file is provided by the ‘nut’ package which is not (and shouldn’'t be) a dependency of ‘nut-client’ package.
I’ve seen CentOS7 installations to start nut-monitor service although nut.target unit file is missing, but I cannot understand how it works. Maybe older functionality of systemd? Enabling nut-monitor service won’t complain for the non-existent target too.
Any help would be greatly appreciated!