[Nut-upsuser] "Communications lost" temporarily at every startup

[Paul Mogren]

I did not have any success with adding a delay between
startup of driver and server.

Yes, I am using openSUSE 10.2. Thanks for the RPM
offer. I'll take you up on it; you can send it to this
email address if you like, or send me a link, whatever
works. Latest stable version would be good.

This leaves me wondering why, since you are a NUT
maintainer and you already have the ability to build a
SUSE RPM, that facility is not included among the
packaging options in the NUT source tarball, and the
link for SUSE RPM's on the NUT homepage is broken.
That way, people in my situation could get updates in
the future. It would probably also speed official
adoption of the new version by SUSE maintainers. Are
you aware of the SUSE build service?


--- Arjen de Korte <nut+users at de-korte.org> wrote:

> Paul Mogren wrote:
> 
> > Sorry, I forgot to CC the list.
> > 
> > --- Paul Mogren <fkamogee at yahoo.com> wrote:
> > 
> >>> Which version of NUT is this? This shouldn't
> >> happen
> >>> anymore with nut-2.2.0.
> >> I'm using a SUSE-managed package which is based
> on
> >> nut-2.0.4. I didn't find a 2.2 RPM for SUSE, so I
> >> guess I'd have to compile from source.
> 
> Since you're using nut-2.0.4, I assume you have
> openSUSE 10.2 installed,
> right? In that case, I keep packaged RPM versions
> handy. Just drop me a
> line if you need one (the latest stable and/or
> development versions).
> 
> >> Is there any workaround for 2.0.4?
> 
> You might add a delay between the startup of the
> driver and the server,
> but this is not recommended. Since openSUSE uses
> RPM, changes to the
> startup script won't stick between updates. Note
> that this a temporary
> and cosmetic thing only. NUT functions normally. If
> you really want to
> get of this, upgrade.
> 
> Best regards, Arjen
>