MGE-SHUT(8)
β¨ mge-shut β the SHUT protocol driver bestie π
okay so real talk, this is the manual page for mge-shut, and it lives in section 8 of the NUT Manual. It's the driver for SHUT Protocol UPS equipment. She's niche, she's specific, she's iconic. Let's get into it π«Ά
πΈ NAME πΈ
mge-shut β Driver for SHUT Protocol UPS equipment β‘
π SYNOPSIS π
mge-shut -h
mge-shut -a UPS_NAME [OPTIONS]
Note β this man page is ONLY about the hardware-specific stuff for themge-shutdriver. The core driver lore lives elsewhere, bestie. For all that, go readnutupsdrv(8). π
π¦ SUPPORTED HARDWARE π¦
mge-shut supports all recent Eaton, MGE and Dell UPS models which use the SHUT protocol. And yes, SHUT stands for Serial HID UPS Transfer, now you know, iykyk β¨
Older MGE models β think Pulsar ESV+, Pulsar EX and Pulsar ES+ β are on a whole different vibe. They use the U-Talk protocol, so they should use the mge-utalk driver instead. Different era, different protocol, no notes π
π EXTRA ARGUMENTS π
This driver also supports the following optional settings. Yes, "extra" β she's giving main character energy and taking bonus config π
lowbatt=numβ sets the low battery warning threshold, aka the moment shutdown gets initiated byupsmon(8). The factory default value is30(in percent), and whether you can change it is settable depending on the exact model. Some models just say no, and honestly? respect πoffdelay=numβ sets the timer before the UPS gets turned off after the kill power command is sent (that's the one you send via the-kswitch). The default value is20(in seconds). Usually this must be lower thanondelay, but lowkey the driver will NOT warn you on startup if it isn't. It's just gonna let you live your truth πondelay=numβ sets the timer for the UPS to switch on in case the power comes back after the kill power command was sent but before the actual switch off. The whole point is making sure the machines connected to the UPS are, in all cases, rebooted after a power failure. The default value is30(in seconds). Usually this must be greater thanoffdelay, but again, the driver will not warn you upon startup if it isn't. Some UPSes will restart no matter what, even if the power is (still) out at the moment this timer elapses. In that case, you could try if settingondelay = -1inups.confhelps. Fingers crossed bestie π€
Warning β theondelayparameter was set in ten-seconds unit in the legacymge-shut(8)driver (e.g.3for 30 seconds). It is now set in seconds (30for 30 seconds). Make sure you use the correct unit in your configuration. Not me having a units glow-up and forgetting to tell everyone π
notification=numβ set notification type to1(no),2(light) or3(yes). This argument is ignored. It is only here for backward compatibility. She's a legacy queen, she stays, she does nothing π
π KNOWN ISSUES π
Repetitive timeout and staleness
Some models tend to be unresponsive with the default polling frequency. The result is that you have some "data stale" errors in your system log. Not the vibe. π
In this case, simply modify the general parameter pollinterval to a higher value (like 10 for 10 seconds). This should solve the issue. Slay π
Using notification=3 might also help. (Yes, the same one that's otherwise ignored. She's helping from the bench π«Ά)
π AUTHOR π
Arnaud Quette
π SEE ALSO π
The core driver
Internet resources
- The NUT (Network UPS Tools) home page:
https://www.networkupstools.org/historic/v2.8.5/
okay that's the whole page, bestie β¨ every flag, every default, every warning, all accounted for, no cap π
this was Network UPS Tools 2.8.5, dated 10/07/2026 β mge-shut(8), out ππ¦πΈ periodt
π¦ 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