tree bee48ad8460b5e57b17db657b365442f1325572b
parent dd51c37a7c19e8b702379dc8cc3abfb4ff43fbcd
author Andrew Geissler <geissonator@yahoo.com> 1524766057 -0700
committer Brad Bishop <bradleyb@fuzziesquirrel.com> 1525279644 +0000

Change the StartLimitIntervalSec to 30s

The BMC CPU performance is already challenged. When a service is
failing and a core dump is being generated and collected into a dump,
it's even more challenged. Recent failures have shown situations where
the service does not fail again until 15-20 seconds after the initial
failure which means the default of 10s for this results in the service
being restarted indefinitely. Change this to 30s to only allow a
service to be restarted StartLimitBurst times within a 30s interval
before being put in a fail state.

Testing: Verified that killing an application 3 times within 30 seconds
results in the service being in a fail state (and not restarted).

Resolves openbmc/openbmc#3131

Change-Id: I58c874c1c5b618c147946195af65f42371d683c8
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>