Em Wed, Apr 29, 2015 at 10:20:26AM -0500, Guy Streeter escreveu:
On 04/29/2015 10:14 AM, Arnaldo Carvalho de Melo wrote:
> Em Wed, Apr 29, 2015 at 10:46:36AM -0400, John Kacur escreveu:
>> Assuming that this is untested though?
> Tested, on a RHEL7 system, and that leads to another problem,
where the
> fact that there is nothing in /etc/tuna/ generates a messageDialog()
> saying that the config file is "corrupted", which is not the case, it
> should just start with default values, etc.
> But that is for another patch. Trying to figure out how to do
that, as
> this was done by somobody else, using some ConfigParser() python classes
> I am not familiar with.
> To repro the problem, just run tuna, as root, on a system with
nothing on
> /etc/tuna/, it should produce the Dialog, and will freeze the screen,
> with nothing on the tuna panes, till the user presses Ok.
I don't know why that configuration stuff was tacked onto tuna.
It's the
reason tuna has to run as root now. I think it would be better if we just
had a button that launched a separate configuration app.
Was part of a integration with tuned, approved/requested by management
at Red Hat.
And yes, it is sad that the GUI now goes thru that sequence that ends up
asking for 'root' priviledges to be granted.
On the command line, tho, it works as before, subject to the permissions
enforced by the kernel to /proc, ethtool, schedutils, etc.
[acme@ssdandy ~]$ tuna -t docker -CP
thread ctxt_switches
pid SCHED_ rtpri affinity voluntary nonvoluntary cmd
1101 OTHER 0 0xff 634 140 docker
1538 OTHER 0 0xff 30 0 docker
1125 OTHER 0 0xff 7215 4 docker
1126 OTHER 0 0xff 3 3 docker
2152 OTHER 0 0xff 7241 1 docker
1258 OTHER 0 0xff 4 0 docker
1105 OTHER 0 0xff 30227 2 docker
1170 OTHER 0 0xff 14205 7 docker
[acme@ssdandy ~]$
I think this should be changed so that it works as before, i.e. as
non-root user one can use the GUI, and whatever operations that requires
root priviledges should be presented only if those priviledges are
available.
- Arnaldo