Re: [linux-audio-user] jackd and /tmp

Paul Davis wrote:
> 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:
>>
>>> 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)...
>>>
>> 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.
>>
>
> 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
>
>
>
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
Received on Tue Mar 13 04:15:02 2007