Reduce service restart limit from 3 to 2 on fails
Further testing has shown that with core files enabled,
it's possible to exceed the 10s default interval time
when doing 3 restarts. Since all testing has shown
either 1 restart fixing the issue, or no restarts fixing
the issue, reduce the restart limit from 3 to 2 to
ensure even if the service is core dumping, the restart
limit will be hit within the 10s.
Resolves openbmc/openbmc#2559
Change-Id: Ie1dac96eb1b4ced0bf166c12419db26924104ab4
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
diff --git a/meta-phosphor/common/recipes-core/systemd/systemd/service-restart-policy.conf b/meta-phosphor/common/recipes-core/systemd/systemd/service-restart-policy.conf
index 0f95073..8e440a4 100644
--- a/meta-phosphor/common/recipes-core/systemd/systemd/service-restart-policy.conf
+++ b/meta-phosphor/common/recipes-core/systemd/systemd/service-restart-policy.conf
@@ -7,7 +7,7 @@
# going to get a fix on a restart of a service, the more time the better
# (think retries on device driver scenarios).
#
-# - Change the StartLimitBurst to 3
+# - Change the StartLimitBurst to 2
# Five just seems excessive for our services in openbmc. In all fail
# scenarios seen so far (other then with phosphor-hwmon), either
# restarting once does the job or restarting all 5 times does not help
@@ -17,4 +17,4 @@
[Manager]
DefaultRestartSec=1s
-DefaultStartLimitBurst=3
+DefaultStartLimitBurst=2