2006/1/11, Kurt Roeckx <[EMAIL PROTECTED]>:
This is due to the initial data enumeration, which is a bit long, and would have been solved during the merge of mge-shut into newhidups (SHUT == Serial HID Ups Transfer, so the same data as in the HID/USB streams).
Anyway, I'll do the necessary on monday.
On Wed, Jan 11, 2006 at 11:11:54AM +0100, Arnaud Quette wrote:
>
> Since the last time it was restarted (when I filed the bug
> > report) it seems to behave a little bit different though, and
> > only goes stale for 2-3 seconds most of them time, but I see some
> > other messages I shouldn't see. Maybe I should raise maxage a
> > little to avoid that it's stale for 2-3 seconds.
> >
> >
> please give more details about the staleness status (is it still there when
> using 2.0.2, or did I get you wrong), and about the "other messages I
> shouldn't see".
I only started using 2.0.2 yesterday, so all the rest is about
2.0.1-3. So far 2.0.2 looks good. It went stale once just after
it was started, but nothing afterwards:
Jan 10 16:39:00 intrepid upsd[1670]: Connected to UPS [myups]: mge-shut-ttyS0
Jan 10 16:39:04 intrepid upsd[1693]: Startup successful
[...]
Jan 10 16:43:54 intrepid upsd[1693]: Data for UPS [myups] is stale - check driver
Jan 10 16:43:57 intrepid upsd[1693]: UPS [myups] data is no longer stale
This is due to the initial data enumeration, which is a bit long, and would have been solved during the merge of mge-shut into newhidups (SHUT == Serial HID Ups Transfer, so the same data as in the HID/USB streams).
Anyway, I'll do the necessary on monday.
We'll see what happens during the next few days/weeks.
feed me back if something happen. Otherwise, I'll close this bug when uploading 2.0.3 debs.
Thanks for your reports,
Arnaud
--
Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/
