Hi David, > 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.
we want it this way to make PACrunner also usable from NM and other connection manager daemons. And that race is known. I have this on my list of things to fix and mentioned this to everybody (including you) that this exists. We need to delay the initial FindProxyByURL response a little bit to give ConnMan time to load the configuration. This is a one time trade off when the daemon starts. We also need to do that anyway since downloading the PAC file might take time. Right now we also not handle that one nicely either. Regards Marcel _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
