dnscrypt-proxy: start from procd interface trigger, not in init 4675/head
authorDirk Brenken <dev@brenken.org>
Thu, 27 Jul 2017 10:44:43 +0000 (12:44 +0200)
committerDirk Brenken <dev@brenken.org>
Mon, 7 Aug 2017 09:48:17 +0000 (11:48 +0200)
commitf5d5f5f176b66b4c441bef70ff2fdf817edf5164
treeae271e559619d1b65d67a0d0ecf3e2955acc5f40
parent5a58466cac323b6d7f2deca40ecefb8b170a3cae
dnscrypt-proxy: start from procd interface trigger, not in init

* Start dnscrypt-proxy from procd interface trigger rather than
immediately in init, to fix a possible race condition during boot and
get rid of rc.local restarts. You can restrict trigger interface(s) by
'procd_trigger' in new global config section.

* tab/whitespace cosmetics

Signed-off-by: Dirk Brenken <dev@brenken.org>
net/dnscrypt-proxy/Makefile
net/dnscrypt-proxy/files/dnscrypt-proxy.config
net/dnscrypt-proxy/files/dnscrypt-proxy.init