"Rui Nuno Capela" <rncbc@xxxxxxxxx> writes:
>> $ ./jack_test3_run.sh 600
>> Launching jack_test3_nmeter...done.
>> Launching 20 ./jack_test3_client(s) instance(s)...done.
>> Running
>> jackd...1...2...3...4...5...6...7...8...9...10...11...12...13...14...15...16..../jack_test3_run.sh:
>> line 48: 32325 Killed ${CMD} >>${LOG} 2>&1
>> done.
>
> OK. That's it. Your test runs were being terminated prematurely. I think
> your setup can't handle the stress of more than 16 clients. This maybe
> caused by an old jackd version. Please, retry with 14 clients only, and be
> back after then ;)
I believe several people have hit this problem due to /usr/bin/jackd
being hard-coded in the script. The default location is actually
/usr/local/bin/jackd. It's probably better to just use `jackd' and
let $PATH resolve the name...
--- jack_test3_run.sh~ Fri Dec 10 06:21:21 2004
+++ jack_test3_run.sh Thu Dec 30 08:04:10 2004
@@ -24,7 +24,7 @@
NMETER_ARGS="t c i x b m"
# jackd configuration.
-JACKD="/usr/bin/jackd"
+JACKD="jackd"
JACKD_DRIVER="alsa"
JACKD_DEVICE="hw:0"
JACKD_PRIO=60
--
joq
