From: "Xiaochao Ma (马小超)" <maxiaochao@inspur.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Can't Call BMCweb/JournalEventLogEntryCollection function
Date: Fri, 4 Dec 2020 01:24:29 +0000 [thread overview]
Message-ID: <0e0a25dea3074ccdab0fcf57f62cebf4@inspur.com> (raw)
Hi all
I tested the JournalEventLogEntryCollection function in the bmcweb module. I found it unexpectedly that I couldn't use the resfish url to call it.
No matter what I change the macro definition ‘BMCWEB_ENABLE_REDFISH_DBUS_LOG_ENTRIES’, the DBusEventLogEntryCollection function is always called.
The bmcweb -- redfish-core/include/redfish.hpp:
#ifndef BMCWEB_ENABLE_REDFISH_DBUS_LOG_ENTRIES
nodes.emplace_back(
std::make_unique<JournalEventLogEntryCollection>(app));
nodes.emplace_back(std::make_unique<JournalEventLogEntry>(app));
nodes.emplace_back(std::make_unique<JournalEventLogClear>(app));
#endif
.
.
.
#ifdef BMCWEB_ENABLE_REDFISH_DBUS_LOG_ENTRIES
nodes.emplace_back(std::make_unique<DBusLogServiceActionsClear>(app));
nodes.emplace_back(std::make_unique<DBusEventLogEntryCollection>(app));
nodes.emplace_back(std::make_unique<DBusEventLogEntry>(app));
#endif
I modify the macro definition by modifying bmcweb/meson_options.txt .
option('redfish-dbus-log', type : 'feature', value : 'disabled', description : 'Enable DBUS log service transactions through Redfish.....
Even if I write this definition as'disable' in meta-inspur/recipe-phosphor/bmcweb/...bbappend, the JournalEventLogEntryCollection cannot be called.
Are there other configurations that will affect it?
reply other threads:[~2020-12-04 1:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0e0a25dea3074ccdab0fcf57f62cebf4@inspur.com \
--to=maxiaochao@inspur.com \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).