Hi all, On 5/19/23 15:11, Greg Troxel wrote:
LB is baked in to nut behavior. So if a UPS doesn't report LB, then it makes sense to synthesize it. Synthetic LB is the cleanest fix at the earlier processing point.
I fully agree and thus this ought to be done in/near uspd IMHO. I glanced over the server/ directory and was not sure where even to begin hooking this in. Should this be directly in upsd (upsd.c) or rather in/near the driver level (driver/main.c)?
Yes, this could be in upsmon, but that's not synthetic LB, it's choosing to shutdown if battery is below X.
Yeah, this should be independent and fully on the client side (and thus upsmon) where each client can choose how to react to a UPS on battery.
We should be clear on "critical" vs "LB" and clean up the language to be consistent.
For upsmon, I would stay with critical as this is already mentioned in upsmon(8) and I guess "LB" could stay for the server part as each user could decide whether she wants to rely on LB from the UPS itself or on the self-defined override.
Beware that I'm a bit fuzzy on details beyond my comments and even some on things I commented on, so take them as such.
Same here, quite at a loss what is handled where on the server and always low on time due to other projects/tasks.
Cheers and any pointers appreciated! Carsten -- Dr. Carsten Aulbert, Max Planck Institute for Gravitational Physics, Callinstraße 38, 30167 Hannover, Germany, Phone +49 511 762 17185
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
