[Nut-upsuser] Spurious messages on start

[Peter Selinger]

I can only guess. Perhaps you are starting the components in the wrong
order? You have to start:

First the driver (upsdrvctl).
Second upsd.
Third upsmon. 

-- Peter

=?ISO-8859-1?Q?Pedro_C=F4rte-Real?= wrote:
> 
> 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?
> 
> Pedro.
>