[Bug 831619] Inaccuracy in Fedora 17 “Power Management Guide”

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=831619

Jack Reed <jreed at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |needinfo?(jskarvad at redhat.c
                   |                            |om)

--- Comment #1 from Jack Reed <jreed at redhat.com> ---
Hi Vasil,

Thanks for reporting these issues with the tuned documentation and for your
praise of the PMG. Much appreciated. :)

I'll respond point by point, and consult Jaroslav Skarvada for technical
assistance on a few of them.

>   In section “2.5. Tuned and ktune” right bellow the “yum install tuned”
> command it's written:
> 
> “Installing the tuned package also sets up a sample configuration file at
> /etc/tuned.conf and activates the default profile.” 
> There is no such file in /etc. I found a /etc/tuned/active_profile file
> containing the following: “/usr/lib/tuned/balanced/tuned.conf”. I'm not sure
> this file (/etc/tuned.conf) is missing only on my system or it has a new
> location by default for each profile - /usr/lib/tuned/profileX/tuned.conf.
> Bellow in this section and in  “2.5.1. The tuned.conf file” it is pointed
> again that the default location for the tuned.conf file is /etc/tuned.conf.

The current man page for tuned.conf says "Profile is stored in
/etc/tuned/<profile_name>/tuned.conf or in
/usr/lib/tuned/<profile_name>/tuned.conf file where the  /etc/tuned/  directory
has higher priority."

On my machine, tuned.conf is in /usr/lib/... . 

Jaroslav, what does "where the  /etc/tuned/  directory has higher priority"
mean? Does this mean both paths will need to be documented? That's fine, but I
would like a better idea of why there are two paths, because that wording is
unclear.


> In section “2.5.2 Tuned-adm” in the first paragraph it is written “Fedora 17
> includes a number of predefined profiles for typical use cases...”. Just to
> be precise it is good to be mentioned that these profiles are not installed
> by default with “yum install tuned” command (tuned-2.0.1-1.fc17 package),
> but can be found in tuned-profile-compat-2.0.1-1.fc17 package (I found it in
> Gnome Package Manager). 

No problem, Vasil. I will list which profiles are available in which package,
and document the new ones.


> Another thing in this section is in the last third of the page where it is
> written:
> “All the profiles are stored in separate subdirectories under
> /etc/tune-profiles. So /etc/tune-profiles/desktop-powersave contains all the
> necessary files and settings for that profile. Each of these directories
> contains up to four files:”
> There /etc/tune-profiles directory does not exist. Instead I found the
> profiles stored in /run/lib/tuned.
> Each directory for the corresponding profile typically contains only 2 files
> - script.sh and tuned.conf. The presence of script.sh is not mentioned in
> the directories contains description – it is mentioned ktune.sh insetad.

Jaroslav, I've confirmed this on my own machine. (See the end of section
2.5.2.) 

Has script.sh replaced ktune.sh? If not, can you describe this file's purpose? 

And will sysctl.ktune and ktune.sysconfig never be present and no longer need
to be documented?


Also, Jaroslav, I'm trying to update the documentation of tuned.conf (section
2.5.1). The man page suggests that the options available for the [main] and
plugin sections have changed.

For [main], the man page only lists include= . For plugins, the man page lists:
- type=
- devices=
- replace=1

Currently the PMG lists the following for [main]: interval, verbose, logging,
and logging_disable.

For plugins, it lists: enabled, verbose, and logging

My question is, are the options the PMG currently lists still available and
have just been joined by those in the man page? Or have they been deprecated?

My tuned.conf files are fairly minimal so I can't tell if any of these options
remain available.

Thanks in advance.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.