Bug 296553 - sysutils/nut: should nut be in the operator group?
Summary: sysutils/nut: should nut be in the operator group?
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Cy Schubert
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-07-06 14:43 UTC by Dan Langille
Modified: 2026-07-06 14:43 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (cy)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Langille freebsd_committer freebsd_triage 2026-07-06 14:43:54 UTC
Cy,

Should nut be in the operator group? I'm not yet proposing we do that by default. At present, I'm just wondering if it needs to be in there for shutdown.

After a recent power outage, I've concluded nut is not actually shutting down the servers:

Jul  6 11:17:45 r730-01 upsmon[2468]: Exiting upsmon program after initiating shutdown
Jul  6 11:17:45 r730-01 upsmon[2466]: upsmon parent: Unable to call shutdown command: /sbin/shutdown
Jul  6 11:17:45 r730-01 upsmon[2466]: upsmon parent: Exiting after trying to call (256) shutdown command: /sbin/shutdown

That, combined with each NVMe now having an UNSAFE SHUTDOWN value one greater than last week, led me to believe the host was not being shutdown. The logs also don't show the jails being shutdown as expected.

Could it be as simple as nut not being in the right groups?

[14:37 r730-03 dvl ~] % id nut
uid=316(nut) gid=316(nut) groups=316(nut),68(dialer)

"pw group mod operator -m nut"

Side note: why dialer?

more detail at https://dan.langille.org/2026/07/06/during-a-power-outage-how-do-the-three-servers-in-the-basement-react/