linuxaudio.org

Le 17 mai 09 à 20:10, Paul Davis a écrit :
> On Sun, May 17, 2009 at 2:04 PM, Stéphane Letz  wrote:

quoted text
>>

>> The point is that when compiled in D-Bus mode, libjack behaves

>> differently

>> regarding the way it start the server: it does not use the fork

>> +exec mode

>> anymore but call the D-Bus service to start the server. This

>> "simple" change

>> is the source of all the problems we then see.

>

> so if i understand correctly, there is effectively a layer of

> indirection. rather than a request arriving via D-Bus leading to a

> normal fork-exec, it leads to D-Bus service request, which presumably

> (somewhere, sometime) leads to a fork-exec of the server? is this

> correct?

"Show me the code" :
http://trac.jackaudio.org/browser/jack2/trunk/jackmp/posix/

JackPosixServerLaunch.cpp
It starts the D-Bus jackaudio service that actually starts "jackdbus"

process with it's own logic (server settings save/restore and so on...)
Hoppefully I described it right (Nedko again?)
Stephane

_______________________________________________

Linux-audio-dev mailing list

Linux-audio-dev@lists.linuxaudio.org

http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev