[Nut-upsuser] NUT service files on systemd

[Andre Mueller]

Hello

I had installed nut 2.8.0-4 debian packages "manually" on my ubuntu 
system. After reworking paths (with confs and symlinks) from a previous 
source make installation of nut 2.8.0-3 I was able to run the default 
packages within systemctl also after reboots (taking all confs from 
/etc/nut/).

nut-driver-enumerator.path                 enabled         enabled
nut-client.service                         alias           -
nut-driver-enumerator.service              enabled         enabled
nut-driver at .service                        indirect        enabled
nut-monitor.service                        enabled         enabled
nut-server.service                         enabled         enabled
nut-driver.target                          enabled         enabled
nut.target                                 enabled         enabled

best,

André


Am 30.11.2022 um 11:44 schrieb Simon Wilson via Nut-upsuser:
> This is what I am running with at the moment:
> 
> [root at emp80 ups]# systemctl list-unit-files | grep -i nut
> nut-driver-enumerator.path                                             
> enabled
> nut-driver-enumerator.service                                          
> enabled
> nut-driver at .service                                                    
> indirect
> nut-monitor.service                                                    
> disabled
> nut-server.service                                                     
> disabled
> nut-driver.target                                                      
> disabled
> nut.target                                                             
> enabled
> 
> nut-driver-enumerator.path enabled (and running) monitors for edits to 
> ups.conf, and flows changes into a driver restart. I can see this happen 
> if I edit ups.conf: the driver restarts.
> 
> The companion nut-driver-enumerator.service is a one-shot run service, 
> is also enabled to run at boot - this appears to run on EITHER when 
> triggered by nut-driver-enumerator.path OR on reboot (enabled), and I 
> believe generates the required nut-driver at eaton5sx.service.
> 
> nut.target enabled should then start nut-driver.target, nut-server and 
> nut-monitor (all are set to "wants" in the unit file).
> 
> At least, that is how I am reading it - if anyone else has other 
> pointers please let me know! :-)
> 
> Will see what happens over multiple reboots!
> 
> 

-- 

Andre Mueller
Leuengasse 26 | CH-4057 Basel | Switzerland
Tel +41-44-350 76 11
mailto:andre.mueller at himmel-blau.com
https://www.himmel-blau.com