Nut upsuser - Feb 2012 - Mac Lion Server as slave

What is the best way to setup a Mac Lion Server as a slave?  A Centos 6
server runs nut and controls the UPS.  The yum epel install has a
nut-client package that has the minimum required to get monitoring working
(upsmon?)...I was wondering if there was some similar configuration for the
Mac?

Thanks,
Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120229/e2e1ec6f/attachment.html>

On Feb 29, 2012, at 10:21 AM, Greg Foreman wrote:
> What is the best way to setup a Mac Lion Server as a slave?  A Centos 6
server runs nut and controls the UPS.  The yum epel install has a nut-client
package that has the minimum required to get monitoring working (upsmon?)...I
was wondering if there was some similar configuration for the Mac?
Since you don't need any drivers, you should be able to download the source
code then run ./configure && make. (NUT will still attempt to detect and
build a lot of stuff you don't need, but if the machine is new enough to run
Lion, it should be quick.)

Creating a launchd plist with the right paths and such has been on my todo list
for some time now. (That project has been stuck since my Mac has an APC UPS that
usbhid-ups can't steal away from the built-in OS UPS monitoring code.)

The plist is probably going to look something like this:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
        <key>Label</key>
        <string>org.networkupstools.upsmon</string>
        <key>OnDemand</key>
        <false/>
        <key>ProgramArguments</key>
        <array>
                <string>/usr/local/ups/bin/upsmon</string>
                <string>-D</string>
        </array>
</dict>
</plist>


-- 
Charles Lepple
clepple at gmail