Gregory Gulik wrote: > > Ah. For the time being I set it up to have everything run as root. > Once it's working I'll sort out the permissions issues. > > tripplite_usb is recognizing the UPS correctly: > > Starting tripplite_usb: Network UPS Tools - Tripp Lite OMNIVS and > SMARTPRO driver 0.6 (2.1.0) > Warning: This is an experimental driver. > Some features may not function correctly. > > Detected a UPS: TRIPP LITE/TRIPP LITE SMART1500RMXL2Ua > Using SMARTPRO protocol (3003) > Attached to Tripp Lite SMART1500RMXL2Ua > > > But then when upsd starts up it can't seem to communicate with the > tripplite_usb driver: > > Starting upsd: Network UPS Tools upsd 2.1.0 > Can't connect to UPS [tripplite] (tripplite): No such file or directory > Synchronizing........ giving up
If you are running the driver with "-u root", then you must run upsd with "-u root" as well. This is (I think) because upsd communicates with the driver through a socket that is owned by the driver. > The ups.conf file has the following: > > [tripplite] > driver = tripplite_usb > port = auto > desc = "Tripp-Lite 1500RM XL2U" > > This is on Fedora Core 4 if it makes a difference. > > > > > Peter Selinger wrote: > > >Looks like a permissions problem. USB drivers require some special > >setting-up. They key is to start by running the driver with "-u root". > > > >I wrote some instructions for APC/newhidups at > >http://www.mathstat.dal.ca/~selinger/ups/backups.html; they might > >help. > > > > > > -- > Greg Gulik http://www.gulik.org/greg/ > greg @ gulik.org _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
