rsyslog unit configuration results in systemd 241 busy loop #19
Comments
geissonator
pushed a commit
to openbmc/meta-phosphor
that referenced
this issue
Apr 5, 2019
Don't enable the remote-logging image feature by default. This avoids openbmc/phosphor-logging#19, which prevents OpenBMC from advancing its upstream subtrees (like poky, meta-openembedded ...). Change-Id: If54e5a3405c97a5d3ecd40f2aaf092cdc923c270 Signed-off-by: Brad Bishop <[email protected]>
geissonator
pushed a commit
to openbmc/openbmc
that referenced
this issue
Apr 5, 2019
Don't enable the remote-logging image feature by default. This avoids openbmc/phosphor-logging#19, which prevents OpenBMC from advancing its upstream subtrees (like poky, meta-openembedded ...). (From meta-phosphor rev: b2c81a4dbdb409e1fae7fdefda99adb97f40d912) Change-Id: I428e2d5a8d1184c25e4900ae166a99baf5f8094d Signed-off-by: Brad Bishop <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While testing with Yocto HEAD (996d1f4518) which includes systemd 241 I find that our rsyslog unit configuration causes systemd to busy wait/loop for a period during boot.
The text was updated successfully, but these errors were encountered: