Nut upsuser - Dec 2017 - Debian 9.3 nut-client.service reports itself as nut-monitor.service

I reported a minor bug in nut 2.7.4 on Debian stretch and got the number 885592 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885592

The systemd service unit /lib/systemd/system/nut-client.service reports itself 
as nut-monitor.service on command systemctl status nut-client.service.

It would be clearer to users if the service unit file was also called

/lib/systemd/service/nut-monitor.service

Roger

On Dec 28, 2017, at 6:35 AM, Roger Price <roger at rogerprice.org>
wrote:
> 
> It would be clearer to users if the service unit file was also called
> 
> /lib/systemd/service/nut-monitor.service
> 
From what I can tell, the "nut-client.service" name comes from this
Debian-specific symlink:

https://sources.debian.org/src/nut/2.7.4-5.1/debian/rules/#L104

On Thu, 28 Dec 2017, Charles Lepple wrote:
> On Dec 28, 2017, at 6:35 AM, Roger Price <roger at rogerprice.org>
wrote:
>> It would be clearer to users if the service unit file was also called
>> /lib/systemd/service/nut-monitor.service
> From what I can tell, the "nut-client.service" name comes from
this Debian-specific symlink:
> https://sources.debian.org/src/nut/2.7.4-5.1/debian/rules/#L104
The comment for the link is

   # Add a symlink to mask the LSB initscript
   ln -s nut-monitor.service
$(CURDIR)/debian/nut-client/lib/systemd/system/nut-client.service

However Debian has now dropped the LSB (See https://lwn.net/Articles/658809/), 
so is the symlink still needed?

Roger