Dbus needs better tracking (logging) possibilities
Submitted by Dag Nygren
Assigned to D-Bus Maintainers
I have been trying to debug a dbus configuration problem here for ages now and noticed that the possibilities of tracking a message through DBUS are virtually non-existant. With the new Polcykit etc. coming up it would be a lot easier if we got:
- All debugging info to syslog. Now if you turn on verbose for the system bus daemon it doesn't write to stderr, but somewhere, and you have no possibility to catch it.
- Tracking of all the config files (paths) opened to syslog
- Tracking of messages passed through. Incoming info, security decisions and where it was sent.
I am sure there could be more, but the above would have saved me some days of trying to figure out...