[Nut-upsdev] Should NUT driver daemons abort on unknown parameters?

[Robert Nichols]

Silently ignoring a misspelled parameter is a terrible way to behave.

-- 
Bob Nichols         AT comcast.net I am "RNichols42"

On 1/13/26 04:56, Jim Klimov via Nut-upsdev wrote:
> Cheers,
>
>    PR https://github.com/networkupstools/nut/pull/3258 <https://github.com/networkupstools/nut/pull/3258> aims to "fix" NUT drivers to proceed rather than abort if they encounter unknown parameters (e.g. ones that were introduced with a newer NUT release being tried with an older build).
>
>    The argumentation is that the driver program does the same activity if the unknown argument is ignored as if when it was not specified, so in effect this is a no-op.