Search results

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

Status: Open.

#3383 In networkupstools/nut;

· cardil opened on Mar 27, 2026

Check if NUT clients always honour the connection timeout

CIEntries related to continuous integration infrastructure (here CI = tools + scripts + recipes)Entries related to continuous integration infrastructure (here CI = tools + scripts + recipes)

Connection stability issuesIssues about driver<->device and/or networked connections (upsd<->upsmon...) going AWOL over timeIssues about driver<->device and/or networked connections (upsd<->upsmon...) going AWOL over time

portabilityWe want NUT to build and run everywhere possibleWe want NUT to build and run everywhere possible

Status: Open.

#3380 In networkupstools/nut;

· jimklimov opened on Mar 27, 2026

·  

2.8.6

RFE: Debug logs from libupsclient methods should include process tags and common timestamps

CIEntries related to continuous integration infrastructure (here CI = tools + scripts + recipes)Entries related to continuous integration infrastructure (here CI = tools + scripts + recipes)

enhancement

portabilityWe want NUT to build and run everywhere possibleWe want NUT to build and run everywhere possible

Status: Open.

#3379 In networkupstools/nut;

· jimklimov opened on Mar 27, 2026

·  

2.8.6

RFE: All standard NUT clients should support -D for debug level

enhancement

service/daemon start/stopGeneral subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/DebugGeneral subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/Debug

Status: Open.

#3378 In networkupstools/nut;

· jimklimov opened on Mar 27, 2026

·  

2.8.5

ignorelb + override.* not reloadable via SIGHUP -- requires driver restart

Status: Open.

#3377 In networkupstools/nut;

· cardil opened on Mar 26, 2026

NUT swarm stress testing (WIN32): upsd should prepare an array of all handles ready to talk, and iterate it like in POSIX code path

enhancement

Windows-not-on-par-with-POSIXAspect of Windows builds known to be dysfunctional compared to POSIX builds; fix needed to be on parAspect of Windows builds known to be dysfunctional compared to POSIX builds; fix needed to be on par

Status: Open.

#3376 In networkupstools/nut;

· jimklimov opened on Mar 26, 2026

·  

2.8.6

RFE: Allow NUT for Windows daemons to customize the pipe name for private signaling

service/daemon start/stopGeneral subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/DebugGeneral subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/Debug

Windows

Status: Open.

#3375 In networkupstools/nut;

· jimklimov opened on Mar 26, 2026

·  

2.8.6

RFE: upslog might do well to reuse libupsclient connections when logging multiple devices from the same server

enhancement

Status: Open.

#3374 In networkupstools/nut;

· jimklimov opened on Mar 25, 2026

·  

2.8.6

RFE: Add an option for upsdrvctl (CLI/ups.conf?) to restart dead drivers, and other refinements

enhancement

service/daemon start/stopGeneral subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/DebugGeneral subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/Debug

Windows-not-on-par-with-POSIXAspect of Windows builds known to be dysfunctional compared to POSIX builds; fix needed to be on parAspect of Windows builds known to be dysfunctional compared to POSIX builds; fix needed to be on par

Status: Open.

#3371 In networkupstools/nut;

· jimklimov opened on Mar 25, 2026

·  

2.8.6

RFE: Add local socket as transport for NUT networked (server-client) protocol within a machine

documentation

NUT protocols

Status: Open.

#3370 In networkupstools/nut;

· jimklimov opened on Mar 25, 2026

·  

NUT 2.9

Reading UPS variables on Windows without TCP/upsd (direct Named Pipe / local-only access?

documentation

documentation-protocolSubmitted vendor-provided or user-discovered protocol information, or similar data (measurements...)Submitted vendor-provided or user-discovered protocol information, or similar data (measurements...)

impacts-release-2.8.4Issues reported against NUT release 2.8.4 (maybe vanilla or with minor packaging tweaks)Issues reported against NUT release 2.8.4 (maybe vanilla or with minor packaging tweaks)

NUT protocols

question

Windows

Status: Open.

#3369 In networkupstools/nut;

· Weruneru opened on Mar 24, 2026

NUT swarm stress testing: revise cleanup of disconnected sockets

Connection stability issuesIssues about driver<->device and/or networked connections (upsd<->upsmon...) going AWOL over timeIssues about driver<->device and/or networked connections (upsd<->upsmon...) going AWOL over time

enhancement

Status: Open.

#3366 In networkupstools/nut;

· jimklimov opened on Mar 23, 2026

·  

2.8.5