Displaying 4 results from an estimated 4 matches for "status_buf".
Did you mean:
stat_buf
2023 May 24
1
Synthesize low batt (LB) fron SNMP UPS which does not support this?
...but there is not.
Hopefully, someone with more knowledge than I have can chime in here :)
Cheers
Carsten
[1] Please don't judge me by this, I still use printf and friends a lot
for debugging (sorry for breaking lines, it's just for illustration):
@@ -1113,12 +1116,13 @@
/* write the status_buf into the externally visible dstate storage */
void status_commit(void)
{
+ upsdebugx(2, "%s: Entering (%d)", __func__, ignorelb);
while (ignorelb) {
const char *val, *low;
val = dstate_getinfo("battery.charge");...
2023 May 24
1
Synthesize low batt (LB) fron SNMP UPS which does not support this?
...more knowledge than I have can chime in here :)
>
> Cheers
>
> Carsten
>
> [1] Please don't judge me by this, I still use printf and friends a lot for debugging (sorry for breaking lines, it's just for illustration):
>
> @@ -1113,12 +1116,13 @@
> /* write the status_buf into the externally visible dstate storage */
> void status_commit(void)
> {
> + upsdebugx(2, "%s: Entering (%d)", __func__, ignorelb);
> while (ignorelb) {
> const char *val, *low;
>
> val = dstate_getinfo("battery.c...
2023 May 22
2
Synthesize low batt (LB) fron SNMP UPS which does not support this?
Hmm. Is there maybe something there already that will do this? Maybe kind of back-handed.
In drivers/dstate.c, I see:
In status_init(), if ?driver.flag.ignorelb? is set in the driver state, the ?ignorelb? flag is set.
In status_set(), if ignorelb is set, and the status being set (presumably from the UPS) is LB, it?s ignored. In other words, LB reported by the UPS is ignored.
In status_commit(),
2011 Feb 07
4
[PATCH/RFC v2 0/3] Updates to ACP smart driver
This is 2nd version of the earlier patch featuring a few new features
and fixes to the apcsmart driver, following the remarks in:
http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02294.html
Major changes from v1:
- handle battery.charge and battery.runtime checks at main.c level
- handle "immutable but writable" conflict gracefully at driver level
-