Re: [LAD] [Jack-Devel] more jack/qjackctl madness : some comments

PrevNext  Index
DateSun, 17 May 2009 14:10:05 -0400
From Paul Davis <[hidden] at linuxaudiosystems dot com>
ToStéphane Letz <[hidden] at grame dot fr>
CcNedko Arnaudov <[hidden] at arnaudov dot name>, Linux Audio Developers <[hidden] at lists dot linuxaudio dot org>, JACK Developers <[hidden] at jackaudio dot org>
In-Reply-ToStéphane Letz Re: [LAD] [Jack-Devel] more jack/qjackctl madness : some comments
Follow-UpStéphane Letz Re: [LAD] [Jack-Devel] more jack/qjackctl madness : some comments
On Sun, May 17, 2009 at 2:04 PM, Stéphane Letz <[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?
PrevNext  Index

1242583824.10019_0.ltw:2,a <eb4b5e1d0905171110ma76c6c9g574e977f64be34eb at mail dot gmail dot com>