Hi! First: I'm going to reassign this bug to libpam-modules, since /etc/security/limits.conf isn't owned by jackd.
Second: There's usually no need to limit the size of the maximum locked memory. Actually, some programs (ardour?) even print a warning if you do so. Third: with realtime prio, I've never seen the need for special nice levels, so there's probably no use (but danger) in including a nice-line. Anyway, I'm not an expert in this field. Suggestion: add these two lines to limits.conf: @audio - memlock 0 @audio - rtprio 99 IIRC, that's what Ubuntu does. If you want more fine-grained control, add a realtime group and change "@audio" to "@realtime". For most desktop users, realtime audio would be a common case (Fedora does this for pulseaudio), but there might also be non-audio users interested in realtime priorities (think of industry PCs) HTH -- mail: a...@thur.de http://adi.thur.de PGP/GPG: key via keyserver -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org