On Thu, Apr 24, 2014 at 2:37 PM, Kris Jordan <[email protected]> wrote:
> > upsset.cgi doesn't check that user/password is valid, it just tries it when > doing a command. > > I just tested it, it is working for me on a remote and a local UPS using the > below upsd.users configuration. > > [admin] > password = xxxxxxxxxx > instcmds = ALL > actions = SET > actions = FSD > First I want to thank both you and Mr. Lepple for taking the time to post your suggestions. Your example of the upsd.users file worked fine for me. In the interest of a complete explanation, I found my example of the upsd.users file at the URL http://www.networkupstools.org/docs/user-manual.chunked/ar01s06.html and it looked like the following. [monuser] password = mypass upsmon master # or upsmon slave Based on that my upsd.users looked like [ups] password = XXXXXXX upsmon master # or upsmon slave That didn’t work but your example which I cut and pasted into upsd.users and then added my password did work with the user admin as you used. My mistake was in thinking that the “mon” and “set” uspd.users configurations were the same and they are not. If I had clicked on the reference “upsd.users (5)” I would have been taken to http://www.networkupstools.org/docs/man/upsd.users.html which would have explained that. That only leaves the output voltage reported by usbhid-ups not reporting correctly but perhaps that will be solved in an updated version of it. There was no change in 2.7.2 but I did not expect any based on the change log. Thanks again to both of you. _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
