21 Apr
2003
21 Apr
'03
12:33 p.m.
Hello,
How can I make Jackd always run? Right now I have to set it up in a
console window. I'd like to learn how to run it always at startup and
not have to start/stop it when I need it.
Also how do you use Jack in real-time mode? In order to run it I have to
be root, but if I run it as root, nobody else can see Jack unless they
are also root.
I wish somebody would write a Jack-HOWTO so dummies like me can figure
out how to run this thing.
Thanks
21 Apr
21 Apr
6:04 p.m.
Nick Tsocanos <nicktsocanos(a)charter.net> writes:
How can I make Jackd always run? Right now I have to
set it up in a
console window. I'd like to learn how to run it always at startup and
not have to start/stop it when I need it.
I don't think many people are doing it this way at the moment. But,
with realtime support and capabilities, it's just about at the point
where you might want to. Most current users of JACK are developers or
early adopters, who run it in an xterm or console window for debugging
reasons.
The best solution is probably to write an /etc/init.d/jackd script
with the usual start, stop, restart parameters. This would be
automatically invoked when changing runlevel using whatever mechanism
your distribution provides. The arguments to jackd would need to be
stored in come kind of config file that would be accessible to the
script.
I've thought about writing one, but haven't done it. If you do,
please post it to the jackit-devel list. Although it would be
somewhat distribution-specific, it would be helpful to distribute, at
least as an example.
Also how do you use Jack in real-time mode? In order
to run it I have to
be root, but if I run it as root, nobody else can see Jack unless they
are also root.
See http://jackit.sourceforge.net/docs/faq.php#a5
I wish somebody would write a Jack-HOWTO so dummies
like me can figure
out how to run this thing.
See http://www.djcj.org/LAU/jack/
HTH,
--
Jack O'Quin
Austin, Texas, USA
9:29 p.m.
Rather than having a startup script (somewhat inappropriately) read a
config file, shouldn't jackd implement a /etc/jackd.conf itself? Running
from the command line would be a cinch too then.
Of course, a /var/log/jack.log and/or syslog facility would be nice too
;)
I've just started setting up a demudi box and if I can stop my machine
from hanging, I'll do it myself - it'll give me a good excuse to start
browsing the source.
Darren
On Mon, 2003-04-21 at 12:54, Jack O'Quin wrote:
Nick Tsocanos <nicktsocanos(a)charter.net>
writes:
________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________
How can I make Jackd always run? Right now I have
to set it up in a
console window. I'd like to learn how to run it always at startup and
not have to start/stop it when I need it.
I don't think many people are doing it this way at the moment. But,
with realtime support and capabilities, it's just about at the point
where you might want to. Most current users of JACK are developers or
early adopters, who run it in an xterm or console window for debugging
reasons.
The best solution is probably to write an /etc/init.d/jackd script
with the usual start, stop, restart parameters. This would be
automatically invoked when changing runlevel using whatever mechanism
your distribution provides. The arguments to jackd would need to be
stored in come kind of config file that would be accessible to the
script.
I've thought about writing one, but haven't done it. If you do,
please post it to the jackit-devel list. Although it would be
somewhat distribution-specific, it would be helpful to distribute, at
least as an example.
Also how do you use Jack in real-time mode? In
order to run it I have to
be root, but if I run it as root, nobody else can see Jack unless they
are also root.
See http://jackit.sourceforge.net/docs/faq.php#a5
I wish somebody would write a Jack-HOWTO so
dummies like me can figure
out how to run this thing.
See http://www.djcj.org/LAU/jack/
HTH,
10:43 p.m.
Darren Warner <darren(a)dazwin.com> writes:
Rather than having a startup script (somewhat
inappropriately) read a
config file, shouldn't jackd implement a /etc/jackd.conf itself? Running
from the command line would be a cinch too then.
Of course, a /var/log/jack.log and/or syslog facility would be nice too
;)
I've just started setting up a demudi box and if I can stop my machine
from hanging, I'll do it myself - it'll give me a good excuse to start
browsing the source.
If you are serious about pursuing this idea, please discuss it first
on the jackit-devel list.
AFAICT, the JACK developers decided not to do this because they wanted
JACK to depend on the minimum number of libraries. Currently it
depends only on libc, libasound, and libcap (if capabilities enabled).
--
Jack O'Quin
Austin, Texas, USA
8:08 p.m.
<quote who="Nick Tsocanos">
Hello,
How can I make Jackd always run? Right now I have to set it up in a
console window. I'd like to learn how to run it always at startup and
not have to start/stop it when I need it.
I use an init script like this:
andy@xfc:/etc/init.d$ ls -l jackd
-rwxr-xr-x 1 root root 852 Mar 11 21:50 jackd
For a SysV-style init, (most linux distros), add a symlink to start it up
automatically for the default runlevel (2 is the default runlevel for a
debian system)...
root@xfc:/etc/rc2.d# runlevel
N 2
root@xfc:/etc/rc2.d# ls -l S20jackd
lrwxrwxrwx 1 root root 15 Apr 21 14:39 S20jackd ->
../init.d/jackd
To see what is going on, run this in a console:
# /etc/init.d/jackd monitor
I include LADCCAD in the init script also.
----------------------------------------------------------------
case $1 in
'start')
echo "Starting Jack Audio Server with period of 256 samples."
# LADCCAD ...
rm -f /var/log/ladccad.log
ladccad 1> /var/log/ladccad.log 2>&1 &
# Jack Audio Server
rm -f /var/log/jackd.log
jackd --realtime -v -d alsa -d hw:0 -r 44100 -p 256 \
1> /var/log/jackd.log 2>&1
;;
'stop')
echo "Stopping Jack Audio Server."
killall jackd
killall ladccad
;;
'restart')
$0 stop
$0 start
;;
'start-monitor')
$0 start
$0 monitor
;;
'monitor')
tail -f /var/log/jackd.log
;;
*)
echo "Usage $0 [start, stop, restart, monitor]"
;;
esac
----------------------------------------------------------------
The above script should be tweaked as necessary for your setup.
--aws
mailto:andy*a2hd,com
http://www.a2hd.com/
7883
days inactive
7883
days old
linux-audio-dev@lists.linuxaudio.org
4 comments
4 participants
participants (4)
-
Andy Schmeder -
Darren Warner -
Jack O'Quin -
Nick Tsocanos