On 2/14/06, Jan Depner <eviltwin69@email-addr-hidden> wrote:
> 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:
> > > 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.
>
> 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
First of all, I'm sure you understand that running applications as
root is a security risk and not recommended...
Secondly, if you run as root, you don't need a patched PAM or set_rlimits..
Dana
Received on Wed Feb 15 08:15:05 2006
This archive was generated by hypermail 2.1.8 : Wed Feb 15 2006 - 08:15:05 EET