The PacRunner dæmon is designed to be started automatically on demand by DBus service activation (which would work better if we rename pacrunner.service to org.pacrunner.service, btw.)
ConnMan will notice when PacRunner appears on the bus, and will prod it with configuration information. But PacRunner doesn't *know* that ConnMan is running, and doesn't know to *wait* for that information. So it usually just returns 'direct://' for the first request that activates it, even though that might be the wrong answer. I'm not sure why it was done this way round. Shouldn't PacRunner have been monitoring ConnMan, rather than vice versa? Then it would *know* when it can start responding to requests. -- David Woodhouse Open Source Technology Centre [email protected] Intel Corporation _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
