On 03/13/2018 07:04 AM, Tom Gundersen wrote: > Hi, > > dbus-broker is a new DBus message bus implementation. We are proposing > it as the default in Fedora as of F29 [0], and as such we would be > grateful for as much testing as possible before the switch is made. > > For instructions on how to test, see [1]. > > Cheers, > > Tom and David > > [0]: <https://fedoraproject.org/wiki/Changes/DbusBrokerAsTheDefaultDbusImplementation> > [1]: <https://fedoraproject.org/wiki/Changes/DbusBrokerAsTheDefaultDbusImplementation#How_To_Test> So everything seems to be working fine for me with it, but I did notice that the logs are... quite a bit more terse. Here's the 4 messages I have so far: Mar 22 16:46:20 taim.scrye.com systemd[1]: Starting D-Bus System Message Bus... Mar 22 16:46:20 taim.scrye.com systemd[1]: Started D-Bus System Message Bus. Mar 22 16:46:26 taim.scrye.com dbus-broker[1284]: :1.27 failed to send message, due to policy. Mar 22 16:46:26 taim.scrye.com dbus-broker[1284]: :1.27 failed to send message, due to policy. For contrast, my last boot with dbus had 11673. It appears dbus logs every connection: Mar 21 13:32:43 taim.scrye.com systemd[1]: Started D-Bus System Message Bus. Mar 21 13:32:43 taim.scrye.com dbus-daemon[1311]: [system] Successfully activated service 'org.freedesktop.systemd1' Mar 21 13:32:43 taim.scrye.com dbus-daemon[1311]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.3' (uid=0 pid=1319 comm="/usr/libexec/bluetooth/bluetoothd " label="system_u:system_r:bluetooth_t:s0") I don't know if we need to log every success by default, but perhaps we could find a middle ground? at least the failed sends might have more information so we could see what was doing that? Thanks. kevin
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
