The expected behavior is fine :)
I updated again becouse with 2.6.4 i found a bug about upssched so now with
2.6.5 all is working great.
Thank you again. Happy to use NUT.
From: Arnaud Quette
Sent: Friday, September 07, 2012 5:15 PM
To: Fabio Cecamore
Cc: [email protected]
Subject: Re: [Nut-upsuser] Communications with UPS lost: No status from UPS
2012/9/6 Fabio Cecamore <[email protected]>
Updated to the last (in the testing debian repository) available: 2.6.4
This time using blazer_ser in debug i find:
363.373978 read: '(233.9 140.0 233.9 006 49.8 13.7 30.7 00001001'
365.162745 send: 'Q1'
366.163904 read: timeout
366.163991 blazer_status: short reply
366.164013 Communications with UPS lost: status read failed!
367.163804 send: 'Q1'
367.378009 read: '(234.3 140.0 234.3 006 49.4 13.7 30.7 00001001'
But this time in syslogd.log no error.. i’ll check more and will let you
know.
so the expected behavior is fine? (to be confirmed)
(nice to see an other android user)
they are everywhere ;)
cheers,
Arnaud
_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
