Bug 35899

Summary:	jack-audio-connection-kit init script?
Product:	Gentoo Linux	Reporter:	Joel Parker <jjk3>
Component:	New packages	Assignee:	Torben Hohn (RETIRED) <torbenh>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	clock, coldwind, eldad, sound, tigger
Priority:	High
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
Package list:		Runtime testing required:	---

Description Joel Parker 2003-12-15 14:12:27 UTC

Shouldn't there be a jack-audio-connection-kit init script that will start jackd on boot? Similar to the esound script that starts esd?

Comment 1 Eldad Zack (RETIRED) gentoo-dev

2004-01-24 05:52:58 UTC

IMHO, jack's really useful for DAW apps, and so I'd really recommend using qjackctl to start it.

Secondly, I think the esound init.d script serves only the purpose of starting the network sound on boot.

Anyway, It should be pretty much trivial to write an init script - just transpose esound's script, and use a /etc/conf.d/jackd configuration file.

Comment 2 Torben Hohn (RETIRED) gentoo-dev

2004-02-18 01:20:12 UTC

How will one select the user as who the jackd will run ?
i am not really sure if we want to provide an init script.

Comment 3 Jeremy Huddleston (RETIRED) gentoo-dev

2004-02-28 05:22:25 UTC

I guess we could have it as an option in /etc/conf.d/jackd, but I really dislike that idea.  It seems much more fitting that it be placed in a users .xsession or similar per-user startup location...

but that's just my $0.02

Comment 4 Torben Hohn (RETIRED) gentoo-dev

2004-03-03 23:47:23 UTC

it looks like the problem will be fixed upstream.
if a jack app starts and it cant find a jackd it starts its own jackd.

there will be some jackrc file which can be edited manually or with qjackctl.

Comment 5 Jeremy Huddleston (RETIRED) gentoo-dev

2004-05-04 20:13:41 UTC

will be resolved upstream...

Comment 6 Jakub Moc (RETIRED) gentoo-dev

2005-11-11 08:21:28 UTC

*** Bug 112185 has been marked as a duplicate of this bug. ***