RFE: Enhance upsd
to LISTEN host:port
with one colon-separated parameter token
#2424
Labels
augeas
Configuration file parser (reader, writer) multi-tool for scripting, etc.
enhancement
Low-hanging fruit
A proposal or issue that is good for newcomers to codebase or otherwise a quick win
nutconf
NUT configuration library and tool
Milestone
Thinking of it... might make sense to parse a single token on a
LISTEN <token1>:<token2>
(with at least one colon character), as anaddr
-colon-port
so spelling ofLISTEN :::3493
would get split into::
and3493
, and someLISTEN 127.0.0.1:3493
would become127.0.0.1
and3493
.That said, in ~25 years of NUT's existence I think this is the first time such issue was raised (to the best of my personal knowledge) - so I guess it is a rare surprise after all the RTFM :)
Originally posted by @jimklimov in #2417 (comment)
UPDATE: This could be easy in the server-side code; most of the problem would be to teach
nutconf
,augeas
and similarupsd.conf
parsers about two acceptable spellings.UPDATE: While at it (although a separate issue): is there any perceived need to parse the
port
part (if its string is not representing a number) through the naming database for services to e.g.LISTEN localhost nut
?CC @aquette @clepple : WDYT ?
The text was updated successfully, but these errors were encountered: