[Nut-upsuser] Spurious messages on start

[Arjen de Korte]

>> > I guess the problem is that "Synchronizing..." step.
>> Indeed. Either the driver needs more time to dump all the data than is
>> allowed for in upsd or it could also be that the first connection to the
>> driver always fails. Since we first declare a driver stale before
>> (re)connecting, this will show a similar effect. I have fixed the latter
>> in the trunk (we now try to reconnect first), so you might want to check
>> out if this solves your problem. If not, we probably need to increase
>> the timeout for the synchronization in upsd to see if that fixes this.
> Shouldn't this timeout be configurable via a configuration variable?

That would be a really neat solution. I'll have a look at it, this should
be a relatively easy thing to do. However, I would like to know if this
problem still exists after the latest change to upsd (the fix to try to
(re)connect first before declaring a data stale).

Best regards, Arjen