Hi enrike, > This kinf of OT because it is pretty general question. I ask here > because i think in this list people would know more about solutions to > my question that in any other list.
it's not OT as long as you use pure:dyne ;) > so here it goes, i might do an installation with one of my apps (that > uses supercollider as sound engine and python (opengl) for the > interface). i would need to run the app on startup for supercollider to > run, in this case i would like to start jackrack as well, because I > would like to avoid using a piece of hardware for equalization by using > jack rack. > > So i would need this to happen on startup: > start the system > start jack > start jackrack and load certain configuration in a .rack file > start my app > connect my supercollider output to jackrack and this to sound output. for "hello process" (http://metabiosis.goto10.org/hello-process/) Marloes and I are calling everything from /etc/rc.local https://code.goto10.org/svn/metabiosis/projects/hello_process/trunk/shell/rc.local and the main startup script is https://code.goto10.org/svn/metabiosis/projects/hello_process/trunk/shell/hello-process.sh > i think i would know how to create the script to run the apps but how > about setting up the connections? i you can use jack_lsp, jack_connect, jack_disconnect in a shell script > would this be reliable? i mean this > would have to be really solid and never fail to start, i am not sure how > long the installation would be running but probably couple of months. Unless your installation requires to be running really 24/7, then I would suggest you have someone turn it on or off where it will be running, just make sure that everything runs correctly once the computer starts. Of course you could also make it run non-stop, we did that in the past and unless you have a bug in your code (specially memory leak) or in any other software that relies on it then pure:dyne or GNU/Linux in general is really reliable. However, it doesn't hurt, if you want to run everything non-stop, that you start a little background daemon that whill check if a certain list of process are still up and running, and if it's not the case this script could restart your main startup script etc... have fun :) a. > any suggestions? > > many thanks > > enrike > > > --- > [email protected] > irc.goto10.org #pure:dyne > --- [email protected] irc.goto10.org #pure:dyne
