rainbow and pam

[Michael Stone]

According to "man sched_setscheduler" you want either CAP_SYS_NICE or a
non-zero RLIMIT_RTPRIO and giving these to you means that you can
hardlock the machine anytime by busywaiting. Audio performance is
clearly important to us in this release -- probably more important than
stopping random malicious activities from locking the machine -- so that
means that I should probably help you out on the condition that we may
need to revise the details of our arrangements in future releases.

Is that acceptable?

If so, I propose simply granting all activities an RLIMIT_RTPRIO rlimit
of some made-up number... say 50?

Anyone have better ideas?

(Note that there is a facility for setting per-bundle rlimits that we
could probably adapt, but it's not very well tested...) 

Michael