rsyslog: Don't disable systemd StartLimit
It is undesirable to have a service restart continually forever if it
gets stuck in a failure loop. This workaround was added due to
"RestartUnit" being ignored if the rsyslog unit had already failed. A
fix to the "RestartUnit" logic has been added, so that the StartLimit is
reset after a configuration change but before calling "RestartUnit".
This will ensure restarts are reliable after configuration change, but
we don't have rsyslog trying to restart indefinitely.
(From meta-phosphor rev: c82d32f8e6993f83ddda35dd1a2152eca8188408)
Change-Id: I719489ceadfadb3cca71bbdbb1697fa83cad2e2f
Signed-off-by: William A. Kennington III <wak@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
diff --git a/meta-phosphor/recipes-extended/rsyslog/files/rsyslog-override.conf b/meta-phosphor/recipes-extended/rsyslog/files/rsyslog-override.conf
index faeeae0..458f52f 100644
--- a/meta-phosphor/recipes-extended/rsyslog/files/rsyslog-override.conf
+++ b/meta-phosphor/recipes-extended/rsyslog/files/rsyslog-override.conf
@@ -1,6 +1,3 @@
[Unit]
-# This service is restarted when an rsyslog property is set, so
-# disable rate limiting to allow it to always be restarted.
-StartLimitIntervalSec=0
# This file exists only if remote logging has been configured
ConditionPathExists=/etc/rsyslog.d/server.conf