colin/NetworkManager
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

cloud-setup: allow bigger restart bursts

Browse Source 
On daemon startup, we may end up enqueueing many nm-cloud-setup.service
restarts in very a short time. That is perfectly fine, just bump the
thresholds so that systemd doesn't get in the way too quickly.

100 requests in 1 seconds seem like a fair choice -- little bit on the
conservative side, yet still giving the service manager some room to
interfere on a chance things really go awry.

https://issues.redhat.com/browse/RHEL-49694
This commit is contained in:
Lubomir Rintel
2024-08-27 00:29:17 +02:00
committed by Fernando Fernandez Mancera
parent 01bee5a6ad
commit 927cff9f17
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
src/nm-cloud-setup/nm-cloud-setup.service.in
View File

@@ -8,6 +8,17 @@ After=NetworkManager.service
Type=oneshot Type=oneshot
ExecStart=@libexecdir@/nm-cloud-setup ExecStart=@libexecdir@/nm-cloud-setup
# The service restart gets triggered from dispatcher script
# (pre-up and dhcp4-change actions), possibly ending up with many
# restart requests at the same time (e.g. on initial daemon startup
# on a machine with multiple NICs). The systemd handles multiple
# concurrent restart requests gracefully (the newer requests supersede
# older, which wait for them to finish), but the default limits are way
# too low: 5 restarts in 10 seconds. Raise that high enough for us to
# be on the safe side.
StartLimitIntervalSec=1
StartLimitBurst=100
#Environment=NM_CLOUD_SETUP_LOG=TRACE #Environment=NM_CLOUD_SETUP_LOG=TRACE
# Cloud providers are disabled by default. You need to # Cloud providers are disabled by default. You need to