On Feb 4, 2014, at 9:05 AM, Chris Duffy wrote: > ugen1.3: <USB UPS PPC> at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON [...] > idVendor = 0x06da > idProduct = 0x0005
This VID:PID combination should be handled by blazer_usb. In NUT 2.7.1 and later, this would be covered by nutdrv_qx as well. > I am running all the ups programs as root, i.e. "ps -aux" shows: > > root 39901 0.0 0.0 22388 3860 ?? Is 12:57AM 0:00.00 > /usr/local/bin/upslog -s UPSonic@localhost -l /var/log/ups.log -i 300 > -u root > root 39976 0.0 0.0 22392 3804 ?? Is 12:57AM 0:00.00 > /usr/local/sbin/upsmon -u root localhost > root 39978 0.0 0.0 22392 3900 ?? S 12:57AM 0:00.01 > /usr/local/sbin/upsmon -u root localhost The key program to run with "-u root" is the driver. When I mentioned logs, I was thinking syslog (/var/log/messages, probably). I hadn't considered upslog, but apparently the *BSD ports tree starts a copy by default. For instance: /usr/local/libexec/nut/blazer_usb -a UPSonic -u root -D > The /var/log/ups.log does not have much in it either that > makes sense....maybe I need a utility to decode it? > Sample lines from the is file are: > > 20140131 103652 NA NA NA [NA] NA NA upslog basically condenses the output of upsc into one line per polling interval, but this falls apart if the driver hasn't started. (The error message from upsc is more descriptive, since it isn't trying to force it into a bunch of columns). Once the driver is running, you will see numbers there, corresponding to the default format string: http://www.networkupstools.org/docs/man/upslog.html -- Charles Lepple clepple@gmail _______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
