| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change the default log level from "debug" to "info" for
the messages that are stored on disk and forwarded to
syslog, so that debug messages don't fill up the journal
and more important ones are lost when the journal file
rotates.
Tested: Verified that debug messages such as the ipmi
"IPMI SET_SENSOR" ones are not printed anymore.
(From meta-phosphor rev: 3692b801b4f273905b87b6de2e61ba3839dae4f0)
Change-Id: I84a88511ed2ff90d0b3c2a77ae968cddcff6899f
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
(From meta-phosphor rev: 3537e1c6eeaef3f4f96201697b8b59f69824168b)
Change-Id: Ia8ca83dd210fc82261e3296c270c18187ba5309a
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
At one point there were duplicate kernel logs going
into the journal. One was disabled (e9722d1) using systemd
configuration options. Not sure what changed but recently
no kernel messages have been going into the journal.
Testing: Verified that only one kernel message appears
in the journal with this change.
(From meta-phosphor rev: 9e5d2bf6d989261478ec0d17705bb883c84ad4a5)
Change-Id: I93bc90b53a0926c610304f73b567e56ad13a0ff1
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
(From meta-phosphor rev: ee52526c80eaca65a581c01bcf703861ec1a80b6)
Change-Id: I8ff4febeb46a746dd3e5e625c5bdc3735963799b
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
|
Adopt a more conventional directory hierarchy. meta-phosphor is still
a _long_ way from suitable for hosting on yoctoproject.org but things
like this don't help.
(From meta-phosphor rev: 471cfcefa74b8c7ceb704cb670e6d915cf27c63b)
Change-Id: I3f106b2f6cdc6cec734be28a6090800546f362eb
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
