Nedko Arnaudov wrote:
>> If the "jackd in engine mode" (jackd started with --dbus) is running,
>> applications are able to connect, aren't they?
> From what i've understood of Dave's patch, it enables jackd executable
> to start jackdbus thing (same executable). I.e. no separate launcher
> executable.
Looks like a good approach. But, then, I'm still not sure I understand
what you wrote previously:
"So having jackd behave in orthagonal way is not confusing? Like, jackd
process is running, why my apps cannot connect?!?!?"
Did you mean a situation when Dave's jackd process is running and
handling DBUS requests, but the server itself (as in, the thingy that
JACK clients are connecting to) is not running?
If that's really the case, the jack controller can detect the fact it
has just turned the server off, and rename its process to jackd
(inactive) or jack-dbus-controller or something in this fashion. Then,
when the server is started, it renames itself back to jackd. Of course,
I mean, renames the process, not the actual executable (that'd be insane!)
It's not exactly a typical behaviour, but it should eliminate the
problems with interpretation of process list. I don't see any particular
disadvantages (apart from "it's extra work").
Krzysztof
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Received on Wed Dec 19 00:15:44 2007
This archive was generated by hypermail 2.1.8 : Wed Dec 19 2007 - 00:15:44 EET