Thanks Thomas.

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.

Thanks... you save me a lot of time looking through the jack source code!

Ethan...

On Sat, 2019-03-09 at 15:12 +0100, Thomas Brand wrote:
On Fri, March 8, 2019 19:12, Ethan Funk wrote:
Hello all.


Some notes taken from jackd manpage that cover a few of the topics in your
mail here:

Every JACK client reads environment variables under the hood that can
control some of the aspects you refer to.

$JACK_DEFAULT_SERVER specifies the default server name.
As an example:
JACKD_DEFAULT_SERVER=nondefault jack_lsp

jack_lsp doesn't need special code for handling for that.

$JACK_NO_START_SERVER specifies to not start a server when none is running
(with given name).
As Nettingsmeier pointed out, you really want to start the server
separately with defined parameters and not rely on a client to do it.

Clients can control server name and autostartup behavior in code
explicitly by passing jack_options_t to the jack_client_open() function.

$JACK_PROMISCUOUS_SERVER allows for relaxed permissions, "allowing clients
from different users to talk with the same server"

Finally you can always wrap the server or client startups in a script or
have a small daemon that will do it iff the other approaches aren't good
enough.

Greetings
Thomas