Problem: By default, systemd services generated from the NixOS system configuration don't attempt to restart on failure since Restart=no. However, in some cases, running processes can fail for unclear reasons, and the simplest way to bring the failed service back to life is to restart it. Instead, currently, the service will fail and trigger an alert without attempting to restart.
Solution: Add default values for startLimitBurst, startLimitIntervalSec, Restart, and RestartSec.
Description
Related issue(s)
Fixed #
:white_check_mark: Checklist for your Pull Request
Related changes (conditional)
Tests
[ ] If I added new functionality, I added tests covering it.
[ ] If I fixed a bug, I added a regression test to prevent the bug from
silently reappearing again.
Documentation
[ ] I checked whether I should update the docs and did so if necessary:
Problem: By default, systemd services generated from the NixOS system configuration don't attempt to restart on failure since Restart=no. However, in some cases, running processes can fail for unclear reasons, and the simplest way to bring the failed service back to life is to restart it. Instead, currently, the service will fail and trigger an alert without attempting to restart.
Solution: Add default values for startLimitBurst, startLimitIntervalSec, Restart, and RestartSec.
Description
Related issue(s)
Fixed #
:white_check_mark: Checklist for your Pull Request
Related changes (conditional)
Tests
Documentation
Stylistic guide (mandatory)
✓ Release Checklist
package.yaml
.vX.Y