Re: [Nut-upsuser] upsd/upsc, LISTEN and hostname resolution in master/slave

Somewhat related: has anyone used nss-myhostname to ensure that the local hostname can be looked up even without DNS? Seems like this is the intended use case. Also, assuming NUT has been built against glibc (more than likely, for most desktop/server Linux distributions), you can use "getent hosts

Re: [Nut-upsuser] upsd/upsc, LISTEN and hostname resolution in master/slave

Manuel, I very much appreciate you taking the time to share such depth of experience, that makes a lot of sense and clearly things out very thoroughly. I will amend my ansible common playbook to get rid of that line and will test to see if I can find any problems elsewhere, but otherwise that soun

Re: [Nut-upsuser] upsd/upsc, LISTEN and hostname resolution in master/slave

On 03/29/2017 06:35 PM, Spike wrote: thank you Arno, I'm with Manuel on the "IP address or hostname", maybe I didn't understand your previous explanation, but to me there's still a bigger issue/unclear behavior. Let's say I just installed ubuntu on a machine with hostname server1 and ip 192.1

Re: [Nut-upsuser] upsd/upsc, LISTEN and hostname resolution in master/slave

oh, my bad, actually, you even mentioned it, the other option would be to listen on 0.0.0.0 . I guess that'd work even tho it'd then be a good thing to have local firewall as you suggested. So maybe just have that in the docs too? I still think it'd be worth clarifying, if I got that right, that us

Re: [Nut-upsuser] upsd/upsc, LISTEN and hostname resolution in master/slave

thank you Arno, I'm with Manuel on the "IP address or hostname", maybe I didn't understand your previous explanation, but to me there's still a bigger issue/unclear behavior. Let's say I just installed ubuntu on a machine with hostname server1 and ip 192.168.0.1 . In /etc/hosts I end up with two l

Re: [Nut-upsuser] upsd/upsc, LISTEN and hostname resolution in master/slave

On 03/29/2017 02:28 PM, Arnaud Quette wrote: 2017-03-29 12:32 GMT+02:00 Arnaud Quette >: 2017-03-29 5:49 GMT+02:00 Spike mailto:sp...@drba.org>>: (...) Is this really the desired behavior? I can certainly work with it, but it seems it

Re: [Nut-upsuser] upsd/upsc, LISTEN and hostname resolution in master/slave

2017-03-29 12:32 GMT+02:00 Arnaud Quette : > > > 2017-03-29 5:49 GMT+02:00 Spike : > (...) > >> 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

Re: [Nut-upsuser] upsd/upsc, LISTEN and hostname resolution in master/slave

2017-03-29 5:49 GMT+02:00 Spike : > Hi, > Hi again Spike ;) 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 h

[Nut-upsuser] upsd/upsc, LISTEN and hostname resolution in master/slave

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 a