Hi Roberto,<br><br>please keep the list cc'ed has the below things can be interesting to others...<br><br><div><span class="gmail_quote">2006/7/25, Roberto - Engenharia - Microsol <<a href="mailto:roberto@microsol.com.br">
roberto@microsol.com.br</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Arnaud.<br><br>My question was just to know if had some another suggestion beyond creating
<br>a new file at conf/ dir to store "last test date". Just to listen<br>suggestions, no more. ;-)</blockquote><div><br>ok, I wasn't sure.<br>for the moment, there is no internal mechanism to allow data persistance.
<br>But there is a sub project underway to deal with configuration files (formalism and accessors, check there: <a href="http://opensource.mgeups.com/projects/nut-config.htm">http://opensource.mgeups.com/projects/nut-config.htm
</a>). And part of this is the variables settings in config files (<a href="https://alioth.debian.org/pm/?group_id=30602">https://alioth.debian.org/pm/?group_id=30602</a>).<br>That answers to 1 point of your need: retrieving a driver parameter at driver init.
<br>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:<br>[myups]<br>...<br>battsched = ...<br><br>For the moment, there are access rights problems that avoid driver to write in the config files.
<br><br>@Jonathan: do you have an idea to address this?<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">About Silvino, I talk with he some times, also he comes to Microsol while it
<br>was working on nut drivers.<br><br>I fixed some problems with solis driver and one new ups was added. I will<br>send my path to Silvino, then he will send you. ;-)</blockquote><div><br>thanks for your help to the project, and don't be afraid to post your patches on upsdev, or on alioth (
<a href="https://alioth.debian.org/tracker/?atid=411544&group_id=30602&func=browse">https://alioth.debian.org/tracker/?atid=411544&group_id=30602&func=browse</a>)<br><br>Lastly, I see a wrong URL at:<br><a href="http://www.microsol.com.br/software.php">
http://www.microsol.com.br/software.php</a><br> <br>Simply replace <font face="Verdana"><small><small><a href="http://eu2.networkupstools.org/">http://eu2.networkupstools.org</a> by <a href="http://www.networkupstools.org">
http://www.networkupstools.org</a> as it is more generic, and the former doesn't work anymore, at least for the moment.<br></small></small></font></div><br>Arnaud<br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
All the best,<br>Roberto<br><br>----- Original Message -----<br>From: Arnaud Quette<br>To: Roberto Alcântara ; Silvino B. Magalhaes<br>Cc: <a href="mailto:nut-upsdev@lists.alioth.debian.org">nut-upsdev@lists.alioth.debian.org
</a><br>Sent: Tuesday, July 25, 2006 4:15 PM<br>Subject: Re: [Nut-upsdev] NUT driver scheduler<br><br><br>Hi Roberto,<br><br><br>2006/7/24, Roberto Alcântara <<a href="mailto:roberto@microsol.com.br">roberto@microsol.com.br
</a>>:<br>Dear nut-upsdev,<br><br>I writed one small function to test if batteries was really bad (using solis<br>driver). Isn't so acurated but it's what we need.<br>Just wait 100% batteries charge, turn off input, wait some time (10% from
<br>previst autonomy) and turn on input again.<br>Looking startAutonomy - stopAutonomy we can know the basic batteries state.<br><br>To scheduler the tests I have one new parameter on driver config file (days<br>between tests) and to record my last batteries test date I created one file
<br>at conf_path/BATT_SCHED_NAME. It's working fine, but I would like know if is<br>it the best way to store this value.<br><br>The first ideia was use crond jobs but I don't would like use crond, then<br>I'm looking for "time to run" inside driver.
<br><br>Let me know what you think about.<br><br>I'm not sure to understand your mail.<br><br>Maybe submitting a patch will help.<br><br><br>BTW, I see that you're working for Microsol.<br>You should get in touch with Silvino B. Magalhães, who has written the solis
<br>and rhino drivers.<br><br>Official manufacturer support in an important point for NUT, and the NUT<br>users. So your help would be welcome...<br><br>Arnaud<br>--<br>Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt<br>
Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/">http://www.networkupstools.org/</a><br>Debian Developer - <a href="http://people.debian.org/~aquette/">http://people.debian.org/~aquette/</a>
<br>OpenSource Developer - <a href="http://arnaud.quette.free.fr/">http://arnaud.quette.free.fr/</a><br><br></blockquote></div><br><br clear="all"><br>-- <br>Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt<br>Network UPS Tools (NUT) Project Leader -
<a href="http://www.networkupstools.org/">http://www.networkupstools.org/</a><br>Debian Developer - <a href="http://people.debian.org/~aquette/">http://people.debian.org/~aquette/</a><br>OpenSource Developer - <a href="http://arnaud.quette.free.fr/">
http://arnaud.quette.free.fr/</a>