Repository navigation
|
Hello My use case is the following, I have one systemd service acting as a DBus server, exposing a DBus method that will be called by several clients (also systemd services). I need to know which client called the method, so I used I'm using sdbus-cpp v1.17 DBus method: DBus server log example: Monitoring: Thank you |
Replies: 3 comments 7 replies
|
When you get unique connection name of the sender (":1.217") as a result of It is completely OK and very typical that not all senders do register a well-known name. D-Bus services do, but pure clients or short-lived clients don't have to. If you have control over the code of senders, you may try to call Otherwise you can use Maybe there are more options, but this is what I am currently aware of. |
|
Thanks for the quick answer. I missed |
|
Hello again, So I tested this with a small DBus client but unfortunately Will try the getCreds*() family next |
To follow up on this, what we ended up doing was:
getObject().getCurrentlyProcessedMessage().getSender(), which would give a unique name (e.g. :1.110)