From: Ratan Gupta <ratagupt@linux.vnet.ibm.com>
To: Brad Bishop <bradleyb@fuzziesquirrel.com>,
Ed Tanous <ed@tanous.net>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
Patrick Williams <patrick@stwcx.xyz>
Subject: Emit interface added signal
Date: Thu, 18 Mar 2021 16:03:21 +0530 [thread overview]
Message-ID: <580c5e6c-5946-eedc-25b0-53315a0831cd@linux.vnet.ibm.com> (raw)
Hi Team,
I faced the following issue in some of the D-Bus services.
Generally D-Bus services emit the interface added signal once the D-Bus
object gets created.
D-Bus objects can be created in two scenario
1) Actual creation of D-Bus object due to some action.
2) Restore the old D-Bus objects reading from the file system.
e.g. Restore the dump objects / Error log objects etc.
We are having some use cases where we have to send the Rest/Redfish
event to the external clients once the dbus object gets added and for
the same we watch for the interface added signal.
Due to the 2) we send the false events to the external clients as the
D-Bus service gets restarted due to any reason(BMC reboot / Genuine
Failure).
Proposal: Don't emit the interface added signal by the D-bus service if
we are restoring the D-Bus objects from file system.
Do we see any concern here? or any other way to fix the above issue?
Ratan
next reply other threads:[~2021-03-18 10:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 10:33 Ratan Gupta [this message]
2021-03-18 14:57 ` Emit interface added signal Patrick Williams
2021-03-19 8:37 ` Ratan Gupta
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=580c5e6c-5946-eedc-25b0-53315a0831cd@linux.vnet.ibm.com \
--to=ratagupt@linux.vnet.ibm.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=ed@tanous.net \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
/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).