[Nut-upsdev] NUT driver scheduler

[Arnaud Quette]

Hi Roberto,

please keep the list cc'ed has the below things can be interesting to
others...

2006/7/25, Roberto - Engenharia - Microsol <roberto at microsol.com.br>:
>
> Hi Arnaud.
>
> My question was just to know if  had some another suggestion beyond
> creating
> a new file at conf/ dir to store "last test date". Just to listen
> suggestions, no more. ;-)


ok, I wasn't sure.
for the moment, there is no internal mechanism to allow data persistance.
But there is a sub project underway to deal with configuration files
(formalism and accessors, check there:
http://opensource.mgeups.com/projects/nut-config.htm). And part of this is
the variables settings in config files (
https://alioth.debian.org/pm/?group_id=30602).
That answers to 1 point of your need: retrieving a driver parameter at
driver init.
But not yet to the "store this data somewhere"... Though the best place is
to store it in the driver's subjection, ie in ups.conf:
[myups]
...
battsched = ...

For the moment, there are access rights problems that avoid driver to write
in the config files.

@Jonathan: do you have an idea to address this?

About Silvino, I talk with he some times, also he comes to Microsol while it
> was working on nut drivers.
>
> I fixed some problems with solis driver and one new ups was added. I will
> send my path to Silvino, then he will send you. ;-)


thanks for your help to the project, and don't be afraid to post your
patches on upsdev, or on alioth (
https://alioth.debian.org/tracker/?atid=411544&group_id=30602&func=browse)

Lastly, I see a wrong URL at:
http://www.microsol.com.br/software.php

Simply replace http://eu2.networkupstools.org by
http://www.networkupstools.org as it is more generic, and the former doesn't
work anymore, at least for the moment.

Arnaud

All the best,
> Roberto
>
> ----- Original Message -----
> From: Arnaud Quette
> To: Roberto Alcântara ; Silvino B. Magalhaes
> Cc: nut-upsdev at lists.alioth.debian.org
> Sent: Tuesday, July 25, 2006 4:15 PM
> Subject: Re: [Nut-upsdev] NUT driver scheduler
>
>
> 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/
>
>


-- 
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/20060726/faa557b0/attachment.html