I don't see dbus-daemon being started by dbus?

[Sandeep Puddupakkam (spuddupa)]

Attached is the patch. The job file we used to start dbus-daemon is
called messagebus.

The patch is as follows

------cut-------

410a411,445

> static void

> event_finished_dbus_connect(Event *event)

> {

>     char *value;

> 

>     nih_debug ("Finished %s event doing event_finished_dbus_connect", 

>               event->name);

>     if (strcmp(event->name,"started")==0) {

>         value = environ_expand(NULL, "${JOB}",event->env);

>         if (value) {

>             nih_debug ("   Job: %s", value);

>             if (strcmp(value,"messagebus")==0) {

>     /* Open connection to the system bus; we normally expect this to

>      * fail and will try again later - don't let ENOMEM stop us
though.

>      */

>                 while (control_bus_open () < 0) {

>                     NihError *err;

>                     int       number;

> 

>                     err = nih_error_get ();

>                     number = err->number;

>                     nih_debug ("Error Number %d ", number);

>                     nih_free (err);

> 

>                     if (number != ENOMEM)

>                         break;

>                 }

>             }

>             nih_free(value);

>         }

>     }

> }

> 

> 

> 

480a516

>     event_finished_dbus_connect(event);

------cut-------

________________________________

From: Saravanan Shanmugham (sarvi) 
Sent: Wednesday, October 01, 2008 10:22 AM
To: Kelvin Chan; upstart-devel at lists.ubuntu.com
Cc: Sandeep Puddupakkam (spuddupa); Corey Stohs (cstohs)
Subject: RE: I don't see dbus-daemon being started by dbus?

 

Sure. We can send you the patches.  

Sandeep, please pullout the upstart patches from the DDTS when you have
the time and send it over.

 

Kelvin, could you please make sure they get merged into Upstart trunk. 

If there is some other formal process to get our patches into trunk, do
let us know and we will follow it.

 

Thx,

Sarvi 

 

 

________________________________

From: upstart-devel-bounces at lists.ubuntu.com
[mailto:upstart-devel-bounces at lists.ubuntu.com] On Behalf Of Kelvin Chan
Sent: Wednesday, October 01, 2008 10:01 AM
To: upstart-devel at lists.ubuntu.com
Subject: Re: I don't see dbus-daemon being started by dbus?

Hi Sarvi,

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/upstart-devel/attachments/20081001/f053d8bb/attachment-0001.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: upstart_messagebus.patch
Type: application/octet-stream
Size: 1134 bytes
Desc: upstart_messagebus.patch
Url : https://lists.ubuntu.com/archives/upstart-devel/attachments/20081001/f053d8bb/attachment-0001.obj