summaryrefslogtreecommitdiff
path: root/units/modprobe@.service
diff options
context:
space:
mode:
authorAlban Bedel <alban.bedel@aerq.com>2022-06-15 13:12:46 +0200
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2022-06-21 18:15:34 +0200
commit9625350e5381a68c1179ae4581e7586c206663e1 (patch)
treef2a7322e5be49a8ddc867d4562befbbb43e36088 /units/modprobe@.service
parent19df770fe14da601d4e54e1592c11c10ffe4df5a (diff)
downloadsystemd-9625350e5381a68c1179ae4581e7586c206663e1.tar.gz
units: remove the restart limit on the modprobe@.service
They are various cases where the same module might be repeatedly loaded in a short time frame, for example if a service depending on a module keep restarting, or if many instances of such service get started at the same time. If this happend the modprobe@.service instance will be marked as failed because it hit the restart limit. Overall it doesn't seems to make much sense to have a restart limit on the modprobe service so just disable it. Fixes: #23742
Diffstat (limited to 'units/modprobe@.service')
-rw-r--r--units/modprobe@.service1
1 files changed, 1 insertions, 0 deletions
diff --git a/units/modprobe@.service b/units/modprobe@.service
index cf8baf6084..85a2c08dee 100644
--- a/units/modprobe@.service
+++ b/units/modprobe@.service
@@ -13,6 +13,7 @@ DefaultDependencies=no
Before=sysinit.target
Documentation=man:modprobe(8)
ConditionCapability=CAP_SYS_MODULE
+StartLimitIntervalSec=0
[Service]
Type=oneshot