> On Wed, Jun 25, 2008 at 09:50, François Revol <revol@xxxxxxx> wrote: > > I think meant RT prio vs non-root. > > RT priority threads can hog the system, which shouldn't be doable > > by a > > user. > > Actually it doesn't make much sense for a user that's not sitting on > the console to be allowed anything above B_NORMAL_PRIORITY (as its > priority value is 10, and B_DISPLAY_PRIORITY is quite close at 15). Just like Linux forbids non root to use negative nice even outside the RT class. > > There I think some capability based system should help. > > Definitely. And there's already some groundwork laid on the scheduler > for this to be pretty easy to implement. > > > When logging in a user would just be granted the RT cap for his > > session. > > Well, this doesn't require a full-blown capability model like > scheduling groups, but it sure is a nice workaround ;) Well other things like allowed mounting, using devices (scanner, printers...), ... should be done by users at the console. François.