On Wed, 29 Jun 2011, Arjen de Korte wrote:
Citeren Charles Lepple <[email protected]>:
I guess I see the scanning code as a stopgap way to contact "legacy"
servers (or what would be legacy after some discovery protocol like mDNS is
set up), and either timeouts or non-blocking is just a kludge to make that
work a little better. And isn't opening a non-blocking socket just a way to
split socket connection and protocol initialization?
If that's the case, this should be handled by the nut-scanner itself. For any
hosts found to be listening on port 3493 it would then proceed to use the
upscli_connect call to check if it really is a NUT server.
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.
--
Stuart D. Gathman <[email protected]>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
_______________________________________________
Nut-upsdev mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
