Messages in this thread |  | | | Subject | Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?) | | From | Lee Revell <> | | Date | Mon, 23 Jan 2006 16:30:28 -0500 |
| |
On Mon, 2006-01-23 at 22:21 +0100, Matthias Andree wrote: > On Mon, 23 Jan 2006, Lee Revell wrote: > > > You will be happy to know that in future Linux distros, cdrecord will > > not require setuid to mlock() and get SCHED_FIFO - both are now > > controlled by rlimits, so if the distro ships with a sane PAM/group > > configuration, all you will need to do is add cdrecord users to the > > "realtime" or "cdrecord" or "audio" group. > > Sounds really good. Can you give a pointer as to the detailed rlimit > requirements?
One thing I believe is still unresolved is that despite the new rlimits, sched_get_priority_max(SCHED_FIFO) always returns 99 rather than RLIMIT_RTPRIO.
Lee
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |