From: Carsten Haitzler (The Rasterman) <raster@rasterman.com>
To: Stanislav Brabec <utx@penguin.cz>
Cc: Koen Kooi <k.kooi@student.utwente.nl>,
openembedded-devel@lists.openembedded.org
Subject: Re: Requiring root access for windowmanagers?
Date: Sun, 30 Nov 2008 08:39:34 +1100 [thread overview]
Message-ID: <20081130083934.d9ee3e4e.raster@rasterman.com> (raw)
In-Reply-To: <20081129215247.52c40a2b@zaurus>
On Sat, 29 Nov 2008 21:52:47 +0100 Stanislav Brabec <utx@penguin.cz> babbled:
> Sat, 29 Nov 2008 01:04:22 +1100
> Carsten Haitzler (The Rasterman) wrote:
>
> > On Fri, 28 Nov 2008 13:20:12 +0100 Koen Kooi
> > <k.kooi@student.utwente.nl> babbled:
>
> > > What's the consensus on requiring root access for running an OE
> > > built windowmanager?
> > >
> > > Case in point: e-wm does 'renice -10', which only root is allow to
> > > do.
> > >
> > > Proposal: remove the 'renice' so regular users can start a window
> > > manager as well.
> >
> > i did this specifically for performance. basically it makes things
> > MUCH smoother.
>
> I understand your trick - I do the same with video player if I want to
> compile in parallel with DVD playback.
>
> Running WM as root would increase any security hole to root access flaw.
> I can see cleaner solutions:
as such though.. the openmoko distro runs everything as root - that's why i
really look at it and went "well.. in this case it'd work - for other cases
where its not root - well. no thing will break but you get no benefit".
> 1. Write a small SUID wrapper. Change priority, drop permissions, run
> window manager.
sure. shouldn't be hard. i have one of these for playing with the realtime
scheduler (eg set scheduler to FIFO... this is fun for benchmarking!)
> 2. Run WM as root and drop privileges after setting priority.
wm would need code internally for this. this is possible. E already runs
sub-process at nice +1 so anything it launches will be of lower priority than
the wm (we can argue pros and cons forever and a day - but imho this is the
right thing. the managing infra here should get top priority for app switching,
launching feedback etc. etc.).
> 3. Use capabilities and enable CAP_SYS_NICE.
never touched this.
> 4. And finally, the best solution may be a different kernel scheduler.
> But I don't follow the development there, so I don't know, whether
> there is possible to find a good solution: "This process does not eat a
> much CPU time, but it wants fast processing".
that's pretty much everything :) the question is... when more than 1 of these
want the cpu "now"... who get's first-pick :)
as it is right now - non-root wm's don't break. they simply don't get a higher
priority. so this is relatively harmless. it just is non-beneficial for
non-root. the question is more - is there an agreement that this is a good
thing to do at all. i'd also argue X should be reduced in nice value (higher
priority) too so all refreshing, drawing, etc. takes priority over back-end
processing by apps.
--
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler) raster@rasterman.com
prev parent reply other threads:[~2008-11-29 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 12:20 Requiring root access for windowmanagers? Koen Kooi
2008-11-28 13:26 ` Koen Kooi
2008-11-28 14:04 ` Carsten Haitzler
2008-11-29 20:52 ` Stanislav Brabec
2008-11-29 21:39 ` Carsten Haitzler [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081130083934.d9ee3e4e.raster@rasterman.com \
--to=raster@rasterman.com \
--cc=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=utx@penguin.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox