12 Mar
2007
12 Mar
'07
3:57 p.m.
Hi (again)
I'm a little baffled about the fact that jackd reports it expects to use
/tmp, which I imagine should be of type tmpfs. Should I do something
about it (if so, what)?
atte@ajstrup:~$ jackd -V
jackd version 0.102.20 tmpdir /tmp protocol 16
atte@ajstrup:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hda2 19G 9,7G 7,8G 56% /
tmpfs 506M 0 506M 0% /lib/init/rw
udev 10M 88K 10M 1% /dev
tmpfs 506M 0 506M 0% /dev/shm
/dev/hda4 54G 43G 7,6G 86% /mnt/data
/dev/hda1 19G 15G 3,1G 83% /mnt/unstable
--
peace, love & harmony
Atte
http://www.atte.dk | quintet: http://www.anagrammer.dk
| compositions: http://www.atte.dk/compositions
12 Mar
12 Mar
4 p.m.
On 3/12/07, Atte André Jensen <atte.jensen(a)gmail.com> wrote:
Hi (again)
I'm a little baffled about the fact that jackd reports it expects to use
/tmp, which I imagine should be of type tmpfs. Should I do something
about it (if so, what)?
Yes - compile it to use /dev/shm.
Lee
4:48 p.m.
Lee Revell wrote:
Yes - compile it to use /dev/shm.
I'm doing that as I type.
But shouldn't that be possible to specofy as an runtime option? "jackd
--help" seems to suggest no, however the name of the config option
"--with-default-tmpdir" suggests that is merely a default dir hence that
some other dir can be specified later (=at runtime)...
--
peace, love & harmony
Atte
http://www.atte.dk | quintet: http://www.anagrammer.dk
| compositions: http://www.atte.dk/compositions
5:10 p.m.
On Mon, Mar 12, 2007 at 08:48:14PM +0100, Atte André Jensen wrote:
Lee Revell wrote:
When you build jack you are building both jackd, the server, and
libjack, the library that clients use to talk to the server. Both need
to know where the tmpdir lives because they use it to communicate with
each other. Hence, it is a compile time option.
-Eric Rz.
Yes - compile it to use /dev/shm.
I'm doing that as I type.
But shouldn't that be possible to specofy as an runtime option? "jackd
--help" seems to suggest no, however the name of the config option
"--with-default-tmpdir" suggests that is merely a default dir hence that
some other dir can be specified later (=at runtime)...
6:12 p.m.
On 3/12/07, Eric Dantan Rzewnicki <eric(a)zhevny.com> wrote:
On Mon, Mar 12, 2007 at 08:48:14PM +0100, Atte André
Jensen wrote:
I think the process could be improved by defaulting to /dev/shm if it
exists then falling back to /tmp otherwise. There are (old) systems
without /dev/shm, but I have not seen any where /dev/shm exists but is
not a tmpfs.
Lee
Lee Revell wrote:
When you build jack you are building both jackd, the server, and
libjack, the library that clients use to talk to the server. Both need
to know where the tmpdir lives because they use it to communicate with
each other. Hence, it is a compile time option. Yes - compile it to use /dev/shm.
I'm doing that as I type.
But shouldn't that be possible to specofy as an runtime option? "jackd
--help" seems to suggest no, however the name of the config option
"--with-default-tmpdir" suggests that is merely a default dir hence that
some other dir can be specified later (=at runtime)... 
6:29 p.m.
On Mon, 2007-03-12 at 16:10 -0400, Eric Dantan Rzewnicki wrote:
On Mon, Mar 12, 2007 at 08:48:14PM +0100, Atte André
Jensen wrote:
actually, not any more. as of 0.103, clients determine where the
directory by invoking jackd -l (you can try it yourself). however, this
doesn't help much, since you could easily do this:
% jackd --tmpdir=/foo/bar & // successful startup
% someJackClient
[ ... runs jackd -l .... ]
[ ... gets default answer, not /foo/bar ... ]
so, the change in discovery technique notwithstanding, Eric's point is
still fundamentally correct.
--p
Lee Revell wrote:
When you build jack you are building both jackd, the server, and
libjack, the library that clients use to talk to the server. Both need
to know where the tmpdir lives because they use it to communicate with
each other. Hence, it is a compile time option. Yes - compile it to use /dev/shm.
I'm doing that as I type.
But shouldn't that be possible to specofy as an runtime option? "jackd
--help" seems to suggest no, however the name of the config option
"--with-default-tmpdir" suggests that is merely a default dir hence that
some other dir can be specified later (=at runtime)... 
11:04 p.m.
Paul Davis wrote:
On Mon, 2007-03-12 at 16:10 -0400, Eric Dantan
Rzewnicki wrote:
so here jack is compiled with:
'tmpdir /mnt/ramfs protocol 16'
and it runs good actually!
is it appropriate way to install ' --with-default-tmpdir=/dev/shm'?
please allow me another question: what is the 'protocol 16' meaning?
cheers,
doc
On Mon, Mar 12, 2007 at 08:48:14PM +0100, Atte
André Jensen wrote:
actually, not any more. as of 0.103, clients determine where the
directory by invoking jackd -l (you can try it yourself). however, this
doesn't help much, since you could easily do this:
% jackd --tmpdir=/foo/bar & // successful startup
% someJackClient
[ ... runs jackd -l .... ]
[ ... gets default answer, not /foo/bar ... ]
so, the change in discovery technique notwithstanding, Eric's point is
still fundamentally correct.
--p
Lee Revell wrote:
When you build jack you are building both jackd, the server, and
libjack, the library that clients use to talk to the server. Both need
to know where the tmpdir lives because they use it to communicate with
each other. Hence, it is a compile time option.
Yes - compile it to use /dev/shm.
I'm doing that as I type.
But shouldn't that be possible to specofy as an runtime option? "jackd
--help" seems to suggest no, however the name of the config option
"--with-default-tmpdir" suggests that is merely a default dir hence that
some other dir can be specified later (=at runtime)...
13 Mar
13 Mar
9:04 a.m.
On Tue, Mar 13, 2007 at 03:07:39AM +0100, Dragan Noveski wrote:
Paul Davis wrote:
iiuc that is the version number of the protocol jack and its clients use
to communicate via the FIFOs in tmpdir.
-Eric Rz.
On Mon, 2007-03-12 at 16:10 -0400, Eric Dantan
Rzewnicki wrote:
so here jack is compiled with:
'tmpdir /mnt/ramfs protocol 16'
and it runs good actually!
is it appropriate way to install ' --with-default-tmpdir=/dev/shm'?
please allow me another question: what is the 'protocol 16' meaning?
6540
days inactive
6541
days old
linux-audio-user@lists.linuxaudio.org
7 comments
5 participants
participants (5)
-
Atte André Jensen -
Dragan Noveski -
Eric Dantan Rzewnicki -
Lee Revell -
Paul Davis