Thanks for testing!
On Fri, Mar 23, 2018, 1:00 AM Kevin Fenzi <kevin@xxxxxxxxx> wrote:
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.
[...]
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?
We attempted to keep the logging to a minimum, in particular we try to only log in case of a potential problem.
The main log message is terse, but we include a lot of metadata (and we are open to adding more). Query the journal with `-o verbose` to see more information.
Cheers,
Tom
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
