7 Mar
2010
7 Mar
'10
6:15 p.m.
On Mon, Mar 8, 2010 at 12:25 AM, <fons(a)kokkinizita.net> wrote:
On Mon, Mar 08, 2010 at 04:32:39AM +0800, Ray Rashif
wrote:
Out of curiosity, what's the pros and cons of using jackd as a system daemon?
Alex.
--
www.openoctave.org
midi-subscribe(a)openoctave.org
development-subscribe(a)openoctave.org
After further testing, it appears
JACK_PROMISCUOUS_SERVER no longer
works. Paul, is that intentional?
Indeed it doesn't. There's at least one error in
/etc/conf.d/jack-audio-connection-kit: the '-d'
in the driver options leads to a double '-d' in
the final command line. But that isn't the reason
things don't work.
It should be noted that Archlinux provides the
script in /etc/rc.d but does not in any way use
it unless the user takes action (that is normal
Arch policy, if you want any daemons you have to
add them manually to /etc/rc.conf). So far I was
completely unaware of its existence.
I'd be *VERY HAPPY* if jackd could be used as
a system daemon, with e.g. access limited to
members of a the audio group. Or even unlimited.
It would simplify things here *A LOT*.
Ciao,
--
FA
O tu, che porte, correndo si ?
E guerra e morte !
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev