[yocto] systemd timeouts started daemons

[Burton, Ross]

On 20 March 2013 08:27, Jukka Rissanen <jukka.rissanen at linux.intel.com> wrote:
> The reason for this was that systemd did not receive NameOwnerChanged dbus
> signal telling that the daemon managed to register its name to the system
> bus.
>
> I checked with dbus-monitor that these NameOwnerChanged signals are indeed
> sent by dbus-daemon but they are not seen in debug prints from systemd.

Andreas sent a patch earlier that masks the dbus init script, because
the names don't match so you'll end up with two system buses
attempting to run.  I'm not sure how this will fail, but it could mean
that systemd isn't listening to the bus that connman is starting on,
or something.

The easy hack to test this is to delete /etc/init.d/dbus-1 and the
symlinks to it in /etc/rc*.

Ross