6 Feb
2006
6 Feb
'06
10:51 p.m.
On 2/6/06, Lee Revell <rlrevell(a)joe-job.com> wrote:
On Mon, 2006-02-06 at 21:30 -0500, Lee Revell wrote:
Great work, Lee! Question, did the patch have "rt_prio" or "rtprio"
in
it? Not sure if you saw my other email about it, but the official PAM
has "rtprio" and most patches I saw out there had "rt_prio" in one
place, but "rtprio" in another (in the README).
By default, you are in the audio group, so I would propose a realtime
group. It makes sense anyhow, since that's what it is for. Also, the
recommendations I saw elsewhere said rtprio = 99 (some say 100, but
looking at the patch, 99 is the max), nice -10, and memlock I am not
sure about. I set mine to 250000, but others put 4000000 even.
On another note.. I hope that the new Ardour 0.99.1 gets into Dapper
too. It has a lot of maintenance fixes.
Dana
On Sat, 2006-02-04 at 15:49 -0500, Dana Olson
wrote:
Since it looks like this is happening the next question is, what do we
thing is a sane default config.
IMHO it needs to be secure OOTB, but we don't want to make users
edit /etc/security/limits.conf, I propose that we
ship /etc/security/limits.conf with the "audio" group set up for
realtime access, but do not add the default user to this group at
install time.
If Ubuntu already places the default user in group "audio", I think we
need to use another group "realtime".
So all that's needed for JACK in realtime mode is "gpasswd -a joeuser
realtime".
There might also be a good argument that we *do* want to allow realtime
access to the default user...
Lee
I hope you can get this into Breezy. There is a discussion on this
page as well, where I learned the steps from:
It's looking good - Matt Zimmermann has instructed the Ubuntu developers
to review and merge the patches.