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:
On 07/29/2016 05:57 AM, Lennart Poettering wrote:
On Thu, 28.07.16 13:44, Chip ([email protected]) 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
I see that my question re: issues with systemd, is more suited for non
development list.
Is there a non development systemd list?
Thanks.
___
systemd-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo
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
starts and other times fails to start.
All files in /etc/systemd/
