NUTCONF(8)
β¨ NAME β¨
nutconf β the NUT configuration tool π
so like, it's the little tool that handles all your NUT config files, bestie. she does it all. π
π¦ SYNOPSIS π¦
nutconf --help
nutconf [OPTIONS]
π DESCRIPTION π
okay so <rainbow>nutconf</rainbow> is the tool you use to create and manipulate NUT configuration files. she's giving main character energy for your whole config setup. β¨
and that's not even all β she also supports device scanning, which is the part where she goes and peeks around and then suggests configuration for devices. so thoughtful of her honestly. π«Ά
π§ INSTALLATION π§
ngl this part matters: the scanning feature depends on the very same compile time and run time dependencies as the nut-scanner. literally the exact same ones. so if nut-scanner is happy, scanning in nutconf is happy too. π¦
π OPTIONS π
-h|-help|--helpβ displays the help text. your "hey what do I even do" button π-Dβ raises the debugging level. use this option multiple times for more details. it overrides the optionalNUT_DEBUG_LEVELenvironment variable. (so like,-Dsaid "I got this" π )-v|--verboseβ increases output verbosity (may be used multiple times). the more times you say it, the more she says back β¨--is-configuredβ checks whether NUT was configured, before.--systemβ the system configuration directory shall be used.--localdirectory β sets an alternative configuration directory.--get-modeβ prints the current NUT configuration mode.--set-modemode β sets the NUT configuration mode.
the known modes are, bestie:
standalonenetservernetclientcontrolledmanualnone
π CONFIGURATION ENTRY SET/ADD OPTIONS π
okay so these ones mostly come in 2 forms: --set-... or --add-.... π
the difference, and this is the whole thing: the set options discard previous settings, while the add options keep them. so set = fresh start, add = build on top. got it? periodt. π
also β note that such options may be specified multiple times for one run, which is how you enable setting multiple entries at once. so you can just keep stacking them. π₯
--set-monitor|--add-monitor<arguments> β sets/adds a NUT monitor.- Arguments:
'<ups_ID>' '<host>[:<port>]' '<power_value>' '<user>' '<passwd>' '(\"master\"|\"slave\")'
--set-listen|--add-listen<address> [<port>] β sets/adds theupsd(8)daemon listen address. π--set-device|--add-device<arguments> β sets/adds a device (typically a UPS).- Arguments:
'<ups_ID>' '<driver>' '<port>' '[<attribute>=<value>]*'
the attribute/value pairs follow the device configuration syntax. heads up tho: devices may have very different configuration attributes depending on the driver. an exhaustive description of them is beyond this man page and may be found in NUT documentation. (iykyk β go read the docs for the deep lore π)
--set-notifyflags|--add-notifyflags<type> <flag>+ β sets/adds notification flags for the notification type.- the notification types are, and there's a LOT of them, stay with me:
ONLINEβ mains is presentONBATTβ mains is goneLOWBATTβ remaining battery capacity is lowFSDβ shutdown was forcedCOMMOKβ communication with device establishedCOMMBADβ lost communication with deviceSHUTDOWNβ system is going down, nowREPLBATTβ UPS battery needs replacingNOCOMMβ device is unavailableNOPARENTβ upsmon parent process died, shutdown is impossibleCALβ calibration in progressNOTCALβ calibration finishedOFFβ UPS is administratively OFF or asleep, should wake up on commandNOTOFFβ UPS is no longer administratively OFF or asleepBYPASSβ on bypass = powered, not protectingNOTBYPASSβ no longer on bypassALARMβ UPS is in an alarm state (has active alarms)NOTALARMβ UPS is no longer in an alarm state (no active alarms)OVERβ overloadedNOTOVERβ no longer overloadedTRIMβ trimming incoming voltageNOTTRIMβ no longer trimming incoming voltageBOOSTβ boosting incoming voltageNOTBOOSTβ no longer boosting incoming voltageOTHERβ UPS has at least one unclassified status tokenNOTOTHERβ UPS has no unclassified status tokens anymoreSUSPEND_STARTINGβ OS is entering sleep/suspend/hibernate modeSUSPEND_FINISHEDβ OS just finished sleep/suspend/hibernate mode
- and the notification flags are:
SYSLOGβ use syslogd to log the notificationWALLβ push a message to users' terminalsEXECβ execute a commandIGNOREβ donβt act
- the notification types are, and there's a LOT of them, stay with me:
--set-notifymsg<type> <message> β sets the message for the specified notification type. π--set-shutdowncmd<command> β sets the command used to shut the system down. π--set-user|--add-user<arguments> β sets/adds a NUT user.- Arguments:
- <username> β specifies user name. for a upsmon user it has a special form of
upsmon=(primary|master|secondary|slave), which specifies the monitoring mode. π password=<passwd>β sets the password for the useractions=<actions>β sets actions (SET,FSDare supported)instcmds=<command>β sets instant commands allowed for the user (may be used multiple times)
- <username> β specifies user name. for a upsmon user it has a special form of
- Arguments:
π SCANNING OPTIONS π
okay bestie, here's the tea: whether you actually get each of these scanning options depends on whether the right 3rd-party libraries showed up β both at compile time and at run time. so like, the vibe has to be right at both parties. π«Ά
run the tool with the --help option to check which of the --scan-... options are actually supported. don't just assume, go check, it's giving "look before you leap" energy fr fr.
β° heads up: all timeouts are in microseconds. not seconds. not milliseconds. microseconds. iykyk.
--scan-snmp<start IP><stop IP>[<attribute>=<value>]*β scans for SNMP devices on IP addresses from the specified range.
β¨ known attributes are:
timeoutβ device scan timeoutcommunityβ SNMP community (default:public)sec-levelβ security level (SNMPv3); one ofnoAuthNoPrivauthNoPriv,authPrivsec-nameβ security name (SNMPv3); mandatory companion ofsec-levelauth-passwordβ authentication password (SNMPv3); mandatory forauthNoPrivandauthPrivpriv-passwordβ privacy password (SNMPv3); mandatory forauthPrivauth-protocolβ authentication protocol (SNMPv3):MD5orSHA,MD5is the defaultpriv-protocolβ priv. protocol (SNMPv3):DESorAES,DESis the defaultpeer-nameβ peer name
--scan-usbβ scans the USB bus for known devices π¦--scan-xml-http[<timeout>]β scans for XML/HTTP devices on the network.--scan-nut<start IP><stop IP><port>[<timeout>]β scans for NUT (pseudo-)devices on the network.--scan-avahi[<timeout>]β scans for Avahi devices.--scan-ipmi<start IP><stop IP>[<attribute>=<value>]*β scans for IPMI devices on IP addresses from the specified range.
β¨ known attributes are:
usernameβ username (mandatory for IPMI/LAN)passwordβ user password (mandatory for IPMI/LAN)auth-typeβ authentication type (see below)cipher-suite-idβ cipher suite ID (see below)K-g-BMC-keyβ optional second key (???)priv-levelβ priv. levelworkaround-flagsversionβ (1.5or2.0)
π Authentication types
specifies the IPMI 1.5 authentication type to use (NONE, STRAIGHT_PASSWORD_KEY, MD2, and MD5) with the remote host (default=MD5). this forces connection through the lan IPMI interface, thus in IPMI 1.5 mode. periodt.
noneβ authentication is disabledMD2MD5β (default)plain-passwordβ no ciphering used for password sendingOEMRMCPplus
π Cipher suite IDs
specifies the IPMI 2.0 cipher suite ID to use.
the Cipher Suite ID identifies a set of authentication, integrity, and confidentiality algorithms to use for IPMI 2.0 communication.
the authentication algorithm identifies the algorithm to use for session setup, the integrity algorithm identifies the algorithm to use for session packet signatures, and the confidentiality algorithm identifies the algorithm to use for payload encryption (default=3). literally three jobs in one little number, main character energy honestly.
the following cipher suite IDs are currently supported:
- code
0β Authentication:None, Integrity:None, Confidentiality:None - code
1β Authentication:HMAC-SHA1, Integrity:None, Confidentiality:None - code
2β Authentication:HMAC-SHA1, Integrity:HMAC-SHA1-96, Confidentiality:None - code
3β Authentication:HMAC-SHA1, Integrity:HMAC-SHA1-96, Confidentiality:AES-CBC-128 - code
6β Authentication:HMAC-MD5, Integrity:None, Confidentiality:None - code
7β Authentication:HMAC-MD5, Integrity:HMAC-MD5-128, Confidentiality:None - code
8β Authentication:HMAC-MD5, Integrity:HMAC-MD5-128, Confidentiality:AES-CBC-128 - code
11β Authentication:HMAC-MD5, Integrity:MD5-128, Confidentiality:None - code
12β Authentication:HMAC-MD5, Integrity:MD5-128, Confidentiality:AES-CBC-128 - code
15β Authentication:HMAC-SHA256, Integrity:None, Confidentiality:None - code
16β Authentication:HMAC-SHA256, Integrity:HMAC_SHA256_128, Confidentiality:None - code
17β Authentication:HMAC-SHA256, Integrity:HMAC_SHA256_128, Confidentiality:AES-CBC-128
--scan-serial<port>*β scans for serial devices (of supported types) on the specified serial port(s).
π EXAMPLES π
to set alternative directory for configuration files:
:; nutconf --local ~/test/nut/etc
to add another user (keeping the existing ones):
:; nutconf --add-user bart password=qwerty
to scan USB devices and serial devices (on the first two ports):
:; nutconf --scan-usb --scan-serial /dev/ttyS1 /dev/ttyS2
see? not scary. you got this, bestie. π
π SEE ALSO π
π INTERNET RESOURCES π
the NUT (Network UPS Tools) home page: http://www.networkupstools.org/
and that's a wrap, gorgeous β¨ this was Network UPS Tools 2.8.5, dated 10/07/2026, and yes the page is literally called NUTCONF(8) β go forth and configure, you absolute icon ππ
π¦ where this page comes from
- fedora 43: nut 2.8.5-9.fc43 Β· GPL-2.0-or-later AND GPL-3.0-or-later
- fedora 43: nut 2.8.5-9.fc43 Β· GPL-2.0-or-later AND GPL-3.0-or-later
- fedora 44: nut 2.8.5-9.fc44 Β· GPL-2.0-or-later AND GPL-3.0-or-later
- fedora 44: nut 2.8.5-9.fc44 Β· GPL-2.0-or-later AND GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms