Revert "Increase StartLimitIntervalSec to 240s"

This reverts commit 342c041b108a30d2bcaee3553971a7f3ca5798e0.

These settings apply to all service starts (not just the error
ones) so this will not work because we have multiple oneshot
services that can be started multiple times if someone is
powering on and off a system quickly.

It does not appear to apply to services that are stopped by conflict
but it does affect oneshot services. Will need to spend some
more time investigating this. Could give our oneshot services
some override settings but would like to see if something more
universal can be done.

Resolves openbmc/openbmc#3393

Change-Id: I511542b1bc420692b791da1318779c188a8ebb5d
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
1 file changed
tree: 59ec0bbe3c0ac68831d3014cdd39710c2960aa24
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. recipes-connectivity/
  6. recipes-core/
  7. recipes-devtools/
  8. recipes-extended/
  9. recipes-phosphor/
  10. recipes-support/
  11. recipes-textproc/
  12. COPYING.apache-2.0
  13. COPYING.MIT
  14. LICENSE
  15. MAINTAINERS
  16. README.md
  17. recipes.txt
README.md

OpenBMC

meta-phosphor is the OpenBMC layer. This layer should be included for all OpenBMC systems. The OpenBMC layer contains content which is shared between all OpenBMC systems.