I'm using set_rlimits to assign realtime privileges to users, but for some reason after a reboot today none of my users have rt access. I have the following line in /etc/set_rtlimits.conf:

That should equal all users that are part of the audio group getting rt privileges.

I'm using this way to have jackd with rt capabilities
http://permalink.gmane.org/gmane.com...o.jackit/22168

From http://slackbuilds.org/repository/13...onnection-kit/:

jackd has to run with realtime priviledges. One way to do this on Slackware
would be to use set_rlimits. Since 12.2 there's another way. If you have
a filesystem that supports posix capabilities (reiserfs does not), you
can grant jackd the rights to run in realtime mode, even when started as
normal user with the following command:

setcap cap_ipc_lock,cap_sys_nice=ep /usr/bin/jackd

The start of this thread got me wondering, as I run jack with RT privileges all the time, how I was doing it. The follow ups gave the answer.

I don't remember running setcap but it was some time ago and my memories not as good as once! Anyway, when I check with /sbin/getcap /usr/bin/jackd I get returned /usr/bin/jackd=cap_ipc_lock,cap_sys_nice+ep so I take it I must have set the file capabilites at some stage and that explains why it works for me.

I think I'll have to start making notes about all these little setups to help my failing recollection . Thanks for the reminder! I'm sure there's a moral here somewhere!

Anyway, I recomend taking the advice and just using setcap as it works for me and the others.

I'll probably do that, but I still want to know why set_rlimits failed... I HATE loose ends.

Ok, I'm with you on that so why not try running set_rlimits with the "-d" option and seeing if that gives any useful information. I have downloaded the source and set_rlimits.c is only 829 lines and just one source file involved. If you really want to get to the bottom of this you could try the debug output option and even strace'ing or gdb'ing the executable, (after debug compiling), to see what's going on. If you really want to know what's failing that's the way to do it but as there's a good alternative option I'd just use what works, to be honest. Also, I don't really like that set_rlimit appears to need setuid root privileges which always make me a bit nervous.

That's what I wound up doing... I simply don't have time to troubleshoot this right now; not when there's an easy workaround. Thanks, guys.