| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
In all of our recipes, we should be following yoctos lead on formatting,
order, and other things, for consistency in our meta layers.
This commit runs oe-stylize.py on all of our files. The types of
changes being made can be seen in the commit, but amount to:
1. Setting an explicit key ordering
2. Sectioning the files appropriately
3. Applying rules checking to our files
At some point in the near future, we would turn this on as part of
repotest, but some minor changes need to be upstreamed to meta-oe (WIP)
to make that happen.
Looking for input on whether this is something we'd like to do, and
whether the diffs below look reasonable to folks.
Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: I489dd21d38a9fe4f3ece89cc7a5e1d0463224abf
|
|
Directory /etc/rsyslog.d/ is expected to hold several *.conf files each
serving an independent purpose, all processed in order for each syslog
message.
The deprecated action ~ means "discard action is carried out, the
received message is immediately discarded. No further processing of it
occurs". Thus the config files that happen to be alphabetically after
server.conf are not going to ever see any messages, and that is
unexpected and confusing.
Fix by shipping a config which writes any message to /dev/null. This is
needed to avoid error 2103 in default configuration where no other
output actions are specified for rsyslog. Also enable processing of
other *.conf file which might be shipped by other packages or added by
an end user.
This should also be accomplished by a similar change to phosphor-logging
so that it wouldn't revert to wrong behaviour when sending to remote
syslog is disabled.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
Change-Id: I5da9a46df1b8cf1326bb1a7b93af18cfc568dee8
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I588025b614416c43aa2d053765ab53bacf890cb5
|
|
Commit 138108a changed the way the rsyslog service is
started. It removed the rsyslog override config file
and also removed references to the rsyslog-policy recipe
that used to install that file.
However, rsyslog-policy recipe itself was still a part of the repo.
Bitbake would still parse the recipe and warn about the missing
rsyslog override file.
This commit removes the policy recipe from the repo.
Tested:
No more warning when we bitbake a phosphor image.
(From meta-phosphor rev: 03b8ecd41c69e2754830efc274961432d7a77358)
Signed-off-by: Santosh Puranik <santosh.puranik@in.ibm.com>
Change-Id: I292e13f565c40b32527427154b5f570767146827
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This reverts commit 37bc1a3568f2e87987be05243627a984dc051de1.
In addition, it changes the default rsyslog server config to
ignore all messages. Also bumps up phosphor-logging:
phosphor-logging: srcrev bump f59854e94b..0a0b5ea558
Santosh Puranik (1):
rsyslod: Change disable action
Tested:
Verified that the default rsyslog behavior is to now ignore
all messages.
(From meta-phosphor rev: 138108a05f68ada8b990024bbaa8b68b135d6aeb)
Signed-off-by: Santosh Puranik <santosh.puranik@in.ibm.com>
Change-Id: Iba11dfa153eaeef17417c82ab26f9a26fe5f9125
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
It is undesirable to have a service restart continually forever if it
gets stuck in a failure loop. This workaround was added due to
"RestartUnit" being ignored if the rsyslog unit had already failed. A
fix to the "RestartUnit" logic has been added, so that the StartLimit is
reset after a configuration change but before calling "RestartUnit".
This will ensure restarts are reliable after configuration change, but
we don't have rsyslog trying to restart indefinitely.
(From meta-phosphor rev: c82d32f8e6993f83ddda35dd1a2152eca8188408)
Change-Id: I719489ceadfadb3cca71bbdbb1697fa83cad2e2f
Signed-off-by: William A. Kennington III <wak@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
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>
|
