…n_instcmd() and main_setvar() handlers [networkupstools#1285, networkupstools#1914]

…ain_setvar() handlers [networkupstools#1285, networkupstools#1914]

…via socket protocol (upsrw etc.) [networkupstools#1285]

Closes: networkupstools#1285

…stools#1917]

…ID, do not proceed to driver handler [networkupstools#1914]

….flag.allow_killpower" setting [networkupstools#1917]

Closes: networkupstools#1917

…oduce NUT_DEBUG_LEVEL envvar support (if no "-D" option(s) among CLI args) [networkupstools#1915]

Closes: networkupstools#1915

…elp text)

… envvars

…cket protocol with (NO)BROADCAST option [networkupstools#1914]

…knowledge of conn_t involved [networkupstools#1914]\

…reload-or-exit" support [networkupstools#1903, networkupstools#1914]

…non-WIN32 builds [networkupstools#1903, networkupstools#1916]

…ka DRIVERS_MAIN_WITHOUT_MAIN now that it is referenced in main_setvar() [networkupstools#1903, networkupstools#1285]

…eparation of string: satisfy platforms where snprintf is a macro [networkupstools#1914]

…est(upslog_flags, UPSLOG_STDERR) at all, not just that the debug is enabled; also mark upslog_start when we first call the method, even if debu is not currently verbose (may change at run time) [networkupstools#1903]

…did recognize and somehow process the request, honour TRACKING if present [networkupstools#1903, networkupstools#1920]

…o `upsd` would accept them and `upscmd` can request them [networkupstools#1903]

…ror" INSTCMD [networkupstools#1903, networkupstools#1914]

… not numbers [networkupstools#1903, networkupstools#1914]

…-restart" support [networkupstools#1903, networkupstools#1914]

…I argument [networkupstools#1903]