nut - impossible to configure/customise

[zyghom]

hi,

I started using UPS and enabled the plugin on Opnsense
I am able to configure it to my needs (/usr/local/etc/nut/...) but the changes in any file don't survire neither reboot nor even disable/enable the Service

example is:

Code Select Expand

POWERDOWNFLAG /etc/killpower
- with this statement Opnsense sends signal to UPS to turn it off - that behaviour migth not be desired
the config files are taken from templates that are here:
/usr/local/opnsense/service/templates/OPNsense/Nut/
but modifying these files does not help as per description:

Code Select Expand

cat /usr/local/opnsense/service/templates/OPNsense/Nut/upsmon.conf
# Please don't modify this file as your changes might be overwritten with
# the next update.

is there any mean to change this behaviour?
as a workaround I added a script that runs on restart and it changes the conf file but that is dirty solution

thank you

[Patrick M. Hausen]

Why don't you use the UI? Services > NUT

That's the point of plugins, you know  ;)

[zyghom]

thank you Patrick
but the GUI for the pluging is very limitted with the configuration

[Patrick M. Hausen]

What's missing? Maybe a pull-request can be created easily?

[zyghom]

hi Patrick,

I spent some time and described everything last month here:

https://github.com/opnsense/plugins/issues/3855

[lilsense]

I agree, The nut GUI should look identical to TrueNAS Core GUI. Hence, I use the TrueNAS nut as oppose to OPNsense.

[zyghom]

right, to go further I use even another machine where my UPS is connected to, that works as nut server
all other machines work as clients
but even client (each client) requires some customisation
and on TrueNAS the customisation option is a bit higher than on OPNsense
good example is: if one of the clients is a Proxmox machine, I will give this machine much more time to shutdown than the other machine that is pure firewall or so

[Redcoat]

hi Patrick,

I spent some time and described everything last month here:

https://github.com/opnsense/plugins/issues/3855

I agree with your conclusions.  I reluctantly reverted to pfSense when I failed to be able configure the shutdown of my two TrueNAS boxes.  You went much further than I in attempting to find a remedy.  I enjoyed and appreciated your report in the other thread.  I thought it was "just me" and one more aspect of what seems to me to be the relative "opacity" of OPNsense over pfSense.

[franco]

Ideas:

* Submit improvements to the code.
* Submit feature requests to the issue tracker.
* Use the NUT package without the GUI for full customization.


Cheers,
Franco

[zyghom]

Ideas:

* Submit improvements to the code.
* Submit feature requests to the issue tracker.
* Use the NUT package without the GUI for full customization.


Cheers,
Franco

I went for point 3 only because I have no idea how to contribute to the code
I tried expressing myself in the point 2 but I am not sure I did it properly

[franco]

Ok, you have to consider that everything eventually is suboptimal and a lot of people use the current state just fine nevertheless. So you need to account for taking those people on the journey which can only lead to structured feature requests (option 2) or a rewrite (option 4 I guess).

I don't see another option except these 4 for NUT on OPNsense.


Cheers,
Franco