<html dir="ltr"><head></head><body style="text-align:left; direction:ltr;"><div>Thanks Thomas.</div><div><br></div><div>Needing to set the JackServerName option bit flag for jack_client_open() when passing a server name into the function is what I was missing when trying to connect to a named jackd server. And along that same line, the JackNoStartServer flag also solves my server auto-start problem from my client. It's good to know that the environmental variables referenced in the jackd man-page are also used by the client API. That wasn't apparent to me.</div><div><br></div><div>Thanks... you save me a lot of time looking through the jack source code!</div><div><br></div><div>Ethan...</div><div><br></div><div>On Sat, 2019-03-09 at 15:12 +0100, Thomas Brand wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><pre>On Fri, March 8, 2019 19:12, Ethan Funk wrote:</pre><pre>Hello all.</pre><pre><br></pre><pre><br></pre><pre>Some notes taken from jackd manpage that cover a few of the topics in your</pre><pre>mail here:</pre><pre><br></pre><pre>Every JACK client reads environment variables under the hood that can</pre><pre>control some of the aspects you refer to.</pre><pre><br></pre><pre>$JACK_DEFAULT_SERVER specifies the default server name.</pre><pre>As an example:</pre><pre>JACKD_DEFAULT_SERVER=nondefault jack_lsp</pre><pre><br></pre><pre>jack_lsp doesn't need special code for handling for that.</pre><pre><br></pre><pre>$JACK_NO_START_SERVER specifies to not start a server when none is running</pre><pre>(with given name).</pre><pre>As Nettingsmeier pointed out, you really want to start the server</pre><pre>separately with defined parameters and not rely on a client to do it.</pre><pre><br></pre><pre>Clients can control server name and autostartup behavior in code</pre><pre>explicitly by passing jack_options_t to the jack_client_open() function.</pre><pre><br></pre><pre>$JACK_PROMISCUOUS_SERVER allows for relaxed permissions, "allowing clients</pre><pre>from different users to talk with the same server"</pre><pre><br></pre><pre>Finally you can always wrap the server or client startups in a script or</pre><pre>have a small daemon that will do it iff the other approaches aren't good</pre><pre>enough.</pre><pre><br></pre><pre>Greetings</pre><pre>Thomas</pre><pre><br></pre><pre><br></pre><pre><br></pre></blockquote></body></html>