I am trying to port upstart-0.5.0 to an embedded Linux platform and encountering this same problem.
wondering you can send us your patchs for the fix and the "systembus" job script ?
Thanks,
Kelvin Chan
----------------------------------------------------------------------
Saravanan Shanmugham (sarvi) sarvi at cisco.com
Tue Sep 23 23:28:11 BST 2008
Previous message: I don't see dbus-daemon being started by dbus?
Next message: Upstart 0.5.0, /proc, and telinit
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Sandeep,
I have made the following fix into upstart to get this work.
Made the following code sengment into a function.
In the event_finished() function, I look for a "started" event for a
special Job called "systembus"
When the systembus job moves into started, I try to connect to the dbus
again.
This means that some one has to define a special upstart job file called
"systembus" which will start the D-Bus daemon.
And Upstart Iit will try to connect to it when it sees the started event
for that special job.
This works fine and I am able to create a dbus-glib client that is able
to connect and query Upstart through DBus.
Haven;t tested signals yet. Thats next on the list.
Is this approach reasonable. Once I am done can I send this as a patch
over for integration
Sarvi
-- upstart-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
