the thing to check are the permissions on the nodes under /dev/shm/jack<br><br>the main (only) thing that the promiscuous server does is to change those permissions so that people other than the user that started jack can access them. your umask or other system settings might interfere with this.<br>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Dec 2, 2012 at 3:53 PM, Fons Adriaensen <span dir="ltr">&lt;<a href="mailto:fons@linuxaudio.org" target="_blank">fons@linuxaudio.org</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Sun, Dec 02, 2012 at 03:31:28PM -0500, Paul Davis wrote:<br>
<br>
&gt; what doesn&#39;t work? i&#39;ve seen people using it on #jack within the last<br>
&gt; several months<br>
<br>
</div>Seems like jack_client_open() fails. Unless the user is the same<br>
one that started jackd. JACK_PROMISCUOUS_SERVER defined for both<br>
server and clients.<br>
<br>
jackd version 0.121.3 tmpdir /dev/shm protocol 24<br>
<br>
downloaded and installed today.<br>
<div class="HOEnZb"><div class="h5"><br>
Ciao,<br>
<br>
--<br>
FA<br>
<br>
A world of exhaustive, reliable metadata would be an utopia.<br>
It&#39;s also a pipe-dream, founded on self-delusion, nerd hubris<br>
and hysterically inflated market opportunities. (Cory Doctorow)<br>
<br>
</div></div></blockquote></div><br></div>