Re: [Jack-Devel] jackd 0.116 won't release terminal?

Hi George,

> I am doing something similar to what was described in part B) of your answer
> and actually have a script similar to the one at the end of the link you
> showed.  I did have to put the sleep in there also to get things started
> up.  I happened to be running this in a terminal over SSH on a server for
> testing purposes.  When exited the shell and expected the terminal to close
> it was kept open.  Since I had run several processes that interact with
> jackd I killed them one at a time and it wasn't until I killed jackd that
> the ssh session closed allowing the terminal window to close.  This is what
> led me to believe that jackd had some dependency on a controlling terminal
> or something.

If you started jackd from a terminal, killing jackd is necessary to
close the terminal, in that particular use case. ~ i also have done
this before (and recently). on my latest machine the only way to
access the machine is remotely (the Nvidia GPU is toast).

as for using sleep, that is necessary. however, what i do on my one
machine (that can use VGA ouput) is actually have it boot into
fluxbox, and jackd isn't in my script that starts up the apps. Instead
jackd is started before the WM starts, which gives it enough time
before my apps load up (As fluxbox loading gives enough time in
between).

> This is what I'm referring to with respect to auto-start:

> http://trac.jackaudio.org/wiki/jackdrc%285%29
> http://trac.jackaudio.org/wiki/jackdrc(5)

Ya, that auto-start specifically says the (jackd) server will start as
"needed", meaning that if you start a jack-client/application, the
server will auto-start, not that it will start on boot... (samething
as in qjackctl).

jordan

1299789979.22105_0.ltw:2,a <AANLkTi=2MxqGd_iBKv-MkQTs0icxd2mZrmNjQk3CZzf6 at mail dot gmail dot com>