On Tue, 15 Nov 2016 at 16:02:07 +0100, Daniel Wagner wrote:
> commit 09aa0243aac40ec4e5bd0fbe41e702be4952a382
> Author: Patrik Flykt
> Date: Thu Sep 17 10:42:46 2015 +0300
>
> connman.service: Fix dependencies for early boot
>
> Unset default dependencies in order to properly run a
Hi,
Daniel Wagner wrote on 15/11/16 15:02:
> Hi Colin,
>
> On 11/15/2016 03:46 PM, Colin Guthrie wrote:
>> Hope you're keeping well?
>
> Doing fine! How is live in the north?
Grand thank you! :)
>> So, by default, dbus should be socket activated. That means that when
>> If socket activation
Hey Daniel,
Hope you're keeping well?
So, by default, dbus should be socket activated. That means that when
dbus.service eventually starts shouldn't really matter, provided it is
eventually started. This is because it's actually dbus.socket that's the
important unit. It should be started by socke
Hi Colin,
On 11/15/2016 03:46 PM, Colin Guthrie wrote:
> Hope you're keeping well?
Doing fine! How is live in the north?
> So, by default, dbus should be socket activated. That means that when
> dbus.service eventually starts shouldn't really matter, provided it is
> eventually started. This i
[Cc: systemd mailing list"
what happened until now
"""
I am working on a system based on Yocto Project which uses ConnMan
v1.33 for network management. The system uses systemd and generally
works well so far, but once in a blue moon ConnMan fails to start up.
Here is the relevant log from systemd
