libmapper: Retry on wait timeouts
At times, early in the boot process, the async GetObject call used in
'mapper wait' can fail with an ETIMEDOUT, probably because the mapper
daemon is so busy introspecting new processes. If this happens, retry
after a 5s wait. Also get a new connection to the bus and event loop
since when this wasn't done the retried method call would fail
immediately.
I first tried to put the ETIMEDOUT check in
async_wait_getobject_callback, but that caused hundreds of more retries
across all the mapper waits in use.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I7175e958fb633b2ecb7479a3307d6918ab29b9f7
1 file changed