Bug#528851: [jackd] Init script shouldn't "fail" if jackd not configured to start

[Adrian Knoth]

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: adi at thur.de  	http://adi.thur.de	PGP/GPG: key via keyserver
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jackd-init.patch
Type: text/x-diff
Size: 446 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20090517/cfc39a3b/attachment.patch>