dbus-wait uses a "success" exit code for timeout: https://git.yoctoproject.org/dbus-wait/tree/dbus-wait.c#n33 This should probably be configurable so the caller can decide whether that should be an error or not. This was making usage in runtime desktop image testing more challenging than it should be. The timeout should also perhaps be an optional parameter?
Hi, Can we use dbus_connection_read_write_dispatch's timeout arg option, which can be based on a command-line parameter passed to the application, instead of the fixed wait time of 60 seconds?
(In reply to Dixit Parmar from comment #1) > Hi, > Can we use dbus_connection_read_write_dispatch's timeout arg option, which > can be based on a command-line parameter passed to the application, instead > of the fixed wait time of 60 seconds? No, because it can not be specific to a match rule or connection type. :)