Bug 1212836

Cause: Previously there was no way to verify that the profile was successfully applied and that the current system settings match the settings requested in the Tuned profile. Consequence: There may happen various events diverting the current system settings from the settings requested in Tuned profile, e.g. some tools could change some system settings when Tuned is running or new devices which was not recognized by Tuned hotplug could be added. And system administrator couldn't be sure that everything is correctly set. The only thing she/he could do was to reapply the current Tuned profile which is not optimal approach, because it may introduce some transient effects (due to rolling back and reapplying the settings) Fix: The 'verify' command was added to the tuned-adm. Result: It is now possible to verify whether the current system settings match the settings requested in the Tuned profile by: # tuned-adm verify It returns with exitcode 0 if everything is OK, or 1 if there is some problem. Simultaneously it writes to Tuned log what is checked, what is the current value and what is the value expected. If script is used in Tuned profile, it is called with the 'verify' argument during verification and its exit code is checked.