Skip to content

Conversation

@m13253
Copy link
Owner

@m13253 m13253 commented May 9, 2025

This solves an issue that on (at least) Fedora and if NetworkManager starts too slow, systemd may stop trying to start it after hitting StartLimitBurst limit.

Thanks to systemd 254, by providing RestartSteps and RestartMaxDelaySec options, we can let the service retry at an exponential backoff delay.

I choose the exponential factor to be 1.618, maxed at 76 seconds, because Fibonacci backoff seems to be another popular backoff sequence. By my educated guess, I think this should be a good number to start with?

I am not sure if this change would ruin somewhere else. Please cast your opinions before I merge it to the master branch.

…to restart it

This solves an issue that on (at least) Fedora and if NetworkManager starts too slow, systemd may stop trying to start it.
@m13253 m13253 merged commit 59a47c8 into master May 13, 2025
2 checks passed
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