On 4/21/06, Tim Howard <tdhoward@xxxxxxxxx> wrote: > Lee Revell wrote: > >On Fri, 2006-04-21 at 16:44 +0100, James McDermott wrote: > >> Yes, latency is still a big issue regardless of how many tracks are > >> involved. You need to search the (recent) archives of this list, and > >> the FC5 docs, for set_rtlimits, PAM, and the kernel version number. > >> You can get good low latency performance with a recent mainstream > >> kernel, they say! > >> > >> Also, you'll have to do some reading to see what packages will be > >> available to you, and what you'll have to compile yourself. > > > >set_rtlimits should be completely unnecessary on FC5 as it has a new > >enough version of PAM. > > OK, last night I did a test install of FC5 as an upgrade to my > FC3+planet installation. > If I log in as root, Jack is in realtime mode, and can't overload my > system enough to cause even one xrun. But when I am logged in as a > normal user, Jack doesn't run in realtime mode, and I get xruns even > on playback. > > Is this caused by something PAM related? (Forgive me, I am a relative newbie) You probably need something like this in /etc/security/limits.conf # restrict realtime scheduling and memory locking to audio group @audio - rtprio 80 @audio - memlock 300000 Then, put yourself in group "audio", log out and log in again. Assuming PAM is properly patched, I think that should work. -- joq
