On Sun, May 17, 2009 at 2:04 PM, Stéphane Letz <letz@email-addr-hidden> wrote:
>
> 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?
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Received on Mon May 18 00:15:06 2009
This archive was generated by hypermail 2.1.8 : Mon May 18 2009 - 00:15:06 EEST