Sponsored Content
Full Discussion: v0.4 convenience release
Special Forums News, Links, Events and Announcements Software Releases - RSS News v0.4 convenience release Post 302259678 by dogfight148 on Tuesday 18th of November 2008 05:28:30 PM
Old 11-18-2008
hello

are You a bot?
 

We Also Found This Discussion For You

1. UNIX for Dummies Questions & Answers

difference between SunOS Release and Solaris Release

Whats the difference between Solaris Relase and SunOS Release?? (1 Reply)
Discussion started by: eloquent99
1 Replies
tuned.conf(5)						tuned.conf file format description					     tuned.conf(5)

NAME
tuned.conf - Tuned profile definition DESCRIPTION
This man page documents format of Tuned 2.0 profile definition files. 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. The tuned.conf configures the profile and it is in ini-file format. MAIN SECTION
The main section is called "[main]" and can contain following options: include= Includes config file defined as value. Config file can be defined as full path or by the profile name to which it belongs. If this parameter is present, the histogram will be shown at the end of the measurement. PLUGINS
Every other section defines one plugin. The name of the section is used as name for the plugin and is used in logs to identify the plugin. There can be only one plugin of particular type tuning particular device. Conflicts are by default fixed by merging the options of both plugins together. This can be changed by "replace" option. Every plugin section can contain following sections: type= Plugin type. Currently there are following plugins: disk, script, net, cpu, eeepc_she. devices= Comma separated list of devices which should be tuned by this plugin instance. If you omit this option, all found devices will be tuned. replace=1 If there is conflict between two plugins (meaning two plugins of the same type are trying to configure the same devices), then the plugin defined as last replaces all options defined by the previosly defined plugin. Plugins can also have plugin related options. EXAMPLE
[main] # Includes plugins defined in "included" profile. include=included # Define my_sysctl plugin [my_sysctl] type=sysctl # This plugin will replace any sysctl plugin defined in "included" profile replace=1 # 256 KB default performs well experimentally. net.core.rmem_default = 262144 net.core.wmem_default = 262144 # Define my_script plugin # Both scripts (profile.sh from this profile and script from "included" # profile) will be run, because if there is no "replace=1" option the # default action is merge. [my_script] type=script script=profile.sh SEE ALSO
tuned(8) AUTHOR
Written by Jan Kaluza <jkaluza@redhat.com>. REPORTING BUGS
Report bugs to <jkaluza@redhat.com>. Jan Kaluza 13 Mar 2012 tuned.conf(5)
All times are GMT -4. The time now is 08:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy