On 29/07/16 18:56, Simon McVittie wrote:
> So I'm not sure what you're doing, or
> where your dnscrypt-proxy.{socket,service} came from.
It's a bug in the Debian/Ubuntu packaging for dnscrypt-proxy, which have
their own fork of the systemd units, possibly derived from 1.6.0. I've
opened a bug in
On 29/07/16 18:46, Chip wrote:
> And I believe, yes, network must be operating before
> dnscrypt-proxy activates. I'm guessing that some configuration file in
> /etc/systemd/system/ needs tweaking?
My normal advice would be to talk to dnscrypt-proxy upstream or the
supplier of your
On 07/29/2016 12:56 PM, Simon McVittie wrote:
On 29/07/16 16:59, Chip wrote:
On 07/29/2016 05:57 AM, Lennart Poettering wrote:
My educated guess is that some cyclic dependency or so caused it to
not be considered for activation at boot.
Lennart's guess was correct:
Jul 29 11:33:06
On 29/07/16 16:59, Chip wrote:
> On 07/29/2016 05:57 AM, Lennart Poettering wrote:
>> My educated guess is that some cyclic dependency or so caused it to
>> not be considered for activation at boot.
Lennart's guess was correct:
> Jul 29 11:33:06 blablabla systemd[1]: basic.target: Found ordering
On 07/29/2016 05:57 AM, Lennart Poettering wrote:
On Thu, 28.07.16 13:44, Chip (jeffsch...@gmail.com) wrote:
Ubuntu 16.04
With no changes to software or anything, on reboot, systemd *sometimes* will
start dnscrypt-proxy.service while other times just ignores it and it fails
to start. There
On Thu, 28.07.16 13:44, Chip (jeffsch...@gmail.com) wrote:
> Ubuntu 16.04
>
> With no changes to software or anything, on reboot, systemd *sometimes* will
> start dnscrypt-proxy.service while other times just ignores it and it fails
> to start. There is no rhyme or reason as to why sometimes it
