Shouldn't there be a jack-audio-connection-kit init script that will start jackd on boot? Similar to the esound script that starts esd?
IMHO, jack's really useful for DAW apps, and so I'd really recommend using qjackctl to start it. Secondly, I think the esound init.d script serves only the purpose of starting the network sound on boot. Anyway, It should be pretty much trivial to write an init script - just transpose esound's script, and use a /etc/conf.d/jackd configuration file.
How will one select the user as who the jackd will run ? i am not really sure if we want to provide an init script.
I guess we could have it as an option in /etc/conf.d/jackd, but I really dislike that idea. It seems much more fitting that it be placed in a users .xsession or similar per-user startup location... but that's just my $0.02
it looks like the problem will be fixed upstream. if a jack app starts and it cant find a jackd it starts its own jackd. there will be some jackrc file which can be edited manually or with qjackctl.
will be resolved upstream...
*** Bug 112185 has been marked as a duplicate of this bug. ***