On Tue, 15 Jun 2010 17:53:18 -0700, Fernando Lopez-Lezcano
wrote:
one
maximum.
oh my,
fwiw, the retry logic is there since dawn. i can assure you it's been
there for half a decade now ;) it's there for making sure qjackctl connects
to the starting jackd server as a client of its own.
indeed, this logic is some kind of a leftover from the early days. when
machines were slower (in errors per second:) and jackd had some
considerable startup overhead before stabilizing to accept client
connections.
the delay between retrials is/was even progressive ie. each retrial takes
a bit longer then the one before, but that's now irrelevant i'm afraid ;)
the retrial code path will be scrapped asap. the only way for you to avoid
qjackctl being stalled due to a (very) slow jackd startup is now giving it
a slack via the start delay configuration setting (cf Setup/Settings/Start
Delay).