On Sat, Jul 12, 2008 at 2:25 PM, Arnold Krille <arnold(a)arnoldarts.de> wrote:
Am Samstag, 12. Juli 2008 schrieb Kjetil S.
Matheussen:
Arnold Krille:
My big cron jobs check wether "pidof
jackd" returns something or not. And
if a jackd is running, they don't start...
That's a good idea. But what if
the file locate updater cron job
has started before you start jack? That could be devastating
if doing a recording of many channels.
I either start my computer well ahead of the real recording session (usually I
check mails and blogs before), or I start jack before the cron jobs try to
run the first time.
Or I simply wait till my backup is finished. Its worth the wait...
And when its really necessary I login/su to root and stop crond (and with it
all its childs).
Have fun,
Arnold
--
I have had my best results with defining a custom runlevel. ksysv
helps with this if you run a system that uses SysV style init (this
would include Debian and Ubuntu). Then you can do a simple "sudo
telinit 3" to turn off all daemons that may interfere with audio
performance (usually, on Debian at least, 2 is the default run level,
and 3-5 are available for custom usage, 0 is halt, 1 is single user,
and 6 is reboot). One approach is to copy the /etc/rc.1/ directory to
/etc/rc.3/ and turn things on selectively until it makes a usable
system. This is also a great way to learn about all those little tasks
that are idling in your htop display, and what they are doing. This is
a bit of work, but is worth it.