Hi, I've been setting up a few Eatons 1500 USB in master/slave mode and run into what I'm thinking is a hostname resolution problem.
Basically, to avoid hardcoding ips, I'd love to be able to add a LISTEN on the lan's ip which has hostname, let's say, server1.local . If I set up upsd.conf such as LISTEN server1.local 3493 what I end up with is upsd listening on 127.0.0.1 . I'm guessing it gets this value from /etc/hosts which overrides server1.local dns resolution. So basically if I want it to listen on anything other than localhost I need to hardcode an ip in upsd.conf or add a line to /etc/hosts, which is not quite convenient if the computer gets its ip from dhcp. What's more, it seems that upsc does the same thing, so if I have a line such as: MONITOR eaton@server1.local ... that will fail if I specified the external ip. However this will succeed from the slave, because there's no server1.local in /etc/hosts I'm guessing so the name resolves to the same ip in the LISTEN. Is this really the desired behavior? I can certainly work with it, but it seems it'd be nice if it could work with dns resolution (at least client side, the LISTEN statement I guess it's ok), but maybe I'm missing some good reason why this would cause other issues. best, Spike
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser