search for: 99_nut

...Driver failed to start (exit status=1) If I try to access the port /dev/ttyUSB0 using minicon (minicom -D /dev/ttyUSB0) or cat ( cat /dev/ttyUSB0 ), the access to device is denied. Then, I try these instructions [0], but nothing changes when I try to open the serial port: # /etc/udev/rules.d/99_nut-serialups.rules KERNEL=="ttyUSB0", GROUP="nut" [0] http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux My /etc/ups/ups.conf has the following configuration: [ups] driver = blazer_ser port = /dev/ttyUSB0 Any tips about that? Thanks...

On Feb 18, 2014, at 10:15 PM, Charles Lepple wrote: > On Feb 18, 2014, at 5:55 PM, Thiago Tiedtke dos Reis wrote: > >> Hi, >> >> Recently I got three units of this nobreak [0]: > ... >> [0] http://www.sms.com.br/produtos/Nobreak-SMS/Manager-III-Senoidal > > According to the HCL, for the Manager III, you might want to try the blazer_ser (or in 2.7.1,

...ups port = /dev/ttyS0 /etc/nut/upsd.users: [upsmon] upsmon master password = somepass /etc/nut/upsmon.conf: MONITOR Patriot_Pro_II_750 at localhost 1 upsmon somepass master /etc/passwd: nut:x:112:119::/var/lib/nut:/bin/false /etc/group: dialout:x:20:nut nut:x:119: /etc/udev/rules.d/99_nut-serialups.rules: KERNEL=="ttyS0", GROUP="nut" ________________ # ls -l /etc/nut -rw-r----- 1 root nut 1544 Nov 23 12:36 nut.conf -rw-r----- 1 root nut 4634 Nov 23 14:03 ups.conf -rw-r----- 1 root nut 4577 Nov 23 13:26 upsd.conf -rw-r----- 1 root nut 2177 Nov 23 14:04 upsd.u...