[Nut-upsuser] Spurious messages on start

Pedro Côrte-Real pedro at pedrocr.net
Mon Nov 13 01:44:31 CET 2006

On 11/12/06, Peter Selinger <selinger at mathstat.dal.ca> wrote:
> Try an analogous setting for DEADTIME in upsmon.conf.

This has no effect either.

> The connection works like this:
>  upsmon <---> upsd <---> driver.
> So which timeout you should increase depends on whether the connection
> was lost between upsmon and upsd, or between upsd and the driver.

The connection isn't being lost per se. It's just when starting up or
restarting that nut goes through "communications lost -> ups
unavailable -> communications established". Probably happens when
starting up the driver (newhidups). Any ideas what it might be?


More information about the Nut-upsuser mailing list