[Nut-upsdev] bestfortress driver establishes/loses/establishes communication and so on...

[Arnaud Quette]

Hi Stuart,

2012/1/25 Stuart D Gathman <stuart at bmsi.com>:
> Long ago, Nostradamus foresaw that on 01/24/2012 03:25 AM, Arnaud Quette
> would write:
>>
>> Use the following procedure to do so:
>
> $ svn co svn://anonscm.debian.org/nut/trunk
> $ cd trunk
> $ ./autogen.sh
> $ ./configure --sysconfdir=/etc/nut --with-statepath=/var/run/nut
> --with-altpidpath=/var/run/nut --with-drvpath=/lib/nut
> --with-pidpath=/var/run/nut --datadir=/usr/share/nut
> --with-pkgconfig-dir=/usr/lib/pkgconfig --with-user=nut
> --with-group=nut
> $ make
> $ sudo ./drivers/bestfortress -a fortress -DDDDD

thanks for the log.
sadly, I don't see any "checksum corruption" in this 76 seconds run.
can you please let the driver run a bit more, so that I can see some
of these, and get an idea of the frequency and corruption level (if
any)?

note that if you already have a patch underhand, I'd happy to look at it.

cheers,
Arnaud
-- 
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/