conf/nut.conf.sample, docs/man/nut.conf.txt: document NUT_DEBUG_PID m…

…issed before [networkupstools#2118] Signed-off-by: Jim Klimov <[email protected]>
jimklimov · Jul 30, 2024 · d1c7450 · d1c7450
1 parent ebba0f6
commit d1c7450
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 0 deletions.
diff --git a/conf/nut.conf.sample b/conf/nut.conf.sample
@@ -94,6 +94,11 @@ MODE=none
 # between that of 'DEBUG_MIN' setting of a driver and the command-line options.
 #NUT_DEBUG_LEVEL=0
 
+# Optionally add current process ID to tags with debug-level identifiers.
+# This may be useful when many NUT daemons write to the same console or log
+# file, such as in containers/plugins for Home Assistant, storage appliances...
+#NUT_DEBUG_PID=true
+
 # Normally NUT can (attempt to) use the syslog or Event Log (WIN32), but the
 # environment variable 'NUT_DEBUG_SYSLOG' allows to bypass it, and perhaps keep
 # the daemons logging to stderr (useful e.g. in NUT Integration Test suite to

diff --git a/docs/man/nut.conf.txt b/docs/man/nut.conf.txt
@@ -122,6 +122,11 @@ Optional, defaults to `0`. This setting controls the default debugging message
 verbosity passed to NUT daemons. As an environment variable, its priority sits
 between that of 'DEBUG_MIN' setting of a driver and the command-line options.
 
+*NUT_DEBUG_PID*::
+Optionally add current process ID to tags with debug-level identifiers.
+This may be useful when many NUT daemons write to the same console or log
+file, such as in containers/plugins for Home Assistant, storage appliances...
+
 *NUT_DEBUG_SYSLOG*::
 Optional, unset by default.
 Normally NUT can (attempt to) use the syslog or Event Log (WIN32), but the