1yum.conf(5) yum configuration file yum.conf(5)
2
6 yum.conf - Configuration file for yum(8).
7
9 Yum uses a configuration file at /etc/yum.conf.
10 Additional configuration files are also read from the directories set
12 by the reposdir option (default is `/etc/yum.repos.d'). See the repos‐
13 dir option below for further details.
14
17 There are two types of sections in the yum configuration file(s): main
18 and repository. Main defines all global configuration options. There
19 should be only one main section. The repository section(s) define the
20 configuration for each repository/server. There should be one or more
21 repository sections.
22
25 The [main] section must exist for yum to do anything. It consists of
26 the following options:
27 cachedir Directory where yum should store its cache and db
30 files. The default is `/var/cache/yum'.
31 persistdir Directory where yum should store information that
34 should persist over multiple runs. The default is
35 `/var/lib/yum'.
36 keepcache Either `1' or `0'. Determines whether or not yum keeps
39 the cache of headers and packages after successful installation.
40 Default is '1' (keep files)
41 reposdir A list of directories where yum should look for .repo
44 files which define repositories to use. Default is
45 `/etc/yum.repos.d'. Each file in this directory should contain
46 one or more repository sections as documented in [repository]
47 options below. These will be merged with the repositories
48 defined in /etc/yum.conf to form the complete set of reposito‐
49 ries that yum will use.
50 debuglevel Debug message output level. Practical range is 0-10.
53 Default is `2'.
54 errorlevel Error message output level. Practical range is 0-10.
57 Default is `2'.
58 rpmverbosity Debug scriptlet output level. 'info' is the
61 default, other options are: 'critical', 'emergency', 'error',
62 'warn' and 'debug'.
63 protected_packages This is a list of packages that yum should
66 never completely remove. They are protected via Obsoletes as
67 well as user/plugin removals.
68 The default is: yum glob:/etc/yum/protected.d/*.conf So any
70 packages which should be protected can do so by including a file
71 in /etc/yum/protected.d with their package name in it.
72 Also if this configuration is set to anything, then yum will
74 protect the package corresponding to the running version of the
75 kernel.
76 protected_multilib Either `1' or `0'. This tells yum whether or
79 not it should perform a check to make sure that multilib pack‐
80 ages are the same version. For example, if this option is off
81 (rpm behavior) then in some cases it might be possible for
82 pkgA-1.x86_64 and pkgA-2.i386 to be installed at the same time.
83 However this is very rarely desired. Install only packages, like
84 the kernel, are exempt from this check. The default is `1'.
85 logfile Full directory and file name for where yum should write
88 its log file.
89 gpgcheck Either `1' or `0'. This tells yum whether or not it
92 should perform a GPG signature check on packages. When this is
93 set in the [main] section it sets the default for all reposito‐
94 ries. The default is `0'.
95 localpkg_gpgcheck Either `1' or `0'. This tells yum whether or
97 not it should perform a GPG signature check on local packages
98 (packages in a file, not in a repositoy). The default is `0'.
99 repo_gpgcheck Either `1' or `0'. This tells yum whether or not
102 it should perform a GPG signature check on the repodata. When
103 this is set in the [main] section it sets the default for all
104 repositories. The default is `0'.
105 skip_broken Either `1' or `0'. Resolve depsolve problems by
108 removing packages that are causing problems from the transac‐
109 tion.
110 assumeyes Either `1' or `0'. Determines whether or not yum
113 prompts for confirmation of critical actions. Default is `0' (do
114 prompt).
115 Command-line option: -y --assumeyes
116 assumeno Either `1' or `0'. If yum would prompt for confirmation
119 of critical actions, assume the user chose no. This is basically
120 the same as doing "echo | yum ..." but is a bit more usable.
121 This option overrides assumeyes, but is still subject to
122 alwaysprompt. Default is `0' (do prompt).
123 Command-line option: --assumeno
124 alwaysprompt Either `1' or `0'. Without this option, yum will
127 not prompt for confirmation when the list of packages to be
128 installed exactly matches those given on the command line.
129 Unless assumeyes is enabled, it will still prompt for package
130 removal, or when additional packages need to be installed to
131 fulfill dependencies. Default is `1'.
132 tolerant Either `1' or `0'. If enabled, then yum will be toler‐
135 ant of errors on the command line with regard to packages. For
136 example: if you request to install foo, bar and baz and baz is
137 installed; yum won't error out complaining that baz is already
138 installed. Default to `0' (not tolerant). Note: This option
139 currently does nothing.
140 Command-line option: -t
141 exclude List of packages to exclude from updates or installs.
144 This should be a space separated list. Shell globs using wild‐
145 cards (eg. * and ?) are allowed.
146 query_install_excludes This applies the command line --exclude
149 option (only, not the configuration exclude above) to installed
150 packages being shown in some query commands (currently:
151 list/info/search/provides). Default is `0'.
152 exactarch Either `1' or `0'. Set to `1' to make yum update only
155 update the architectures of packages that you have installed.
156 ie: with this enabled yum will not install an i686 package to
157 update an i386 package. Default is `1'.
158 installonlypkgs List of package provides that should only ever
161 be installed, never updated. Kernels in particular fall into
162 this category. Defaults to kernel, kernel-bigmem, kernel-enter‐
163 prise, kernel-smp, kernel-debug, kernel-unsupported, kernel-
164 source, kernel-devel, kernel-PAE, kernel-PAE-debug.
165 Note that because these are provides, and not just package
167 names, kernel-devel will also apply to kernel-debug-devel, etc.
168 Note that "kernel-modules" is not in this list, in RHEL-6, and
170 so anything providing that is updated like any other package.
171 installonly_limit Number of packages listed in installonlypkgs
174 to keep installed at the same time. Setting to 0 disables this
175 feature. Default is '3'. Note that this functionality used to be
176 in the "installonlyn" plugin, where this option was altered via
177 tokeep. Note that as of version 3.2.24, yum will now look in
178 the yumdb for a installonly attribute on installed packages. If
179 that attribute is "keep", then they will never be removed.
180 kernelpkgnames List of package names that are kernels. This is
183 really only here for the updating of kernel packages and should
184 be removed out in the yum 2.1 series.
185 showdupesfromrepos Either `0' or `1'. Set to `1' if you wish to
188 show any duplicate packages from any repository, from package
189 listings like the info or list commands. Set to `0' if you want
190 only to see the newest packages from any repository. Default is
191 `0'.
192 obsoletes This option only has affect during an update. It
195 enables yum's obsoletes processing logic. Useful when doing dis‐
196 tribution level upgrades. See also the yum upgrade command docu‐
197 mentation for more details (yum(8)). Default is `true'.
198 Command-line option: --obsoletes
199 overwrite_groups Either `0' or `1'. Used to determine yum's be‐
202 haviour if two or more repositories offer the package groups
203 with the same name. If overwrite_groups is `1' then the group
204 packages of the last matching repository will be used. If over‐
205 write_groups is `0' then the groups from all matching reposito‐
206 ries will be merged together as one large group.
207 groupremove_leaf_only Either `0' or `1'. Used to determine yum's
210 behaviour when the groupremove command is run. If groupre‐
211 move_leaf_only is `0' (default) then all packages in the group
212 will be removed. If groupremove_leaf_only is `1' then only
213 those packages in the group that aren't required by another
214 package will be removed.
215 enable_group_conditionals Either `0' or `1'. Determines whether
218 yum will allow the use of conditionals packages. Default is `1'
219 (package conditionals are allowed).
220 group_package_types List of the following: optional, default,
223 mandatory. Tells yum which type of packages in groups will be
224 installed when 'groupinstall' is called. Default is: default,
225 mandatory
226 installroot Specifies an alternative installroot, relative to
229 which all packages will be installed.
230 Command-line option: --installroot
231 distroverpkg The package used by yum to determine the "version"
234 of the distribution. This can be any installed package. Default
235 is `redhat-release'. You can see what provides this manually by
236 using: "yum whatprovides redhat-release".
237 diskspacecheck Either `0' or `1'. Set this to `0' to disable the
240 checking for sufficient diskspace before a RPM transaction is
241 run. Default is `1' (perform the check).
242 tsflags Comma or space separated list of transaction flags to
245 pass to the rpm transaction set. These include 'noscripts',
246 'notriggers', 'nodocs', 'test', 'justdb' and 'nocontexts'.
247 'repackage' is also available but that does nothing with newer
248 rpm versions. You can set all/any of them. However, if you
249 don't know what these do in the context of an rpm transaction
250 set you're best leaving it alone. Default is an empty list.
251 recent Number of days back to look for `recent' packages added
254 to a repository. Used by the list recent command. Default is
255 `7'.
256 retries Set the number of times any attempt to retrieve a file
259 should retry before returning an error. Setting this to `0'
260 makes yum try forever. Default is `10'.
261 keepalive Either `0' or `1'. Set whether HTTP keepalive should
264 be used for HTTP/1.1 servers that support it. This can improve
265 transfer speeds by using one connection when downloading multi‐
266 ple files from a repository. Default is `1'.
267 timeout Number of seconds to wait for a connection before timing
270 out. Defaults to 30 seconds. This may be too short of a time for
271 extremely overloaded sites.
272 http_caching Determines how upstream HTTP caches are instructed
275 to handle any HTTP downloads that Yum does. This option can take
276 the following values:
277 `all' means that all HTTP downloads should be cached.
279 `packages' means that only RPM package downloads should be
281 cached (but not repository metadata downloads).
282 `none' means that no HTTP downloads should be cached.
284 The default is `all'. This is recommended unless you are experi‐
286 encing caching related issues. Try to at least use `packages' to
287 minimize load on repository servers.
288 throttle Enable bandwidth throttling for downloads. This option
291 can be expressed as a absolute data rate in bytes/sec. An SI
292 prefix (k, M or G) may be appended to the bandwidth value (eg.
293 `5.5k' is 5.5 kilobytes/sec, `2M' is 2 Megabytes/sec).
294 Alternatively, this option can specify the percentage of total
296 bandwidth to use (eg. `60%'). In this case the bandwidth option
297 should be used to specify the maximum available bandwidth.
298 Set to `0' to disable bandwidth throttling. This is the default.
300 bandwidth Use to specify the maximum available network bandwidth
303 in bytes/second. Used with the throttle option (above). If
304 throttle is a percentage and bandwidth is `0' then bandwidth
305 throttling will be disabled. If throttle is expressed as a data
306 rate (bytes/sec) then this option is ignored. Default is `0' (no
307 bandwidth throttling).
308 ftp_disable_epsv This options disables Extended Passive Mode
311 (the EPSV command) which does not work correctly on some buggy
312 ftp servers. Default is `0' (EPSV enabled).
313 sslcacert Path to the directory containing the databases of the
316 certificate authorities yum should use to verify SSL certifi‐
317 cates. Defaults to none - uses system default
318 sslverify Boolean - should yum verify SSL certificates/hosts at
321 all. Defaults to True.
322 Note that the plugin yum-rhn-plugin will force this value to
324 true, and may alter other ssl settings (like hostname checking),
325 even if it the machine is not registered.
326 sslclientcert Path to the SSL client certificate yum should use
329 to connect to repos/remote sites Defaults to none.
330 Note that if you are using curl compiled against NSS (default in
332 Fedora/RHEL), curl treats sslclientcert values with the same
333 basename as _identical_. This version of yum will check that
334 this isn't true and output an error when the repositories "foo"
335 and "bar" violate this, like so:
336 sslclientcert basename shared between foo and bar
338 sslclientkey Path to the SSL client key yum should use to con‐
341 nect to repos/remote sites Defaults to none.
342 ssl_check_cert_permissions Boolean - Whether yum should check
345 the permissions on the paths for the certificates on the reposi‐
346 tory (both remote and local). If we can't read any of the files
347 then yum will force skip_if_unavailable to be true. This is
348 most useful for non-root processes which use yum on repos. that
349 have client cert files which are readable only by root.
350 Defaults to True.
351 history_record Boolean - should yum record history entries for
354 transactions. This takes some disk space, and some extra time in
355 the transactions. But it allows how to know a lot of information
356 about what has happened before, and display it to the user with
357 the history info/list/summary commands. yum also provides the
358 history undo/redo commands. Defaults to True.
359 Note that if history is recorded, yum uses that information to
361 see if any modifications to the rpmdb have been done outside of
362 yum. These are always bad, from yum's point of view, and so yum
363 will issue a warning and automatically run some of "yum check"
364 to try and find some of the worst problems altering the rpmdb
365 might have caused.
366 This means that turning this option off will stop yum from being
368 able to detect when the rpmdb has changed and thus. it will
369 never warn you or automatically run "yum check". The problems
370 will likely still be there, and yumdb etc. will still be wrong
371 but yum will not warn you about it.
372 history_record_packages This is a list of package names that
375 should be recorded as having helped the transaction. yum plugins
376 have an API to add themselves to this, so it should not normally
377 be necessary to add packages here. Not that this is also used
378 for the packages to look for in --version. Defaults to rpm, yum,
379 yum-metadata-parser.
380 history_list_view Which column of information to display in the
383 "yum history list" command. There are currently three options:
384 users, cmds (or commands), single-user-commands.
385 Older versions of yum acted like "users", which always outputs
387 the user who initiated the yum transaction. You can now specify
388 "commands" which will instead always output the command line of
389 the transaction. You can also specify "single-user-commands"
390 which will display the users if there are more than one, other‐
391 wise it will display the command line.
392 You can also specify "default" which currently selects "users".
394 commands List of functional commands to run if no functional
397 commands are specified on the command line (eg. "update foo bar
398 baz quux"). None of the short options (eg. -y, -e, -d) are
399 accepted for this option.
400 syslog_ident Identification (program name) for syslog messages.
403 syslog_facility Facility name for syslog messages, see sys‐
406 log(3). Default is `LOG_USER'.
407 syslog_device Where to log syslog messages. Can be a local
410 device (path) or a host:port string to use a remote syslog. If
411 empty or points to a nonexistent device, syslog logging is dis‐
412 abled. Default is `/dev/log'.
413 proxy URL to the proxy server that yum should use.
416 proxy_username username to use for proxy
419 proxy_password password for this proxy
422 plugins Either `0' or `1'. Global switch to enable or disable
425 yum plugins. Default is `0' (plugins disabled). See the PLUGINS
426 section of the yum(8) man for more information on installing yum
427 plugins.
428 pluginpath A list of directories where yum should look for plug‐
431 in modules. Default is `/usr/share/yum-plugins' and
432 `/usr/lib/yum-plugins'.
433 pluginconfpath A list of directories where yum should look for
436 plugin configuration files. Default is `/etc/yum/pluginconf.d'.
437 metadata_expire Time (in seconds) after which the metadata will
440 expire. So that if the current metadata downloaded is less than
441 this many seconds old then yum will not update the metadata
442 against the repository. If you find that yum is not downloading
443 information on updates as often as you would like lower the
444 value of this option. You can also change from the default of
445 using seconds to using days, hours or minutes by appending a d,
446 h or m respectively. The default is 6 hours, to compliment yum-
447 updatesd running once an hour. It's also possible to use the
448 word "never", meaning that the metadata will never expire. Note
449 that when using a metalink file the metalink must always be
450 newer than the metadata for the repository, due to the valida‐
451 tion, so this timeout also applies to the metalink file.
452 mirrorlist_expire Time (in seconds) after which the mirrorlist
455 locally cached will expire. If the current mirrorlist is less
456 than this many seconds old then yum will not download another
457 copy of the mirrorlist, it has the same extra format as meta‐
458 data_expire. If you find that yum is not downloading the mir‐
459 rorlists as often as you would like lower the value of this
460 option.
461 mdpolicy You can select from different metadata download poli‐
464 cies depending on how much data you want to download with the
465 main repository metadata index. The advantages of downloading
466 more metadata with the index is that you can't get into situa‐
467 tions where you need to use that metadata later and the versions
468 available aren't compatible (or the user lacks privileges) and
469 that if the metadata is corrupt in any way yum will revert to
470 the previous metadata.
471 `instant' - Just download the new metadata index, this is
473 roughly what yum always did, however it now does some checking
474 on the index and reverts if it classifies it as bad.
475 `group:primary' - Download the primary metadata with the index.
477 This contains most of the package information and so is almost
478 always required anyway. This is the default.
479 `group:small' - With the primary also download the updateinfo
481 metadata, this is required for yum-security operations and it
482 also used in the graphical clients. This file also tends to be
483 significantly smaller than most others.
484 `group:main' - With the primary and updateinfo download the
486 filelists metadata and the group metadata. The filelists data is
487 required for operations like "yum install /bin/bash", and also
488 some dependency resolutions require it. The group data is used
489 in some graphical clients and for group operations like "yum
490 grouplist Base".
491 `group:all' - Download all metadata listed in the index, cur‐
493 rently the only one not listed above is the other metadata,
494 which contains the changelog information which is used by yum-
495 changelog. This is what "yum makecache" uses.
496 multilib_policy Can be set to 'all' or 'best'. All means install
499 all possible arches for any package you want to install. There‐
500 fore yum install foo will install foo.i386 and foo.x86_64 on
501 x86_64, if it is available. Best means install the best arch for
502 this platform, only.
503 bugtracker_url URL where bugs should be filed for yum. Config‐
506 urable for local versions or distro-specific bugtrackers.
507 color Display colorized output automatically, depending on the
510 output terminal, always (using ANSI codes) or never. Command-
511 line option: --color
512 color_list_installed_older The colorization/highlighting for
515 packages in list/info installed which are older than the latest
516 available package with the same name and arch. Default is
517 `bold'. Possible values are a comma separated list containing:
518 bold, blink, dim, reverse, underline, fg:black, fg:red,
519 fg:green, fg:yellow, fg:blue, fg:magenta, fg:cyan, fg:white,
520 bg:black, bg:red, bg:green, bg:yellow, bg:blue, bg:magenta,
521 bg:cyan, bg:white.
522 color_list_installed_newer The colorization/highlighting for
525 packages in list/info installed which are newer than the latest
526 available package with the same name and arch. Default is
527 `bold,yellow'. See color_list_installed_older for possible val‐
528 ues.
529 color_list_installed_reinstall The colorization/highlighting for
532 packages in list/info installed which is the same version as the
533 latest available package with the same name and arch. Default
534 is `normal'. See color_list_installed_older for possible val‐
535 ues.
536 color_list_installed_extra The colorization/highlighting for
539 packages in list/info installed which has no available package
540 with the same name and arch. Default is `bold,red'. See
541 color_list_installed_older for possible values.
542 color_list_available_upgrade The colorization/highlighting for
545 packages in list/info available which is an upgrade for the lat‐
546 est installed package with the same name and arch. Default is
547 `bold,blue'. See color_list_installed_older for possible val‐
548 ues.
549 color_list_available_downgrade The colorization/highlighting for
552 packages in list/info available which is a downgrade for the
553 latest installed package with the same name and arch. Default
554 is `dim,cyan'. See color_list_installed_older for possible val‐
555 ues.
556 color_list_available_install The colorization/highlighting for
559 packages in list/info available which has no installed package
560 with the same name and arch. Default is `normal'. See
561 color_list_installed_older for possible values.
562 color_list_available_reinstall The colorization/highlighting for
565 packages in list/info available which is the same version as the
566 installed package with the same name and arch. Default is
567 `bold,underline,green. See color_list_installed_older for pos‐
568 sible values.
569 color_search_match The colorization/highlighting for text
572 matches in search. Default is `bold'. See
573 color_list_installed_older for possible values.
574 color_update_installed The colorization/highlighting for pack‐
577 ages in the "updates list" which are installed. The updates list
578 is what is printed when you run "yum update", "yum list
579 updates", "yum list obsoletes" and "yum check-update". Default
580 is `normal'. See color_list_installed_older for possible val‐
581 ues.
582 color_update_local The colorization/highlighting for packages in
585 the "updates list" which are already downloaded. The updates
586 list is what is printed when you run "yum update", "yum list
587 updates", "yum list obsoletes" and "yum check-update". Default
588 is `bold'. See color_list_installed_older for possible values.
589 color_update_remote The colorization/highlighting for packages
592 in the "updates list" which need to be downloaded. The updates
593 list is what is printed when you run "yum update", "yum list
594 updates", "yum list obsoletes" and "yum check-update". Default
595 is `normal'. See color_list_installed_older for possible val‐
596 ues.
597 clean_requirements_on_remove When removing packages (by removal,
601 update or obsoletion) go through each package's dependencies. If
602 any of them are no longer required by any other package then
603 also mark them to be removed. Boolean (1, 0, True, False,
604 yes,no) Defaults to False
605 reset_nice If set to true then yum will try to reset the nice
608 value to zero, before running an rpm transaction. Defaults to
609 True.
610 depsolve_loop_limit Set the number of times any attempt to dep‐
613 solve before we just give up. This shouldn't be needed as yum
614 should always solve or fail, however it has been observed that
615 it can loop forever with very large system upgrades. Setting
616 this to `0' (or "<forever>") makes yum try forever. Default is
617 `100'.
618
622 The repository section(s) take the following form:
623 Example: [repositoryid]
625 name=Some name for this repository
626 baseurl=url://path/to/repository/
627 repositoryid Must be a unique name for each repository, one
630 word.
631 name A human readable string describing the repository.
634 baseurl Must be a URL to the directory where the yum reposi‐
637 tory's `repodata' directory lives. Can be an http://, ftp:// or
638 file:// URL. You can specify multiple URLs in one baseurl state‐
639 ment. The best way to do this is like this:
640 [repositoryid]
641 name=Some name for this repository
642 baseurl=url://server1/path/to/repository/
643 url://server2/path/to/repository/
644 url://server3/path/to/repository/
645 If you list more than one baseurl= statement in a repository you
647 will find yum will ignore the earlier ones and probably act
648 bizarrely. Don't do this, you've been warned.
649 You can use HTTP basic auth by prepending "user:password@" to
651 the server name in the baseurl line. For example:
652 "baseurl=http://user:passwd@example.com/".
653 metalink Specifies a URL to a metalink file for the repomd.xml,
656 a list of mirrors for the entire repository are generated by
657 converting the mirrors for the repomd.xml file to a baseurl. The
658 metalink file also contains the latest timestamp from the data
659 in the repomd.xml, the length of the repomd.xml and checksum
660 data. This data is checked against any downloaded repomd.xml
661 file and all of the information from the metalink file must
662 match. This can be used instead of or with the baseurl option.
663 Substitution variables, described below, can be used with this
664 option. This option disables the mirrorlist option. As a spe‐
665 cial hack is the mirrorlist URL contains the word "metalink"
666 then the value of mirrorlist is copied to metalink (if metalink
667 is not set).
668 mirrorlist Specifies a URL to a file containing a list of
671 baseurls. This can be used instead of or with the baseurl
672 option. Substitution variables, described below, can be used
673 with this option. As a special hack is the mirrorlist URL con‐
674 tains the word "metalink" then the value of mirrorlist is copied
675 to metalink (if metalink is not set).
676 enabled Either `1' or `0'. This tells yum whether or not use
680 this repository.
681 gpgcheck Either `1' or `0'. This tells yum whether or not it
684 should perform a GPG signature check on the packages gotten from
685 this repository.
686 repo_gpgcheck Either `1' or `0'. This tells yum whether or not
689 it should perform a GPG signature check on the repodata from
690 this repository.
691 gpgkey A URL pointing to the ASCII-armored GPG key file for the
694 repository. This option is used if yum needs a public key to
695 verify a package and the required key hasn't been imported into
696 the RPM database. If this option is set, yum will automatically
697 import the key from the specified URL. You will be prompted
698 before the key is installed unless the assumeyes option is set.
699 Multiple URLs may be specified here in the same manner as the
701 baseurl option (above). If a GPG key is required to install a
702 package from a repository, all keys specified for that reposi‐
703 tory will be installed.
704 gpgcakey A URL pointing to the ASCII-armored CA key file for the
707 repository. This is a normal gpg public key - but this key will
708 be used to validate detached signatures of all other keys. The
709 idea is you are asked to confirm import for this key. After that
710 any other gpg key needed for package or repository verification,
711 if it has a detached signature which matches this key will be
712 automatically imported without user confirmation.
713 exclude Same as the [main] exclude option but only for this
716 repository. Substitution variables, described below, are hon‐
717 ored here.
718 includepkgs Inverse of exclude. This is a list of packages you
721 want to use from a repository. If this option lists only one
722 package then that is all yum will ever see from the repository.
723 Defaults to an empty list. Substitution variables, described
724 below, are honored here.
725 enablegroups Either `0' or `1'. Determines whether yum will
728 allow the use of package groups for this repository. Default is
729 `1' (package groups are allowed).
730 failovermethod Either `roundrobin' or `priority'.
733 `roundrobin' randomly selects a URL out of the list of URLs to
735 start with and proceeds through each of them as it encounters a
736 failure contacting the host.
737 `priority' starts from the first baseurl listed and reads
739 through them sequentially.
740 failovermethod defaults to `roundrobin' if not specified.
742 keepalive Either `1' or `0'. This tells yum whether or not
745 HTTP/1.1 keepalive should be used with this repository. See the
746 global option in the [main] section above for more information.
747 timeout Overrides the timeout option from the [main] section for
750 this repository.
751 http_caching Overrides the http_caching option from the [main]
754 section for this repository.
755 retries Overrides the retries option from the [main] section for
758 this repository.
759 throttle Overrides the throttle option from the [main] section
762 for this repository.
763 bandwidth Overrides the bandwidth option from the [main] section
766 for this repository.
767 ftp_disable_epsv Overrides the ftp_disable_epsv option from the
770 [main] section for this repository.
771 sslcacert Overrides the sslcacert option from the [main] section
774 for this repository.
775 sslverify Overrides the sslverify option from the [main] section
778 for this repository.
779 sslclientcert Overrides the sslclientcert option from the [main]
782 section for this repository.
783 sslclientkey Overrides the sslclientkey option from the [main]
786 section for this repository.
787 ssl_check_cert_permissions Overrides the ssl_check_cert_permis‐
790 sions option from the [main] section for this repository.
791 metadata_expire Overrides the metadata_expire option from the
794 [main] section for this repository.
795 mirrorlist_expire Overrides the mirrorlist_expire option from
798 the [main] section for this repository.
799 proxy URL to the proxy server for this repository. Set to
802 '_none_' to disable the global proxy setting for this reposi‐
803 tory. If this is unset it inherits it from the global setting
804 proxy_username username to use for proxy. If this is unset it
807 inherits it from the global setting
808 proxy_password password for this proxy. If this is unset it
811 inherits it from the global setting
812 cost relative cost of accessing this repository. Useful for
816 weighing one repo's packages as greater/less than any other.
817 defaults to 1000
818 skip_if_unavailable If set to True yum will continue running if
821 this repository cannot be contacted for any reason. This should
822 be set carefully as all repos are consulted for any given com‐
823 mand. Defaults to False.
824
826 The inclusion of external configuration files is supported for
827 /etc/yum.conf and the .repo files in the /etc/yum.repos.d directory. To
828 include a URL, use a line of the following format:
829 include=url://to/some/location
831 The configuration file will be inserted at the position of the
833 "include=" line. Included files may contain further include lines. Yum
834 will abort with an error if an inclusion loop is detected.
835
838 Any of the configurations options which are a list of items can be
839 specfied using the glob syntax: glob:/etc/path/somewhere.d/*.conf. This
840 will read in all files matching that glob and include all lines in each
841 file (excluding comments and blank lines) as items in the list.
842
844 There are a number of variables you can use to ease maintenance of
845 yum's configuration files. They are available in the values of several
846 options including name, baseurl and commands.
847 $releasever This will be replaced with the value of the version
849 of the package listed in distroverpkg. This defaults to the ver‐
850 sion of `redhat-release' package.
851 $arch This will be replaced with the architecture or your system
854 as detected by yum.
855 $basearch This will be replaced with your base architecture in
858 yum. For example, if your $arch is i686 your $basearch will be
859 i386.
860 $uuid This will be replaced with a unique but persistent uuid
863 for this machine. The value that is first generated will be
864 stored in /var/lib/yum/uuid and reused until this file is
865 deleted.
866 $YUM0-$YUM9 These will be replaced with the value of the shell
869 environment variable of the same name. If the shell environment
870 variable does not exist then the configuration file variable
871 will not be replaced.
872 As of 3.2.28, any properly named file in /etc/yum/vars is turned into a
875 variable named after the filename (or overrides any of the above vari‐
876 ables). Filenames may contain only alphanumeric characters and under‐
877 scores and be in lowercase.
878 Note that no warnings/errors are given if the files are unreadable, so
880 creating files that only root can read may be confusing for users.
881 Also note that only the first line will be read and all new line char‐
883 acters are removed, as a convenience. However, no other checking is
884 performed on the data. This means it is possible to have bad character
885 data in any value.
886
889 /etc/yum.conf
890 /etc/yum.repos.d/
891 /etc/yum/pluginconf.d/
892 /etc/yum/protected.d
893 /etc/yum/vars
894
897 yum(8)
898Seth Vidal yum.conf(5)