Age | Commit message (Collapse) | Author | Files | Lines |
|
Rsyslog is currently used only for remote logging. The daemon would run
though (started by systemd) even when remote logging has not been
configured. In other words, it would run without any actions.
With Yocto 2.6, rsyslogd won't run without any actions. Hence, start
rsyslogd on demand - only when remote logging is configured.
(From meta-phosphor rev: 37bc1a3568f2e87987be05243627a984dc051de1)
Change-Id: Ic895ea80b2fb2537a25d1d40d4ae156f3d95c629
Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Update meta-phosphor to master HEAD.
Adriana Kobylak (2):
rsyslog-policy: Add rsyslog-override.conf
Move remote logging features to their own category
Brad Bishop (2):
phosphor: rsyslog: remove obmc-phosphor-license
phosphor: mrw-api: fetch all of serverwiz
Change-Id: Ic342bda5d19272b2806f65c7082189d4a79c69d8
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The intent is to use rsyslog for streaming journal logs off of the BMC.
Since this is the only intent (i.e at the moment there's no requirement
to employ rsyslog for local logging), modify rsyslog.conf accordingly.
(From meta-phosphor rev: a549e7540ede46686c5011ac2f7209704643a2d6)
Change-Id: I01d7dbd648da82536085f7586efcd7f1c7dd8ae0
Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|