Skip to content

upscmd/upsrw: make the "OK" without "TRACKING" warning visible…#3389

Open
jimklimov wants to merge 1 commit intonetworkupstools:masterfrom
jimklimov:issue-3383
Open

upscmd/upsrw: make the "OK" without "TRACKING" warning visible…#3389
jimklimov wants to merge 1 commit intonetworkupstools:masterfrom
jimklimov:issue-3383

Conversation

@jimklimov
Copy link
Copy Markdown
Member

@jimklimov jimklimov commented Apr 1, 2026

…introduce NUT_QUIET_OK_NOTRACKING envvar to hide it though

Closes: #3383

Example:

:; upscmd  -u user -p pass eco650@localhost beeper.mute
OK
WARNING: 'OK' only means the NUT data server accepted
the request as valid, but as we did not wait for result,
we do not know if it was handled in fact.
You can export NUT_QUIET_OK_NOTRACKING=true to hide this message,
or use -w [-t SEC] option(s) to track the actual outcome.

:; NUT_QUIET_OK_NOTRACKING=true upscmd  -u user -p pass eco650@localhost beeper.mute
OK

Note that both the warning and the value returned by the server and reported by upscmd/upsrw (e.g. OK or an error code) are currently printed to stderr. Hopefully nobody relies on parsing that stream, as there may be various other outputs there anyway. Maybe the value from server should be reported on stdout, but that would be a separate issue.

@jimklimov jimklimov added this to the 2.8.5 milestone Apr 1, 2026
…le; introduce NUT_QUIET_OK_NOTRACKING to hide it though [networkupstools#3383]

Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

upscmd/upsrw returns OK before driver processes the command (without -w)

1 participant