Look at the signature of the dbus signal as it's fired in dbus-monitor. It should give you all the information you need. The service, the path, the interface and the method/signal name. And also the parameters.
Printable View
Look at the signature of the dbus signal as it's fired in dbus-monitor. It should give you all the information you need. The service, the path, the interface and the method/signal name. And also the parameters.
OK I'll try that out and report back :thumb:
I can think of an easy example... That's exactly what the obdsim dbus generator does. In C:Quote:
Now I just need to learn how to grab DBus events without depending on introspection... Any clues?
src/sim/generators/dbus/gen_dbus.c
It would take much to write a config file for obdsim that would listen to obdgpslogger. So a determined user could do something like launch
obdsim -g Random -o
Then launch another obdsim with the DBus generator configured to listen to obdgpslogger. Ideally you'd get almost exactly the same output from both logger instances [practical reasons mean you wouldn't get *exactly* the same output, but it'd be damn close]
Gary (-;