3 ms·
File-based tools is an interesting question. D-Bus is hierarchical, but it's also strongly typed, so you'd have to encode stuff as text, and when you get the se
by geofft 12y ago
File-based tools is an interesting question. D-Bus is hierarchical, but it's also strongly typed, so you'd have to encode stuff as text, and when you get the serialization wrong, write(2) can't give you a useful error message. But maybe it'd be useful for reading and monitoring.... imagine if you could `sudo tail -f /dbus/org/freedesktop/UDisks2/Manager` or something, and see all calls to it.
I've been using D-Feet and dbus-monitor, which seem to be solid enough. D-Bus does have extensive introspection.
But yeah, in general the state of D-Bus tooling is miserable. Part of it is how verbose it is — which is fine for compiled software, but for interactive use, it really makes you miss the "creat" and "umount" school of thought. Part of it is that there aren't great introspection tools at the command line.
- ppurka 12y agoThe only D-Bus tool that is nice in the command line is qdbus, and that stems from Qt. I wonder why the original D-Bus writers could not write a decent enough command line tool for it.
- seba_dos1 12y agoTry mdbus2 - https://github.com/freesmartphone/mdbus https://github.com/freesmartphone/mdbus - it's also in Debian/Ubuntu repos. It's a little tool that works really well with dbus services that properly implement introspection. We used it extensively on Openmoko phones to play with our middleware (or when GUI was broken ;) )