Increase StartLimitIntervalSec to 240s
The DefaultTimeoutStartSec is 90s. If a service is hitting
this timeout repeatedly then the StartLimitIntervalSec needs
to be set in a way to handle this worse case scenario so
that the service which is timing out does not continuously
get restarted.
This means it needs to be set to:
StartLimitBurst*DefaultTimeoutStartSec +
StartLimitBurst*<worst case processing time> (30s)
which currently would be 2x90 + 2x30
Ref: systemd-system.conf
Tested: Verified that if 90s timeout is hit in service that
it is no longer restarted after 2 attempts.
Resolves openbmc/openbmc#3379
Change-Id: I12eca7bc23f54d77b4bf0327e44eb042359aaeae
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
1 file changed