Skip to content

systemd: reduce default service stop timeout to 5s#2395

Merged
r3claimer merged 1 commit intoROCKNIX:nextfrom
aenertia:systemd-aggressive-shutdown
Apr 1, 2026
Merged

systemd: reduce default service stop timeout to 5s#2395
r3claimer merged 1 commit intoROCKNIX:nextfrom
aenertia:systemd-aggressive-shutdown

Conversation

@aenertia
Copy link
Copy Markdown
Contributor

@aenertia aenertia commented Mar 9, 2026

Noticed during testing - this is already set for some things - this makes it consistent.

On ROCKNIX's read-only squashfs root, network services don't need graceful shutdown — only persistent storage sync matters. Services like iwd and systemd-resolved can hang for 90s (the systemd default) on shutdown/reboot, blocking device access during development and causing poor user experience on handheld gaming devices.

Changes:

  • Add system.conf.d/10-shutdown-timeout.conf with DefaultTimeoutStopSec=5s and DefaultTimeoutAbortSec=5s
  • Add TimeoutStopSec=1s to iwd.service (matches existing pattern used by avahi, bluez, sshd, samba)
  • Add TimeoutStopSec=1s to systemd-resolved override

On ROCKNIX's read-only squashfs root, network services don't need
graceful shutdown — only persistent storage sync matters.  Services
like iwd and systemd-resolved can hang for 90s (the systemd default)
on shutdown/reboot, blocking device access during development and
causing poor user experience on handheld gaming devices.

Changes:
- Add system.conf.d/10-shutdown-timeout.conf with
  DefaultTimeoutStopSec=5s and DefaultTimeoutAbortSec=5s
- Add TimeoutStopSec=1s to iwd.service (matches existing pattern
  used by avahi, bluez, sshd, samba)
- Add TimeoutStopSec=1s to systemd-resolved override

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@r3claimer r3claimer merged commit c9adf7b into ROCKNIX:next Apr 1, 2026
@r3claimer
Copy link
Copy Markdown
Contributor

This is fine, usually not an issue but sometimes definitely an annoying issue.

aenertia added a commit to aenertia/distribution that referenced this pull request Apr 3, 2026
Adopts upstream patterns:
- systemd: use upstream 10-shutdown-timeout.conf filename with our
  aggressive 1s values (upstream merged our PR ROCKNIX#2395 with 5s defaults)
- iwd/resolved: upstream adopted our TimeoutStopSec=1s
- ppsspp-sa: add clock speed ES feature
- scummvm: scan script moved to tools
- CI: SM6115 device in selection matrix
- kernel configs: upstream auto-update

nert/next changes preserved:
- All version bumps and SM8250 fixes intact
- All mainline targets (SM8250/SM8550/SM8650/H700/S922X/RK3399/RK3566/SM6115)
  unified on kernel 7.0-rc5
- cgroupv2 slices, containers, wayvnc, inputplumber, rxjoy integration
@aenertia aenertia deleted the systemd-aggressive-shutdown branch April 4, 2026 07:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants