Some NUT daemons have a way to send signals (e.g. upsd -c reload contacting a running copy), with Windows builds using calls like pipe_create(UPSD_PIPE_NAME); to set up a named pipe. That name is hard-coded (via common.h like #define UPSMON_PIPE_NAME TEXT("upsmon"), where TEXT is variably defined in /usr/include/w32api/winnt.h) for each daemon, so no more than one instance can be running on the same system.
This issue proposes to make the name configurable via upsd.conf and upsmon.conf (as the two currently impacted daemons; drivers already use custom-named pipes), with current values being just a default. Note that scripts/Windows/wininit.c (nut.exe service manager) would also need to parse that, to communicate with daemon instances that it launched.
Loosely related to #3370 (that idea would probably also need configurable pipe/socket names, for different platforms).
Some NUT daemons have a way to send signals (e.g.
upsd -c reloadcontacting a running copy), with Windows builds using calls likepipe_create(UPSD_PIPE_NAME);to set up a named pipe. That name is hard-coded (viacommon.hlike#define UPSMON_PIPE_NAME TEXT("upsmon"), whereTEXTis variably defined in/usr/include/w32api/winnt.h) for each daemon, so no more than one instance can be running on the same system.This issue proposes to make the name configurable via
upsd.confandupsmon.conf(as the two currently impacted daemons; drivers already use custom-named pipes), with current values being just a default. Note thatscripts/Windows/wininit.c(nut.exeservice manager) would also need to parse that, to communicate with daemon instances that it launched.Loosely related to #3370 (that idea would probably also need configurable pipe/socket names, for different platforms).