search for: batterylevel

Hi, are this UPS supported by any other driver than "richcomm_usb". The device works with richcomm_usb, but only signals online, offline etc. Not voltage, batterylevels etc. Bus 006 Device 009: ID 0925:1234 Lakeview Research Bus 006 Device 009: ID 0925:1234 Lakeview Research Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass...

Is it possible to shutdown earlier by certain conditions: by battery level and estimated by UPS runtime. In APCUPSD this done by config options "BATTERYLEVEL" "MINUTES". By what condition NUT shutdown server? How to disable UPS shutdown?

...wer failure is detected. However, the # onbattery argument is passed to apccontrol only after the # ONBATTERYDELAY time. If you don't want to be annoyed by short # powerfailures, make sure that apccontrol powerout does nothing # i.e. comment out the wall. ONBATTERYDELAY 6 # # Note: BATTERYLEVEL, MINUTES, and TIMEOUT work in conjunction, so # the first that occurs will cause the initation of a shutdown. # # If during a power failure, the remaining battery percentage # (as reported by the UPS) is below or equal to BATTERYLEVEL, # apcupsd will initiate a system shutdown. BATTERYLEVEL 5 #...

We have about 4 servers connected to an APC UPS. The UPS only has one UPS connection. So my question is, in a power outage how do i get all my servers to safely shutdown? Do i run a USB hub? Do i write a script on the one machine connected to turn off all the other machines? I'm confused. Jamie

Anyone else around using apcupsd? I seem to be seeing a problem, and I'd like someone to check me on it: I edit /etc/apcupsd/apccontrol to replace the value of SHUTDOWN from /sbin/shutdown to /bin/false (we don't want 3 or 6 servers shutting down over a 2 second or so blip, which it really wants to do). What's happened is that a machine shut down the other day, and looking at it, I

...As nothing happened, i did set the first value for battery-threshold to 90%, (while the batt was below) and that then did immediately react with hiberate. My preferred setting would be to wait after powerfailure for 1 minute, then hibernate. Without taking other values into account like batterylevel or batteryruntime? Any help or information on that would be appreciated. Thanks Eddie _______________________________________________ Nut-upsuser mailing list Nut-upsuser at alioth-lists.debian.net <mailto:Nut-upsuser at alioth-lists.debian.net> https://alioth-lists.debian.net/cgi-...

...ins/nut/nut.cfg: line 10: PORT: command not found /boot/config/plugins/nut/nut.cfg: line 11: MODE: command not found /boot/config/plugins/nut/nut.cfg: line 12: IPADDR: command not found /boot/config/plugins/nut/nut.cfg: line 13: SHUTDOWN: command not found /boot/config/plugins/nut/nut.cfg: line 14: BATTERYLEVEL: command not found /boot/config/plugins/nut/nut.cfg: line 15: SECONDS: command not found /boot/config/plugins/nut/nut.cfg: line 16: TIMEOUT: command not found /boot/config/plugins/nut/nut.cfg: line 17: UPSKILL: command not found /boot/config/plugins/nut/nut.cfg: line 18: POLL: command not found /bo...

...did set the first value for battery-threshold to > 90%, (while the batt was below) and that then did immediately react with > hiberate. > > > > My preferred setting would be to wait after powerfailure for 1 minute, > then hibernate. Without taking other values into account like batterylevel > or batteryruntime? > > > > Any help or information on that would be appreciated. > > > > Thanks > > Eddie > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at alioth-lists.debian.net > https://alioth-lists....

...As nothing happened, i did set the first value for battery-threshold to 90%, (while the batt was below) and that then did immediately react with hiberate. My preferred setting would be to wait after powerfailure for 1 minute, then hibernate. Without taking other values into account like batterylevel or batteryruntime. Any help or information on that would be appreciated. Thanks Eddie -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20240105/d48c5ded/attachment-0001.htm> ------------...

This patch introduces a handful of new options, I mentioned earlier in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02088.html See the large commit message in the follow-up for the details and rationale. I realize it's a bit larger diff - so if it's required I can split it into few smaller ones. Michal Soltys (1): APC smart driver update and new features.