-
-
Notifications
You must be signed in to change notification settings - Fork 365
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nut-scanner should add non-standard NUT ports to "nutclient" configs #1815
Labels
Milestone
Comments
The format does work for dummy-ups:
Same for
|
jimklimov
added a commit
to jimklimov/nut
that referenced
this issue
Jan 16, 2023
jimklimov
added a commit
to jimklimov/nut
that referenced
this issue
Jan 16, 2023
jimklimov
added a commit
to jimklimov/nut
that referenced
this issue
Jan 16, 2023
jimklimov
added a commit
to jimklimov/nut
that referenced
this issue
Jan 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While searching for devices served by
upsd
on a randomNUT_PORT
in the NIT suite, the script gets the following config from nut-scanner:So the
NUT_PORT
values are not appended, e.g. asport = "UPS2@127.0.0.1:12345"
. As currently provided, clients using this config would tryupsd
on port 3493 which would likely not serve such devices.This ticket is about fixing that, after making sure the clients (dummy-ups relay, upsc, etc.) can actually parse this format (should for decades, unless something broke).
Tests added per #1814 should verify that the port is mentioned in output (unless it is default).
The text was updated successfully, but these errors were encountered: