[Nut-upsdev] Changes to upscli_connect (and general discovery)

[Arjen de Korte]

Citeren "Stuart D. Gathman" <stuart op bmsi.com>:

> That is a very good idea.  Use some other port scanning code to narrow down
> ports to try instead of corrupting upscli_connect with complications not
> needed for normal operation.

This still leaves me with one question - being able to auto-detect the  
upsd servers does not help in finding which UPS is providing power to  
a client. So how is this going to help setting up things? Only if a  
single server would be found that monitors only one UPS you *might*  
have found the one that is providing power (but you could also be on a  
non-UPS outlet). Since power cords are independent from the network  
cables (most of the time that is), this will never work for  
installations with more than one upsd server. And if you only have  
one, the whole point of auto-detection is moot.

Maybe I'm missing the point here, but as far as I can see there is no  
way for clients to auto-detect which UPS to monitor. I do see merit in  
auto-detecting UPS (or other devices) for setting up the upsd server,  
but as far as I'm concerned, we're wasting our time on the nut-scanner.

Best regards, Arjen
-- 
Please keep list traffic on the list (off-list replies will be rejected)