On Sat, May 16, 2009 at 11:18:25AM +0200, Erich Schubert wrote: Hi!
> Or when at shutdown no jackd was found running. When jackd is > installed via some dependencies, it is very common to be configured to > NOT start, so this should at most show up as a "warning" in the > startup logs. It hasn't failed, it's behaving exactly as configured I guess you're right. I also think the majority of jackd installations uses qjackctl or jackd autostart and doesn't rely on a system-wide jackd. Find attached a patch proposal. Does it fix your issue? HTH -- mail: a...@thur.de http://adi.thur.de PGP/GPG: key via keyserver
diff --git a/debian/jackd.init b/debian/jackd.init index e87168d..392c8cf 100755 --- a/debian/jackd.init +++ b/debian/jackd.init @@ -29,8 +29,8 @@ test -f /etc/default/jackd || exit 0 OPTIONS="$OPTIONS" -if [ ! "x$START_DAEMON" = "xyes" -a ! "$1" = "stop" ]; then - echo "Edit /etc/default/jackd to start jackd" +if [ ! "x$START_DAEMON" = "xyes" ]; then + echo "No system-wide jackd. Edit /etc/default/jackd if you want one." exit 0 fi
