On 21 March 2013 14:10, Martin Jansa wrote:
> Does this resolve also update-rc.d postinst trying to start
> /etc/init.d/dbus-1 and failing to find it?
That's something else to be fixed.
Ross
___
yocto mailing list
yocto@yoctoproject.org
https://lists.y
Does this resolve also update-rc.d postinst trying to start /etc/init.d/dbus-1
and failing to find it?
On Thu, Mar 21, 2013 at 1:36 PM, Burton, Ross wrote:
> On 20 March 2013 08:27, Jukka Rissanen
> wrote:
> > The reason for this was that systemd did not receive NameOwnerChanged
> dbus
> > sig
Hi Ross,
On 21.03.2013 14:36, Burton, Ross wrote:
On 20 March 2013 08:27, Jukka Rissanen 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 Name
On 20 March 2013 08:27, Jukka Rissanen 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 dbu
Hi all,
some update to the problem I am seeing with systemd.
So the symptom of the problem is that after systemd has started a daemon
like connmand, it kills it after 30 secs.
The reason for this was that systemd did not receive NameOwnerChanged
dbus signal telling that the daemon managed to
Hi,
I have a weird problem with systemd. It starts a daemon then kills it
after a 30 second timeout.
Mar 12 08:50:19 eca connmand[970]: Connection Manager version 1.12
...
Mar 12 08:51:49 eca systemd[1]: connman.service operation timed out.
Terminating.
Mar 12 08:51:49 eca connmand[970]: Ter
