<div dir="auto"><div>As recently noted in the lists, <span style="font-size:12.8px">this was tracked </span><br style="font-size:12.8px"><span style="font-size:12.8px">down to a Fedora 37 packaging bug: </span><a href="https://bugzilla.redhat.com/show_bug.cgi" style="text-decoration-line:none;color:rgb(66,133,244);font-size:12.8px">https://bugzilla.redhat.com/show_bug.cgi</a><span style="font-size:12.8px">?</span><span style="font-size:12.8px">id=2127269</span><br><br>I did also recently revise build recipes and in particular use of PIDPATH (not superficially suffixed with /nut now). Various precedents were messy and confusing about it :-\</div><div dir="auto"><br></div><div dir="auto">Regarding enabled services - I think you should `systemctl enable nut-server nut-monitor` and possibly `nut-driver@eaton5sx` explicitly. Possibly - because i think this instance should have been enabled by nut-driver-enumerator which registered it.</div><div dir="auto"><br></div><div dir="auto">I did not yet inspect Fedora packaging and how it differs from `make install` so can't quickly suggest more. OTOH would first suspect that new recipe inherits parts of what was used for 2.7.4 and before, which might pull in another direction than new in-project abilities.</div><div dir="auto"><br></div><div dir="auto">Jim<br><br><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Tue, Nov 29, 2022, 13:14 Simon Wilson via Nut-upsuser <<a href="mailto:nut-upsuser@alioth-lists.debian.net">nut-upsuser@alioth-lists.debian.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I've installed nut and nut-client 2.8.0 on my systemd server (had some <br>
fun with the 2.8.0-1.el8 packages not correctly generating /var/run <br>
due to an incorrect /usr/lib/tmpfiles.d entry (nut-common.conf instead <br>
of nut-client.conf and pointing to /var/run/nut/nut) but that's a <br>
story for another day - I worked around that).<br>
<br>
My question is about systemd service files...<br>
<br>
The 2.8.0 service files are different from 2.7.4 - and while I have <br>
read the 2.8.0 documentation I am not clear on which of the various <br>
.service and .target files should be set to autostart.<br>
<br>
Immediately after install systemd had nut like this:<br>
<br>
[root@emp80 ~]# systemctl list-unit-files | grep -i nut<br>
nut-driver-enumerator.path disabled<br>
nut-driver-enumerator.service disabled<br>
nut-driver@.service disabled<br>
nut-monitor.service disabled<br>
nut-server.service disabled<br>
nut-driver.target disabled<br>
nut.target disabled<br>
<br>
In 2.8.0 I have a configured ups.conf. I have not created or edited <br>
any .service or .target unit-files, all are as standard. Editing <br>
ups.conf resulted in nut-driver@eaton5sx.service correctly, and <br>
systemctl start nut-driver@eaton5sx.service runs fine, as does <br>
'upsdrvctl start'.<br>
<br>
Then starting nut-server.service and nut-monitor.service gets me to a <br>
fully operational state. After a reboot, nothing was auto-started, but <br>
manually starting everything (driver, server, monitor) worked - so PID <br>
files/locations are OK.<br>
<br>
I'm now trying to work out what to "enable" for systemd autostart on <br>
boot, and having mixed results.<br>
<br>
I'm setup as follows at the moment, but am not sure if this is correct <br>
for what should be enabled for autostart on reboot as sometimes the <br>
driver does not start and has to be manually triggered into life.<br>
<br>
[root@emp80 ~]# systemctl list-unit-files | grep -i nut<br>
nut-driver-enumerator.path disabled<br>
nut-driver-enumerator.service disabled<br>
nut-driver@.service disabled<br>
nut-monitor.service disabled<br>
nut-server.service disabled<br>
nut-driver.target enabled<br>
nut.target enabled<br>
<br>
What should be set to start with "systemctl enable ...."? Can someone <br>
with a fully working systemd 2.8.0 setup please tell me what they have?<br>
<br>
Thanks<br>
Simon<br>
<br>
<br>
<br>
<br>
<br>
<br>
-- <br>
Simon Wilson<br>
M: 0400 12 11 16<br>
<br>
<br>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net" target="_blank" rel="noreferrer">Nut-upsuser@alioth-lists.debian.net</a><br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
</blockquote></div></div></div>