Smarter/Quieter/Indefinite Reconnection attempts

[gbakeman]

It would be useful if WinNUT could attempt to reconnect to the NUT server indefinitely. This would mean that it is quieter about the reconnection attempts. If the tools are available, then it may also be useful if WinNUT can first detect if it's even possible to make a connection first (network adapter is up & route to the NUT server is available), otherwise wait until the conditions are present.

Ref #63
@f33d13ack

[SSPW]

Indefinite is a must.
Maybe a checkbox in setting if your want the noisy poppups.

[s0uls]

Hello.

My nas is the UPS master and it auto powers off during night until 9 am to preserver HDD lifespam.
My Desktop PC using win nut client will time out and not reconnect automatically when the UPS is back at 9 am.
Would it be posible to add a connection schedule or a manual time out override ?

[gbakeman]

Hello.

My nas is the UPS master and it auto powers off during night until 9 am to preserver HDD lifespam. My Desktop PC using win nut client will time out and not reconnect automatically when the UPS is back at 9 am. Would it be posible to add a connection schedule or a manual time out override ?

I'm definitely thinking that, at minimum, we have an option (by default) where WinNUT will just indefinitely attempt to make a re-connection to the NUT server if it was previously connected successfully (connection lost event) without any kind of notification. The last item in the log would be a notification that ongoing connection attempts are occurring. How important is scheduling to you? Perhaps we can just do a simple ping instead if you want lower overhead.

[s0uls]

Hello.
My nas is the UPS master and it auto powers off during night until 9 am to preserver HDD lifespam. My Desktop PC using win nut client will time out and not reconnect automatically when the UPS is back at 9 am. Would it be posible to add a connection schedule or a manual time out override ?

I'm definitely thinking that, at minimum, we have an option (by default) where WinNUT will just indefinitely attempt to make a re-connection to the NUT server if it was previously connected successfully (connection lost event) without any kind of notification. The last item in the log would be a notification that ongoing connection attempts are occurring. How important is scheduling to you? Perhaps we can just do a simple ping instead if you want lower overhead.

No, schedules are not a must, but as you said indefinitely attempts would bee great.

[bernatcg]

In my opinion this kind of software should be always connected, and if there is no connection for any reason, keep reconnecting all the time. Maybe the time between tries should be dynamic rather than a fixed interval, but it should be able to reconnect no matter what. This kind of software should be designed to work unattended to work as expected.

[yoyoma2]

I vote for the Quieter part of this issue. My WinNUT client connects to a rpi which hosts the UPS. While the rpi is performing backups (about 1 hr) most services are stopped including NUT services. I have to exit WinNUT before the rpi backup and restart WinNUT after the rpi backup is done and NUT services are available again.

It would be great if a single "Not Connected" and a single "Connected" notification appeared an hour later.