14 Feb
2006
14 Feb
'06
5:44 p.m.
On Mon, 2006-02-13 at 21:04 -0500, Ross Vandegrift wrote:
On Sun, Feb 12, 2006 at 08:52:30PM -0500, Lee Revell
wrote:
I may be missing something here but, why would you run your window
manager as the same user that you use to run RT applications? I
normally log in as Joe_User and then start my applications as a
privileged user (in my case root because I'm lazy ;-) In most window
managers/desktops it is pretty easy to start an app as a different user
with a desktop icon. The only PITA is that you have to enter a password
to start the apps but you only do that once so it's not a big problem.
--
Jan 'Evil Twin' Depner
The Fuzzy Dice
http://myweb.cableone.net/eviltwin69/fuzzy.html
"As we enjoy great advantages from the invention of others, we should be
glad of an opportunity to serve others by any invention of ours, and
this we should do freely and generously."
Benjamin Franklin, on declining patents offered by the governor of
Pennsylvania for his "Pennsylvania Fireplace", c. 1744
No, it's not that bad, but IMHO it's more
of a pain than the realtime
LSM, or the PAM solution.
Does a process inherit its parent's RT rlimits? I would expect them
to work that way. If so, it should be enough to run your display or
window manager under set_rlimits. Then, any app you started in that X
session would automatically inherit the ability to request RT
scheduling and mlock pages.