WinNUT-Client
WinNUT-Client copied to clipboard
gawindx
Request: Ability to run as a service
In order to use this on servers I need to be able to start this automatically and not in the context of an interactive user. I guess this would also mean splitting the GUI-parts from the application.
This will be done, the development of this feature is already underway, the request having already been made and it seems to me to be quite relevant. On the other hand, I have at this moment no idea of the delay of development. We will therefore have to wait until then.
This functionality will come but in the meantime I have reviewed my roadmap and it is not for now, there is still a little work before I can get there. The next big step of the project is to deport the common functions/classes to the GUI and to the service to a DLL so that it is available to each part. Only then, and once resolved any problems that the previous step may cause, I could move on to the development of a service that will manage the communication between the gui / Windows and NUT (or only NUT and windows if the gui is not not executed)
I think the best option would be the complete port of NUT server to Windows that is in Beta here: https://networkupstools.org/download.html
There is not much documentation that comes with it. I finally decided to use AlwaysUp to run WinNUT as a service. The downside is that the UI icon is not present in the notification area, but if I need the interface I can always manually start it while I'm logged in. A free version would be to use Windows Task Manager to start WinNUT at Windows start.
+1 for this functionality - I have a windows host running a VMS which starts as a service, it's protected by a UPS but i very rarely need to log into the machine.
