On 06/21/2017 03:52 PM, Julien Massot wrote:
I'm currently integrating PacRunner,
but I don't see any recommended solution to start it.
PACRunner ship a dbus autostart file in:
BTW the path is not correct, I will send a patch to have
And PacRunner doesn't ship any systemd unit file, so my guess was that
ConnMan will start it through dbus if a proxy server is set manually, or if wpad
discover a pac/wpad file.
But ConnMan plugins doesn't call PacRunner if the daemon is not running,
and explicitely ask to not start the daemon.
static void destroy_proxy_configuration(void)
line 237: dbus_message_set_auto_start(msg, FALSE);
static void default_service_changed(struct connman_service *service)
line 267: if (!daemon_running)
So from my point of view, shipping a systemd unit file is not the best solution,
since starting pacrunner on boot is a waste of time.
And ConnMan pacrunner plugin,
should try to autostart PacRunner if we connect to a network which
have a proxy configured or discovered.
Last solution should be that on a first call of libproxy pacrunner
starts but it look like a bad solution since most likely connman will
not send the proxy
I haven't really a clue what the dependencies are. Isn't there already
some integration in some distributions? At least we got some patches
from distros on PacRunners. Maybe there are some pointers how it might