Nut upsuser - Dec 2013 - new related project nutdown: https://github.com/arwarw/nutdown

Hello,

I'd like to announce "nutdown", a nut client written using perl
UPS::Nut. 

It's purpose is to enable shutdowns in stages, e.g. "less important
servers shut down at 80% charge, the important ones at 10% and the nut
server at 5%". To that end, nutdown supports "events" like
power_fail,
the charge falling below configurable percentages (i.e. every integer
from 0 to 100) etc. Those events can be assigned as default events to
all hosts, to one host or a group of hosts. Each event may trigger
configurable actions like the execution of a command, a syslog entry or
a Linux SysRq. 

nutdown is still experimental and work in progress. There is a suite of
tests, some documentation, a Debian package (not upstream and not yet
confirming to Debian's policy) and a github repository, but of course
everything could be nicer and shinier. Therefore I hereby ask for
comments and suggestions.




Greetings,

Alexander Wuerstlein.


----
Alexander Wuerstlein         Informatik 4            Univ. of Erlangen
Martensstrasse 1            91058 Erlangen           +49-9131-85-27824
arw at arw.name  arw at cs.fau.de   CDE28BE334E57BBBDA34F007D80C47C8898A5B24
snalwuer at cip.cs.fau.de                      http://www4.cs.fau.de/~arw

On Dec 6, 2013, at 8:21 AM, Alexander Wuerstlein wrote:
> I'd like to announce "nutdown", a nut client written using
perl
> UPS::Nut. 

Thanks for posting this.

One thing that I would consider changing is to treat "ups.status" as a
set (splitting on whitespace, if any), and to not rely on the order of the
status flags.

Actually, splitting ups.status into an array of strings should probably be done
in UPS::Nut, but that module doesn't look like it has been updated in a
while.

-- 
Charles Lepple
clepple at gmail

On 13-12-09 04:40, Charles Lepple <clepple at gmail.com>
wrote:
> On Dec 6, 2013, at 8:21 AM, Alexander Wuerstlein wrote:
> 
> > I'd like to announce "nutdown", a nut client written
using perl
> > UPS::Nut. 
> 
> 
> Thanks for posting this.
> 
> One thing that I would consider changing is to treat "ups.status"
as a
> set (splitting on whitespace, if any), and to not rely on the order of
> the status flags.
Good idea, fixed.



Ciao,

Alexander Wuerstlein.