search for: shutdownups

...ECUTE ups-3-low AT LOWBATT ups-4 EXECUTE ups-4-low AT LOWBATT ups-5 EXECUTE ups-5-low AT LOWBATT ups-6 EXECUTE ups-6-low AT LOWBATT ups-7 EXECUTE ups-7-low Upssched-cmd: echo "upssched-cmd entry was $1" case $1 in ups-1-low) /ws/tools/shutdownUps-1 logger -t upssched-cmd "UPS 1 low battery" ;; ups-2-low) /ws/tools/shutdownUps-2 logger -t upssched-cmd "UPS 2 low battery" ;; ups-3-low) /ws/tools/shutdownUps-3...

...ECUTE ups-3-low AT LOWBATT ups-4 EXECUTE ups-4-low AT LOWBATT ups-5 EXECUTE ups-5-low AT LOWBATT ups-6 EXECUTE ups-6-low AT LOWBATT ups-7 EXECUTE ups-7-low Upssched-cmd: echo "upssched-cmd entry was $1" case $1 in ups-1-low) /ws/tools/shutdownUps-1 logger -t upssched-cmd "UPS 1 low battery" ;; ups-2-low) /ws/tools/shutdownUps-2 logger -t upssched-cmd "UPS 2 low battery" ;; ups-3-low) /ws/tools/shutdownUps-3...

Greetings Gentlebeings, I have started deploying a number of NUT instances on Raspberry Pi machines (Raspbian Jessie) across my network. The purpose of these "nutcases" as we refer to them is to monitor the status of the UPSs supporting our network switching infrastructure and notify us of power and battery events via email. No shutdown or other actions are required. Everything is

...ECUTE ups-3-low AT LOWBATT ups-4 EXECUTE ups-4-low AT LOWBATT ups-5 EXECUTE ups-5-low AT LOWBATT ups-6 EXECUTE ups-6-low AT LOWBATT ups-7 EXECUTE ups-7-low Upssched-cmd: echo "upssched-cmd entry was $1" case $1 in ups-1-low) /ws/tools/shutdownUps-1 logger -t upssched-cmd "UPS 1 low battery" ;; ups-2-low) /ws/tools/shutdownUps-2 logger -t upssched-cmd "UPS 2 low battery" ;; ups-3-low) /ws/tools/shutdownUps-3...

On Mon, 10 Aug 2020, Todd Benivegna wrote: > synoups: https://hastebin.com/xexafofiha.bash Wow! What a mess. It looks as if Synology wanted to write their own "NUT", but decided it would be easier to put their ideas in a script when they saw they could use upssched.conf to call it. NUT intends such a script for timer management. Synology use it for general system management.