[Nut-upsdev] NUT driver scheduler

[Arnaud Quette]

Hi Roberto,

2006/7/24, Roberto Alcântara <roberto at microsol.com.br>:
>
> Dear nut-upsdev,
>
> I writed one small function to test if batteries was really bad (using
> solis
> driver). Isn't so acurated but it's what we need.
> Just wait 100% batteries charge, turn off input, wait some time (10% from
> previst autonomy) and turn on input again.
> Looking startAutonomy - stopAutonomy we can know the basic batteries
> state.
>
> To scheduler the tests I have one new parameter on driver config file
> (days
> between tests) and to record my last batteries test date I created one
> file
> at conf_path/BATT_SCHED_NAME. It's working fine, but I would like know if
> is
> it the best way to store this value.
>
> The first ideia was use crond jobs but I don't would like use crond, then
> I'm looking for "time to run" inside driver.
>
> Let me know what you think about.


I'm not sure to understand your mail.
Maybe submitting a patch will help.

BTW, I see that you're working for Microsol.
You should get in touch with Silvino B. Magalhães, who has written the solis
and rhino drivers.

Official manufacturer support in an important point for NUT, and the NUT
users. So your help would be welcome...

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/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20060725/3c7669e7/attachment.htm