On Thu 29 May 2003 17:04, Austin posted as excerpted below: > On 2003.05.29 18:30, Michael Scherer wrote: > > what about doing a script to launch jack, which mount a tmpfs on > > ~/.jack/tmp, and patch jack to use it ? > > Hmm, found that out fast. No can do. > ALL jack client applications look for jack fifo in /tmp. > Maybe jack will be patched in the future to 'redirect' them.
I'm sure someone will correct me if I'm wrong, or you can test and correct me then, but what about a symlink in /tmp to the previous mentioned home based subdir, which can be mounted anything you want? If I'm not incorrect, while the first access to the symlink might take a bit to spin up the disk (in the worst case scenario), after that, the symlink should be cached, and the system will only be looking in memory to see the redirect, and go from there to find the mounted tmpfs. One could even use the starter script as mentioned to recreate if necessary and access the symlink, so by the time jack itself starts, it's already in memory. If necessary, one could start the binary in the background then, and go into a loop, with a sleep 10 or whatever between accesses, just to make sure the symlink never goes out of cache, as it's always used every X seconds. BTW, if you DO use that wrapper script, it seems the various drak tools, when needed, use program.real rather than program.bin, for the real program. I'd probably be a good idea to follow that lead, and keep things as consistent as possible within the Mdk system. I don't know if it's formallized that way, or if other packages use .bin or not, but the Mdk drak tools I've seen use .real, so that's what I'd use. -- Duncan - List replies preferred. "They that can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." Benjamin Franklin
