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: 1. 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. 2. Tracking of all the config files (paths) opened to syslog 3. 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...
I want Xorg.0.log entries sent via syslog daemon as well, I am using following line to get it to send new log entries to my logging program (Adds TIMESTAMP!!!) on another PC when something isn't right: rob@some-system:~$ tail -f /var/log/Xorg.0.log | netcat log-listener.local 514 -q -u I detest the extra line-feeds this puts in on my remote logger and not everyone cares to run a listening machine so don't close this one based on that crap solution above. I would much prefer Dag Nygren get his way, then I could just put "Xorg.* @log-listener.local" in the rsyslog.conf of the only machine in my life that gives me "low graphics" grief at the moment - user let's me know it's bombed on him again and if I don't have to leave my PC then why should I?
The systemd Journal captures stderr. The system dbus-daemon logs rejected messages now. Beyond that, the logging options are still "horribly verbose" or "rather quiet". There's a patch on Bug #60859 to add optional pcap packet capture, for when you need to see every message. Realistically, I don't think this is going to be closed unless someone with a less "D-Bus developer" and more "sysadmin" perspective describes what they want logged, preferably in the form of patches.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/dbus/dbus/issues/18.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.