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 usercache Either `1' or `0'. Determines whether or not yum
44 should store per-user cache in $TMPDIR. When set to `0', then
45 whenever yum runs as a non-root user, --cacheonly is implied and
46 system cache is used directly, and no new user cache is created
47 in $TMPDIR. This can be used to prevent $TMPDIR from filling up
48 if many users on the system often use yum and root tends to have
49 up-to-date metadata that the users can rely on (they can still
50 enable this feature with --setopt if they wish). Default is `1'
51 (user cache enabled).
52 reposdir A list of directories where yum should look for .repo
55 files which define repositories to use. Default is
56 `/etc/yum.repos.d'. Each file in this directory should contain
57 one or more repository sections as documented in [repository]
58 options below. These will be merged with the repositories
59 defined in /etc/yum.conf to form the complete set of reposito‐
60 ries that yum will use.
61 debuglevel Debug message output level. Practical range is 0-10.
64 Default is `2'.
65 errorlevel Error message output level. Practical range is 0-10.
68 Default is `2'.
69 rpmverbosity Debug scriptlet output level. 'info' is the
72 default, other options are: 'critical', 'emergency', 'error',
73 'warn' and 'debug'.
74 protected_packages This is a list of packages that yum should
77 never completely remove. They are protected via Obsoletes as
78 well as user/plugin removals.
79 The default is: yum glob:/etc/yum/protected.d/*.conf So any
81 packages which should be protected can do so by including a file
82 in /etc/yum/protected.d with their package name in it.
83 Also if this configuration is set to anything, then yum will
85 protect the package corresponding to the running version of the
86 kernel.
87 protected_multilib Either `1' or `0'. This tells yum whether or
90 not it should perform a check to make sure that multilib pack‐
91 ages are the same version. For example, if this option is off
92 (rpm behaviour) pkgA-1.x86_64 and pkgA-2.i386 can be installed
93 at the same time. However this is very rarely desired. Install
94 only packages, like the kernel, are exempt from this check. The
95 default is `1'.
96 logfile Full directory and file name for where yum should write
99 its log file.
100 gpgcheck Either `1' or `0'. This tells yum whether or not it
103 should perform a GPG signature check on packages. When this is
104 set in the [main] section it sets the default for all reposito‐
105 ries. The default is `0'.
106 localpkg_gpgcheck Either `1' or `0'. This tells yum whether or
108 not it should perform a GPG signature check on local packages
109 (packages in a file, not in a repositoy). The default is `0'.
110 repo_gpgcheck Either `1' or `0'. This tells yum whether or not
113 it should perform a GPG signature check on the repodata. When
114 this is set in the [main] section it sets the default for all
115 repositories. The default is `0'.
116 payload_gpgcheck Either `1' or `0'. This tells yum whether or
119 not it should perform a v3 signature check on packages when
120 gpgcheck (or localpkg_gpgcheck for local packages) is enabled.
121 There are two types of GPG signatures generated by rpm: v3 (on
123 header+payload) and v4 (on header only). When rpm signs a pack‐
124 age, it creates both types. Yum can verify any of them before
125 the transaction, depending on which options are set. When
126 gpgcheck is enabled and this option is disabled, yum will verify
127 v4 signatures only. When both gpgcheck and this option are
128 enabled, yum will verify both v4 and v3 signatures (equivalent
129 to running "rpm --checksig"). The same rules apply to local
130 packages and the localpkg_gpgcheck option accordingly.
131 Since the header contains sha256 digests of individual files in
133 the payload (a gzip-compressed cpio archive of files used in the
134 package), verifying the header signature (v4) is sufficient to
135 ensure authenticity and integrity of the whole package. After
136 rpm unpacks the payload, it moves the files to their destination
137 paths one by one after they pass the digest check. If a file
138 doesn't pass, it won't be moved and the transaction will abort.
139 However, because no rollback is done in such a case, the package
140 may end up in the partially installed state.
141 By verifying v3 signatures, yum will detect payload tamper
143 before the transaction. While this will slightly increase pro‐
144 cessing time for big transactions and/or packages, it will pre‐
145 vent such broken installs and enhance security.
146 The default is `0'.
148 skip_broken Either `1' or `0'. Resolve depsolve problems by
151 removing packages that are causing problems from the transac‐
152 tion.
153 assumeyes Either `1' or `0'. Determines whether or not yum
156 prompts for confirmation of critical actions. Default is `0' (do
157 prompt).
158 Command-line option: -y --assumeyes
159 assumeno Either `1' or `0'. If yum would prompt for confirmation
162 of critical actions, assume the user chose no. This is basically
163 the same as doing "echo | yum ..." but is a bit more usable.
164 This option overrides assumeyes, but is still subject to
165 alwaysprompt. Default is `0' (do prompt).
166 Command-line option: --assumeno
167 alwaysprompt Either `1' or `0'. Without this option, yum will
170 not prompt for confirmation when the list of packages to be
171 installed exactly matches those given on the command line.
172 Unless assumeyes is enabled, it will still prompt when addi‐
173 tional packages need to be installed to fulfill dependencies.
174 Note that older versions of yum would also always prompt for
175 package removal, and that is no longer true. Default is `1'.
176 tolerant Either `1' or `0'. If enabled, yum will go slower,
179 checking for things that shouldn't be possible making it more
180 tolerant of external errors. Default to `0' (not tolerant).
181 Command-line option: -t
182 exclude List of packages to exclude from all repositories, so
185 yum works as if that package was never in the repositories. This
186 should be a space separated list. This is commonly used so a
187 package isn't upgraded or installed accidentally, but can be
188 used to remove packages in any way that "yum list" will show
189 packages. Shell globs using wildcards (eg. * and ?) are
190 allowed.
191 Can be disabled using disable_excludes or --disableexcludes.
193 Command-line option: -x
194 disable_excludes A way to permanently set the --disableexcludes
197 command line option.
198 query_install_excludes This applies the command line exclude
201 option (only, not the configuration exclude above) to installed
202 packages being shown in some query commands (currently:
203 list/info/search/provides). Default is '0'.
204 installonlypkgs List of package provides that should only ever
207 be installed, never updated. Kernels in particular fall into
208 this category. Defaults to kernel, kernel-bigmem, kernel-enter‐
209 prise, kernel-smp, kernel-debug, kernel-unsupported, kernel-
210 source, kernel-devel, kernel-PAE, kernel-PAE-debug.
211 Note that because these are provides, and not just package
213 names, kernel-devel will also apply to kernel-debug-devel, etc.
214 Note that "kernel-modules" is not in this list, in RHEL-6, and
216 so anything providing that is updated like any other package.
217 installonly_limit Number of packages listed in installonlypkgs
220 to keep installed at the same time. Setting to 0 disables this
221 feature. Default is '3'. Note that this functionality used to be
222 in the "installonlyn" plugin, where this option was altered via
223 tokeep. Note that as of version 3.2.24, yum will now look in
224 the yumdb for a installonly attribute on installed packages. If
225 that attribute is "keep", then they will never be removed.
226 kernelpkgnames List of package names that are kernels. This is
229 really only here for the updating of kernel packages and should
230 be removed out in the yum 2.1 series.
231 exactarchlist List of packages that should never change archs in
234 an update. That means, if a package has a newer version avail‐
235 able which is for a different compatible arch, yum will not con‐
236 sider that version an update if the package name is in this
237 list. For example, on x86_64, foo-1.x86_64 won't be updated to
238 foo-2.i686 if foo is in this list. Kernels in particular fall
239 into this category. Shell globs using wildcards (eg. * and ?)
240 are allowed. Default is an empty list.
241 showdupesfromrepos Either `0' or `1'. Set to `1' if you wish to
244 show any duplicate packages from any repository, from package
245 listings like the info or list commands. Set to `0' if you want
246 only to see the newest packages from any repository. Default is
247 `0'.
248 obsoletes This option only has affect during an update. It
251 enables yum's obsoletes processing logic. Useful when doing dis‐
252 tribution level upgrades. See also the yum upgrade command docu‐
253 mentation for more details (yum(8)). Default is `true'.
254 Command-line option: --obsoletes
255 remove_leaf_only Either `0' or `1'. Used to determine yum's be‐
258 haviour when a package is removed. If remove_leaf_only is `0'
259 (default) then packages, and their deps, will be removed. If
260 remove_leaf_only is `1' then only those packages that aren't
261 required by another package will be removed.
262 repopkgsremove_leaf_only Either `0' or `1'. Used to determine
265 yum's behaviour when the repo-pkg remove command is run. If
266 repopkgremove_leaf_only is `0' (default) then all packages in
267 the repo. will be removed. If repopkgremove_leaf_only is `1'
268 then only those packages in the repo. that aren't required by
269 another package will be removed. Note that this option does not
270 override remove_leaf_only, so enabling that option means this
271 has almost no affect.
272 overwrite_groups Either `0' or `1'. Used to determine yum's be‐
275 haviour if two or more repositories offer the package groups
276 with the same name. If overwrite_groups is `1' then the group
277 packages of the last matching repository will be used. If over‐
278 write_groups is `0' then the groups from all matching reposito‐
279 ries will be merged together as one large group. Note that this
280 option does not override remove_leaf_only, so enabling that
281 option means this has almost no affect.
282 groupremove_leaf_only Either `0' or `1'. Used to determine yum's
285 behaviour when the groupremove command is run. If groupre‐
286 move_leaf_only is `0' (default) then all packages in the group
287 will be removed. If groupremove_leaf_only is `1' then only
288 those packages in the group that aren't required by another
289 package will be removed.
290 enable_group_conditionals Either `0' or `1'. Determines whether
293 yum will allow the use of conditionals packages. Default is `1'
294 (package conditionals are allowed).
295 group_package_types List of the following: optional, default,
298 mandatory. Tells yum which type of packages in groups will be
299 installed when 'groupinstall' is called. Default is: default,
300 mandatory
301 group_command List of the following: simple, compat, objects.
304 Tells yum what to do for group install/upgrade/remove commands.
305 Simple acts like you did yum group cmd $(repoquery --group
307 --list group), so it is vrery easy to reason about what will
308 happen. Alas. this is often not what people want to happen.
309 Compat. works much like simple, except that when you run "group
311 upgrade" it actually runs "group install" (this means that you
312 get any new packages added to the group, but you also get pack‐
313 ages added that were there before and you didn't want).
314 Objects makes groups act like a real object, separate from the
316 packages they contain. Yum keeps track of the groups you have
317 installed, so "group upgrade" will install new packages for the
318 group but not install old ones. It also knows about group mem‐
319 bers that are installed but weren't installed as part of the
320 group, and won't remove those on "group remove". Running "yum
321 upgrade" will also run "yum group upgrade" (thus. adding new
322 packages for all groups).
323 Default is: objects
325 upgrade_group_objects_upgrade Either `0' or `1'. Set this to `0'
328 to disable the automatic running of "group upgrade" when running
329 the "upgrade" command, and group_command is set to "objects".
330 Default is `1' (perform the operation).
331 autocheck_running_kernel Either `0' or `1'. Set this to `0' to
334 disable the automatic checking of the running kernel against
335 updateinfo ("yum updateinfo check-running-kernel"), in the
336 "check-update" and "updateinfo summary" commands. Default is
337 `1' (perform the check).
338 installroot Specifies an alternative installroot, relative to
341 which all packages will be installed.
342 Command-line option: --installroot
343 config_file_path Specifies the path to main the configuration
346 file. Default is /etc/yum/yum.conf.
347 check_config_file_age Either `0' or `1'. Specifies whether yum
350 should auto metadata expire repos. that are older than any of
351 the configuration files that led to them (usually the yum.conf
352 file and the foo.repo file). Default is `1' (perform the
353 check).
354 distroverpkg The package used by yum to determine the "version"
357 of the distribution, this sets $releasever for use in config.
358 files. This can be any installed package. Default is `system-
359 release(releasever)', `redhat-release'. Yum will now look at the
360 version provided by the provide, and if that is non-empty then
361 will use the full V(-R), otherwise it uses the version of the
362 package.
363 You can see what provides this manually by using: "yum whatpro‐
364 vides 'system-release(releasever)' redhat-release" and you can
365 see what $releasever is most easily by using: "yum version".
366 diskspacecheck Either `0' or `1'. Set this to `0' to disable the
369 checking for sufficient diskspace and inodes before a RPM trans‐
370 action is run. Default is `1' (perform the check).
371 tsflags Comma or space separated list of transaction flags to
374 pass to the rpm transaction set. These include 'noscripts',
375 'notriggers', 'nodocs', 'test', 'justdb' and 'nocontexts'.
376 'repackage' is also available but that does nothing with newer
377 rpm versions. You can set all/any of them. However, if you
378 don't know what these do in the context of an rpm transaction
379 set you're best leaving it alone. Default is an empty list.
380 Also see the "yum fs" command, for excluding docs.
381 override_install_langs This is a way to override rpm's
384 _install_langs macro. without having to change it within rpm's
385 macro file. Default is nothing (so does nothing). Also see the
386 "yum fs" command.
387 recent Number of days back to look for `recent' packages added
390 to a repository. Used by the list recent command. Default is
391 `7'.
392 retries Set the number of times any attempt to retrieve a file
395 should retry before returning an error. Setting this to `0'
396 makes yum try forever. Default is `10'.
397 keepalive Either `0' or `1'. Set whether HTTP keepalive should
400 be used for HTTP/1.1 servers that support it. This can improve
401 transfer speeds by using one connection when downloading multi‐
402 ple files from a repository. Default is `1'.
403 timeout Number of seconds to wait for a connection before timing
406 out. Defaults to 30 seconds. This may be too short of a time for
407 extremely overloaded sites.
408 http_caching Determines how upstream HTTP caches are instructed
411 to handle any HTTP downloads that Yum does. This option can take
412 the following values:
413 `all' means that all HTTP downloads should be cached.
415 `packages' means that only RPM package downloads should be
417 cached (but not repository metadata downloads).
418 `lazy:packages' means that act like `packages' unless package
420 verification fails (e.g. the package download doesn't match the
421 expected checksum), in which case try re-downloading the package
422 as if `none' was set. This value is a good compromise if you
423 want to avoid issues caused by stale proxy cache after remote
424 RPMs change contents without changing filenames (e.g. are pushed
425 unsigned and later signed) but still want the benefits of pack‐
426 age caching whenever possible.
427 `none' means that no HTTP downloads should be cached.
429 The default is `all'. This is recommended unless you are experi‐
431 encing caching related issues. Try to at least use `packages' to
432 minimize load on repository servers.
433 throttle Enable bandwidth throttling for downloads. This option
436 can be expressed as a absolute data rate in bytes/sec. An SI
437 prefix (k, M or G) may be appended to the bandwidth value (eg.
438 `5.5k' is 5.5 kilobytes/sec, `2M' is 2 Megabytes/sec).
439 Alternatively, this option can specify the percentage of total
441 bandwidth to use (eg. `60%'). In this case the bandwidth option
442 should be used to specify the maximum available bandwidth.
443 Set to `0' to disable bandwidth throttling. This is the default.
445 Note that when multiple downloads run simultaneously the total
447 bandwidth might exceed the throttle limit. You may want to also
448 set max_connections=1 or scale your throttle option down accord‐
449 ingly.
450 minrate This sets the low speed threshold in bytes per second.
453 If the server is sending data slower than this for at least
454 `timeout' seconds, Yum aborts the connection. The default is
455 `1000'.
456 bandwidth Use to specify the maximum available network bandwidth
459 in bytes/second. Used with the throttle option (above). If
460 throttle is a percentage and bandwidth is `0' then bandwidth
461 throttling will be disabled. If throttle is expressed as a data
462 rate (bytes/sec) then this option is ignored. Default is `0' (no
463 bandwidth throttling).
464 ip_resolve Determines how yum resolves host names.
467 `4' or `IPv4': resolve to IPv4 addresses only.
469 `6' or `IPv6': resolve to IPv6 addresses only.
471 max_connections
474 The maximum number of simultaneous connections. This overrides
476 the urlgrabber default of 5 connections. Note that there are
477 also implicit per-mirror limits and the downloader honors these
478 too.
479 ftp_disable_epsv This options disables Extended Passive Mode
482 (the EPSV command) which does not work correctly on some buggy
483 ftp servers. Default is `0' (EPSV enabled).
484 deltarpm
487 When non-zero, delta-RPM files are used if available. The value
489 specifies the maximum number of "applydeltarpm" processes Yum
490 will spawn, if the value is negative then yum works out how many
491 cores you have and multiplies that by the value (cores=2,
492 deltarpm=-2; 4 processes). (2 by default).
493 Note that the "applydeltarpm" process uses a significant amount
495 of disk IO, so running too many instances can significantly slow
496 down all disk IO including the downloads that yum is doing
497 (thus. a too high value can make everything slower).
498 deltarpm_percentage When the relative size of delta vs pkg is
501 larger than this, delta is not used. Default value is 75
502 (Deltas must be at least 25% smaller than the pkg). Use `0' to
503 turn off delta rpm processing. Local repositories (with file://
504 baseurl) have delta rpms turned off by default.
505 deltarpm_metadata_percentage When the relative size of deltarpm
508 metadata vs pkgs is larger than this, deltarpm metadata is not
509 downloaded from the repo. Default value is 100 (Deltarpm meta‐
510 data must be smaller than the packages from the repo). Note that
511 you can give values over 100, so 200 means that the metadata is
512 required to be half the size of the packages. Use `0' to turn
513 off this check, and always download metadata.
514 sslcacert Path to the directory containing the databases of the
517 certificate authorities yum should use to verify SSL certifi‐
518 cates. Defaults to none - uses system default
519 sslverify Boolean - should yum verify SSL certificates/hosts at
522 all. Defaults to True.
523 Note that the plugin yum-rhn-plugin will force this value to
525 true, and may alter other ssl settings (like hostname checking),
526 even if it the machine is not registered.
527 sslclientcert Path to the SSL client certificate yum should use
530 to connect to repos/remote sites Defaults to none.
531 Note that if you are using curl compiled against NSS (default in
533 Fedora/RHEL), curl treats sslclientcert values with the same
534 basename as _identical_. This version of yum will check that
535 this isn't true and output an error when the repositories "foo"
536 and "bar" violate this, like so:
537 sslclientcert basename shared between foo and bar
539 sslclientkey Path to the SSL client key yum should use to con‐
542 nect to repos/remote sites Defaults to none.
543 ssl_check_cert_permissions Boolean - Whether yum should check
546 the permissions on the paths for the certificates on the reposi‐
547 tory (both remote and local). If we can't read any of the files
548 then yum will force skip_if_unavailable to be true. This is
549 most useful for non-root processes which use yum on repos. that
550 have client cert files which are readable only by root.
551 Defaults to True.
552 history_record Boolean - should yum record history entries for
555 transactions. This takes some disk space, and some extra time in
556 the transactions. But it allows how to know a lot of information
557 about what has happened before, and display it to the user with
558 the history info/list/summary commands. yum also provides the
559 history undo/redo commands. Defaults to True.
560 Note that if history is recorded, yum uses that information to
562 see if any modifications to the rpmdb have been done outside of
563 yum. These are always bad, from yum's point of view, and so yum
564 will issue a warning and automatically run some of "yum check"
565 to try and find some of the worst problems altering the rpmdb
566 might have caused.
567 This means that turning this option off will stop yum from being
569 able to detect when the rpmdb has changed and thus. it will
570 never warn you or automatically run "yum check". The problems
571 will likely still be there, and yumdb etc. will still be wrong
572 but yum will not warn you about it.
573 history_record_packages This is a list of package names that
576 should be recorded as having helped the transaction. yum plugins
577 have an API to add themselves to this, so it should not normally
578 be necessary to add packages here. Not that this is also used
579 for the packages to look for in --version. Defaults to rpm, yum,
580 yum-metadata-parser.
581 history_list_view Which column of information to display in the
584 "yum history list" command. There are currently three options:
585 users, cmds (or commands), auto.
586 Older versions of yum acted like "users", which always outputs
588 the user who initiated the yum transaction. You can now specify
589 "commands" which will instead always output the command line of
590 the transaction. You can also specify "single-user-commands"
591 which will display the users if there are more than one, other‐
592 wise it will display the command line.
593 You can also specify "default" which currently selects "single-
595 user-commands".
596 commands List of functional commands to run if no functional
599 commands are specified on the command line (eg. "update foo bar
600 baz quux"). None of the short options (eg. -y, -e, -d) are
601 accepted for this option.
602 syslog_ident Identification (program name) for syslog messages.
605 syslog_facility Facility name for syslog messages, see sys‐
608 log(3). Default is `LOG_USER'.
609 syslog_device Where to log syslog messages. Can be a local
612 device (path) or a host:port string to use a remote syslog. If
613 empty or points to a nonexistent device, syslog logging is dis‐
614 abled. Default is `/dev/log'.
615 proxy URL to the proxy server that yum should use. Set this to
618 `libproxy' to enable proxy auto configuration via libproxy.
619 Defaults to direct connection.
620 proxy_username username to use for proxy
623 proxy_password password for this proxy
626 username username to use for basic authentication to a repo or
629 really any url.
630 password password to use with the username for basic authentica‐
633 tion.
634 plugins Either `0' or `1'. Global switch to enable or disable
637 yum plugins. Default is `0' (plugins disabled). See the PLUGINS
638 section of the yum(8) man for more information on installing yum
639 plugins.
640 pluginpath A list of directories where yum should look for plug‐
643 in modules. Default is `/usr/share/yum-plugins' and
644 `/usr/lib/yum-plugins'.
645 pluginconfpath A list of directories where yum should look for
648 plugin configuration files. Default is `/etc/yum/pluginconf.d'.
649 metadata_expire Time (in seconds) after which the metadata will
652 expire. So that if the current metadata downloaded is less than
653 this many seconds old then yum will not update the metadata
654 against the repository. If you find that yum is not downloading
655 information on updates as often as you would like lower the
656 value of this option. You can also change from the default of
657 using seconds to using days, hours or minutes by appending a d,
658 h or m respectively. The default is 6 hours, to compliment yum-
659 updatesd running once an hour. It's also possible to use the
660 word "never", meaning that the metadata will never expire. Note
661 that when using a metalink file the metalink must always be
662 newer than the metadata for the repository, due to the valida‐
663 tion, so this timeout also applies to the metalink file. Also
664 note that "never" does not override "yum clean expire-cache"
665 metadata_expire_filter Filter the metadata_expire time, allowing
668 a trade of speed for accuracy if a command doesn't require it.
669 Each yum command can specify that it requires a certain level of
670 timeliness quality from the remote repos. from "I'm about to
671 install/upgrade, so this better be current" to "Anything that's
672 available is good enough".
673 `never' - Nothing is filtered, always obey metadata_expire.
675 `read-only:past' - Commands that only care about past informa‐
677 tion are filtered from metadata expiring. Eg. yum history info
678 (if history needs to lookup anything about a previous transac‐
679 tion, then by definition the remote package was available in the
680 past).
681 `read-only:present' - Commands that are balanced between past
683 and future. This is the default. Eg. yum list yum
684 `read-only:future' - Commands that are likely to result in run‐
686 ning other commands which will require the latest metadata. Eg.
687 yum check-update
688 Note that this option requires that all the enabled repositories
690 be roughly the same freshness (meaning the cache age difference
691 from one another is at most 5 days). Failing that, meta‐
692 data_expire will always be obeyed, just like with `never'.
693 Also note that this option does not override "yum clean expire-
695 cache".
696 mirrorlist_expire Time (in seconds) after which the mirrorlist
699 locally cached will expire. If the current mirrorlist is less
700 than this many seconds old then yum will not download another
701 copy of the mirrorlist, it has the same extra format as meta‐
702 data_expire. If you find that yum is not downloading the mir‐
703 rorlists as often as you would like lower the value of this
704 option.
705 mdpolicy You can select from different metadata download poli‐
708 cies depending on how much data you want to download with the
709 main repository metadata index. The advantages of downloading
710 more metadata with the index is that you can't get into situa‐
711 tions where you need to use that metadata later and the versions
712 available aren't compatible (or the user lacks privileges) and
713 that if the metadata is corrupt in any way yum will revert to
714 the previous metadata.
715 `instant' - Just download the new metadata index, this is
717 roughly what yum always did, however it now does some checking
718 on the index and reverts if it classifies it as bad.
719 `group:primary' - Download the primary metadata with the index.
721 This contains most of the package information and so is almost
722 always required anyway.
723 `group:small' - With the primary also download the updateinfo
725 metadata, groups, and pkgtags. This is required for yum-security
726 operations and it also used in the graphical clients. This file
727 also tends to be significantly smaller than most others. This is
728 the default.
729 `group:main' - With the primary and updateinfo download the
731 filelists metadata and the group metadata. The filelists data is
732 required for operations like "yum install /bin/bash", and also
733 some dependency resolutions require it. The group data is used
734 in some graphical clients and for group operations like "yum
735 grouplist Base".
736 `group:all' - Download all metadata listed in the index, cur‐
738 rently the only one not listed above is the other metadata,
739 which contains the changelog information which is used by yum-
740 changelog. This is what "yum makecache" uses.
741 mddownloadpolicy You can select which kinds of repodata you
744 would prefer yum to download:
745 `sqlite' - Download the .sqlite files, if available. This is
747 currently slightly faster, once they are downloaded. However
748 these files tend to be bigger, and thus. take longer to down‐
749 load.
750 `xml' - Download the .XML files, which yum will do anyway as a
752 fallback on the other options. These files tend to be smaller,
753 but they require parsing/converting locally after download and
754 some aditional checks are performed on them each time they are
755 used.
756 multilib_policy Can be set to 'all' or 'best'. All means install
759 all possible arches for any package you want to install. There‐
760 fore yum install foo will install foo.i386 and foo.x86_64 on
761 x86_64, if it is available. Best means install the best arch for
762 this platform, only.
763 bugtracker_url URL where bugs should be filed for yum. Config‐
766 urable for local versions or distro-specific bugtrackers.
767 color Whether to display colorized output automatically, depend‐
770 ing on the output terminal, can be changed to always (using ANSI
771 codes) or never. Default is `auto'. Possible values are: auto,
772 never, always. Command-line option: --color
773 color_list_installed_older The colorization/highlighting for
776 packages in list/info installed which are older than the latest
777 available package with the same name and arch. Default is
778 `bold'. Possible values are a comma separated list containing:
779 bold, blink, dim, reverse, underline, fg:black, fg:red,
780 fg:green, fg:yellow, fg:blue, fg:magenta, fg:cyan, fg:white,
781 bg:black, bg:red, bg:green, bg:yellow, bg:blue, bg:magenta,
782 bg:cyan, bg:white.
783 color_list_installed_newer The colorization/highlighting for
786 packages in list/info installed which are newer than the latest
787 available package with the same name and arch. Default is
788 `bold,yellow'. See color_list_installed_older for possible val‐
789 ues.
790 color_list_installed_reinstall The colorization/highlighting for
793 packages in list/info installed which is the same version as the
794 latest available package with the same name and arch. Default
795 is `normal'. See color_list_installed_older for possible val‐
796 ues.
797 color_list_installed_running_kernel The colorization/highlight‐
800 ing for kernel packages in list/info installed which is the same
801 version as the running kernel. Default is `bold,underline. See
802 color_list_installed_older for possible values.
803 color_list_installed_extra The colorization/highlighting for
806 packages in list/info installed which has no available package
807 with the same name and arch. Default is `bold,red'. See
808 color_list_installed_older for possible values.
809 color_list_available_upgrade The colorization/highlighting for
812 packages in list/info available which is an upgrade for the lat‐
813 est installed package with the same name and arch. Default is
814 `bold,blue'. See color_list_installed_older for possible val‐
815 ues.
816 color_list_available_downgrade The colorization/highlighting for
819 packages in list/info available which is a downgrade for the
820 latest installed package with the same name and arch. Default
821 is `dim,cyan'. See color_list_installed_older for possible val‐
822 ues.
823 color_list_available_install The colorization/highlighting for
826 packages in list/info available which has no installed package
827 with the same name and arch. Default is `normal'. See
828 color_list_installed_older for possible values.
829 color_list_available_reinstall The colorization/highlighting for
832 packages in list/info available which is the same version as the
833 installed package with the same name and arch. Default is
834 `bold,underline,green. See color_list_installed_older for pos‐
835 sible values.
836 color_list_available_running_kernel The colorization/highlight‐
839 ing for kernel packages in list/info available which is the same
840 version as the running kernel. Default is `bold,underline. See
841 color_list_installed_older for possible values.
842 color_search_match The colorization/highlighting for text
845 matches in search. Default is `bold'. See
846 color_list_installed_older for possible values.
847 color_update_installed The colorization/highlighting for pack‐
850 ages in the "updates list" which are installed. The updates list
851 is what is printed when you run "yum update", "yum list
852 updates", "yum list obsoletes" and "yum check-update". Default
853 is `normal'. See color_list_installed_older for possible val‐
854 ues.
855 color_update_local The colorization/highlighting for packages in
858 the "updates list" which are already downloaded. The updates
859 list is what is printed when you run "yum update", "yum list
860 updates", "yum list obsoletes" and "yum check-update". Default
861 is `bold'. See color_list_installed_older for possible values.
862 color_update_remote The colorization/highlighting for packages
865 in the "updates list" which need to be downloaded. The updates
866 list is what is printed when you run "yum update", "yum list
867 updates", "yum list obsoletes" and "yum check-update". Default
868 is `normal'. See color_list_installed_older for possible val‐
869 ues.
870 ui_repoid_vars When a repository id is displayed, append these
873 yum variables to the string if they are used in the baseurl/etc.
874 Variables are appended in the order listed (and found). Default
875 is 'releasever basearch'.
876 clean_requirements_on_remove When removing packages (by removal,
879 update or obsoletion) go through each package's dependencies. If
880 any of them are no longer required by any other package then
881 also mark them to be removed. Boolean (1, 0, True, False, yes,
882 no) Defaults to False
883 upgrade_requirements_on_install When installing/rein‐
886 stalling/upgrading packages go through each package's installed
887 dependencies and check for an update. Boolean (1, 0, True,
888 False, yes,no) Defaults to False
889 recheck_installed_requires When upgrading a package do we
892 recheck any requirements that existed in the old package. Turn‐
893 ing this on shouldn't do anything but slow yum depsolving down,
894 however using rpm --nodeps etc. can break the rpmdb and then
895 this will help. Boolean (1, 0, True, False, yes,no) Defaults to
896 False
897 reset_nice If set to true then yum will try to reset the nice
900 value to zero, before running an rpm transaction. Defaults to
901 True.
902 exit_on_lock Should the yum client exit immediately when some‐
904 thing else has the lock. Boolean (1, 0, True, False, yes, no)
905 Defaults to False
906 loadts_ignoremissing Should the load-ts command ignore packages
909 that are missing. This includes packages in the TS to be
910 removed, which aren't installed, and packages in the TS to be
911 added, which aren't available. If this is set to true, and an
912 rpm is missing then loadts_ignorenewrpm is automatically set to
913 true. Boolean (1, 0, True, False, yes, no) Defaults to False
914 loadts_ignorerpm Should the load-ts command ignore the rpmdb
917 version (yum version nogroups) or abort if there is a mismatch
918 between the TS file and the current machine. If this is set to
919 true, then loadts_ignorenewrpm is automatically set to true.
920 Boolean (1, 0, True, False, yes, no) Defaults to False
921 loadts_ignorenewrpm Should the load-ts command ignore the future
924 rpmdb version or abort if there is a mismatch between the TS
925 file and what will happen on the current machine. Note that if
926 loadts_ignorerpm is True, this option does nothing. Boolean (1,
927 0, True, False, yes, no) Defaults to False
928 autosavets Should yum automatically save a transaction to a file
931 when the transaction is solved but not run. Boolean (1, 0,
932 True, False, yes, no) Defaults to True
933 fssnap_automatic_pre Should yum try to automatically create a
936 snapshot before it runs a transaction. Boolean (1, 0, True,
937 False, yes, no) Defaults to False
938 fssnap_automatic_post Should yum try to automatically create a
941 snapshot after it runs a transaction. Boolean (1, 0, True,
942 False, yes, no) Defaults to False
943 fssnap_automatic_keep How many old snapshots should yum keep
946 when trying to automatically create a new snapshot. Setting to 0
947 disables this feature. Default is '1'.
948 fssnap_percentage The size of new snaphosts, expressed as a per‐
951 centage of the old origin device. Any number between 1 and 100.
952 Default is '100'.
953 fssnap_devices The origin LVM devices to use for snapshots.
956 Wildcards and negation are allowed, first match (positive or
957 negative) wins. Default is: !*/swap !*/lv_swap
958 glob:/etc/yum/fssnap.d/*.conf
959 fssnap_abort_on_errors When fssnap_automatic_pre or fssnap_auto‐
962 matic_post is enabled, it's possible to specify which fssnap
963 errors should make the transaction fail. The default is `any'.
964 `broken-setup' - Abort current transaction if snapshot support
966 is unavailable because lvm is missing or broken.
967 `snapshot-failure' - Abort current transaction if creating a
969 snapshot fails (e.g. there is not enough free space to make a
970 snapshot).
971 `any' - Abort current transaction if any of the above occurs.
973 `none' - Never abort a transaction in case of errors.
975 depsolve_loop_limit Set the number of times any attempt to dep‐
978 solve before we just give up. This shouldn't be needed as yum
979 should always solve or fail, however it has been observed that
980 it can loop forever with very large system upgrades. Setting
981 this to `0' (or "<forever>") makes yum try forever. Default is
982 `100'.
983 usr_w_check Either `0' or `1'. Set this to `0' to disable the
986 checking for writability on /usr in the installroot (when going
987 into the depsolving stage). Default is `1' (perform the check).
988 skip_missing_names_on_install If set to False, 'yum install'
991 will fail if it can't find any of the provided names (package,
992 group, rpm file). Boolean (1, 0, True, False, yes, no). Defaults
993 to True.
994 skip_missing_names_on_update If set to False, 'yum update' will
997 fail if it can't find any of the provided names (package, group,
998 rpm file). It will also fail if the provided name is a package
999 which is available, but not installed. Boolean (1, 0, True,
1000 False, yes, no). Defaults to True.
1001 shell_exit_status Determines the exit status that should be
1004 returned by `yum shell' when it terminates after reading the
1005 `exit' command or EOF. Possible values are: 0, ?. If ? is set,
1006 the exit status is that of the last command executed before
1007 `exit' (bash-like behavior). Defaults to 0.
1008
1011 The repository section(s) take the following form:
1012 Example: [repositoryid]
1014 name=Some name for this repository
1015 baseurl=url://path/to/repository/
1016 repositoryid Must be a unique name for each repository, one
1019 word.
1020 name A human readable string describing the repository.
1023 baseurl Must be a URL to the directory where the yum reposi‐
1026 tory's `repodata' directory lives. Can be an http://, ftp:// or
1027 file:// URL.
1028 You can specify multiple URLs in one baseurl statement. The best
1030 way to do this is like this:
1031 [repositoryid]
1032 name=Some name for this repository
1033 baseurl=url://server1/path/to/repository/
1034 url://server2/path/to/repository/
1035 url://server3/path/to/repository/
1036 The URLs listed are considered different locations (mirrors) of
1038 the same repository. That means, if one URL fails, another one
1039 is tried, and so on. The order in which the URLs are tried is
1040 determined by the failovermethod option.
1041 If you list more than one baseurl= statement in a repository you
1043 will find yum will ignore the earlier ones and probably act
1044 bizarrely. Don't do this, you've been warned.
1045 You can use HTTP basic auth by prepending "user:password@" to
1047 the server name in the baseurl line. For example:
1048 "baseurl=http://user:passwd@example.com/".
1049 metalink Specifies a URL to a metalink file for the repomd.xml,
1052 a list of mirrors for the entire repository are generated by
1053 converting the mirrors for the repomd.xml file to a baseurl. The
1054 metalink file also contains the latest timestamp from the data
1055 in the repomd.xml, the length of the repomd.xml and checksum
1056 data. This data is checked against any downloaded repomd.xml
1057 file and all of the information from the metalink file must
1058 match. This can be used instead of or with the baseurl option.
1059 Substitution variables, described below, can be used with this
1060 option. This option disables the mirrorlist option. As a spe‐
1061 cial hack is the mirrorlist URL contains the word "metalink"
1062 then the value of mirrorlist is copied to metalink (if metalink
1063 is not set).
1064 mirrorlist Specifies a URL to a file containing a list of
1067 baseurls. This can be used instead of or with the baseurl
1068 option. Substitution variables, described below, can be used
1069 with this option. As a special hack is the mirrorlist URL con‐
1070 tains the word "metalink" then the value of mirrorlist is copied
1071 to metalink (if metalink is not set).
1072 enabled Either `1' or `0'. This tells yum whether or not use
1076 this repository.
1077 keepcache Overrides the keepcache option from the [main] section
1080 for this repository.
1081 gpgcheck Either `1' or `0'. This tells yum whether or not it
1084 should perform a GPG signature check on the packages gotten from
1085 this repository.
1086 repo_gpgcheck Either `1' or `0'. This tells yum whether or not
1089 it should perform a GPG signature check on the repodata from
1090 this repository.
1091 gpgkey A URL pointing to the ASCII-armored GPG key file for the
1094 repository. This option is used if yum needs a public key to
1095 verify a package and the required key hasn't been imported into
1096 the RPM database. If this option is set, yum will automatically
1097 import the key from the specified URL. You will be prompted
1098 before the key is installed unless the assumeyes option is set.
1099 Multiple URLs may be specified here in the same manner as the
1101 baseurl option (above). If a GPG key is required to install a
1102 package from a repository, all keys specified for that reposi‐
1103 tory will be installed.
1104 gpgcakey A URL pointing to the ASCII-armored CA key file for the
1107 repository. This is a normal gpg public key - but this key will
1108 be used to validate detached signatures of all other keys. The
1109 idea is you are asked to confirm import for this key. After that
1110 any other gpg key needed for package or repository verification,
1111 if it has a detached signature which matches this key will be
1112 automatically imported without user confirmation.
1113 exclude Same as the [main] exclude option but only for this
1116 repository. Substitution variables, described below, are hon‐
1117 ored here.
1118 Can be disabled using --disableexcludes.
1120 includepkgs Inverse of exclude, yum will exclude any package in
1123 the repo. that doesn't match this list. This works in conjunc‐
1124 tion with exclude and doesn't override it, so if you
1125 exclude=*.i386 and includepkgs=python* then only packages start‐
1126 ing with python that do not have an i386 arch. will be seen by
1127 yum in this repo.
1128 Substitution variables, described below, are honored here.
1130 Can be disabled using --disableexcludes.
1132 enablegroups Either `0' or `1'. Determines whether yum will
1135 allow the use of package groups for this repository. Default is
1136 `1' (package groups are allowed).
1137 failovermethod Either `roundrobin' or `priority'.
1140 `roundrobin' randomly selects a URL out of the list of URLs to
1142 start with and proceeds through each of them as it encounters a
1143 failure contacting the host.
1144 `priority' starts from the first baseurl listed and reads
1146 through them sequentially.
1147 failovermethod defaults to `roundrobin' if not specified.
1149 keepalive Either `1' or `0'. This tells yum whether or not
1152 HTTP/1.1 keepalive should be used with this repository. See the
1153 global option in the [main] section above for more information.
1154 timeout Overrides the timeout option from the [main] section for
1157 this repository.
1158 http_caching Overrides the http_caching option from the [main]
1161 section for this repository.
1162 retries Overrides the retries option from the [main] section for
1165 this repository.
1166 throttle Overrides the throttle option from the [main] section
1169 for this repository.
1170 bandwidth Overrides the bandwidth option from the [main] section
1173 for this repository.
1174 ip_resolve Overrides the ip_resolve option from the [main] sec‐
1177 tion for this repository.
1178 ftp_disable_epsv Overrides the ftp_disable_epsv option from the
1181 [main] section for this repository.
1182 deltarpm_percentage Overrides the deltarpm_percentage option
1185 from the [main] section for this repository.
1186 deltarpm_metadata_percentage Overrides the deltarpm_meta‐
1189 data_percentage option from the [main] section for this reposi‐
1190 tory.
1191 sslcacert Overrides the sslcacert option from the [main] section
1194 for this repository.
1195 sslverify Overrides the sslverify option from the [main] section
1198 for this repository.
1199 sslclientcert Overrides the sslclientcert option from the [main]
1202 section for this repository.
1203 sslclientkey Overrides the sslclientkey option from the [main]
1206 section for this repository.
1207 ssl_check_cert_permissions Overrides the ssl_check_cert_permis‐
1210 sions option from the [main] section for this repository.
1211 metadata_expire Overrides the metadata_expire option from the
1214 [main] section for this repository.
1215 metadata_expire_filter Overrides the metadata_expire_filter
1218 option from the [main] section for this repository.
1219 mirrorlist_expire Overrides the mirrorlist_expire option from
1222 the [main] section for this repository.
1223 proxy URL to the proxy server for this repository. Set to
1226 '_none_' to disable the global proxy setting for this reposi‐
1227 tory. If this is unset it inherits it from the global setting
1228 proxy_username username to use for proxy. If this is unset it
1231 inherits it from the global setting
1232 proxy_password password for this proxy. If this is unset it
1235 inherits it from the global setting
1236 username username to use for basic authentication to a repo or
1240 really any url. If this is unset it inherits it from the global
1241 setting
1242 password password to use with the username for basic authentica‐
1245 tion. If this is unset it inherits it from the global setting
1246 cost relative cost of accessing this repository. Useful for
1249 weighing one repo's packages as greater/less than any other.
1250 defaults to 1000
1251 skip_if_unavailable If set to True yum will continue running if
1254 this repository cannot be contacted for any reason. This should
1255 be set carefully as all repos are consulted for any given com‐
1256 mand. Defaults to False.
1257 async If set to True Yum will download packages and metadata
1260 from this repo in parallel, if possible. Defaults to True.
1261 ui_repoid_vars Overrides the ui_repoid_vars option from the
1264 [main] section for this repository.
1265 compare_providers_priority During depsolving, when choosing the
1268 best provider among several, yum will respect the priority of
1269 each provider's repository (note that there are other factors
1270 which yum considers, which may overweigh the repository prior‐
1271 ity). The value is an integer from 1 to 99, 1 being the most
1272 preferred repository, and 99 being the least preferred one. By
1273 default all repositories have the priority of 80.
1274
1277 The inclusion of external configuration files is supported for
1278 /etc/yum.conf and the .repo files in the /etc/yum.repos.d directory. To
1279 include a URL, use a line of the following format:
1280 include=url://to/some/location
1282 The configuration file will be inserted at the position of the
1284 "include=" line. Included files may contain further include lines. Yum
1285 will abort with an error if an inclusion loop is detected.
1286
1289 Any of the configurations options which are a list of items can be
1290 specfied using the glob syntax: glob:/etc/path/somewhere.d/*.conf. This
1291 will read in all files matching that glob and include all lines in each
1292 file (excluding comments and blank lines) as items in the list.
1293
1295 There are a number of variables you can use to ease maintenance of
1296 yum's configuration files. They are available in the values of several
1297 options including name, baseurl and commands.
1298 $releasever This will be replaced with the value of the version
1300 of the package listed in distroverpkg. This defaults to the ver‐
1301 sion of `redhat-release' package.
1302 $arch This will be replaced with the architecture or your system
1305 as detected by yum.
1306 $basearch This will be replaced with your base architecture in
1309 yum. For example, if your $arch is i686 your $basearch will be
1310 i386.
1311 $uuid This will be replaced with a unique but persistent uuid
1314 for this machine. The value that is first generated will be
1315 stored in /var/lib/yum/uuid and reused until this file is
1316 deleted.
1317 $YUM0-$YUM9 These will be replaced with the value of the shell
1320 environment variable of the same name. If the shell environment
1321 variable does not exist then the configuration file variable
1322 will not be replaced.
1323 When variable names are parsed in a string, all alphanumeric characters
1326 and underscores immediately following a $ sign are interpreted as part
1327 of a name. If a variable is undefined, it will not be replaced. For
1328 example, the strings $releasever-foo or $releasever/foo will be
1329 expanded with the $releasever value accordingly, whereas $releaseverfoo
1330 or $releasever_foo will not be expanded.
1331 As of 3.2.28, any properly named file in /etc/yum/vars is turned into a
1333 variable named after the filename (or overrides any of the above vari‐
1334 ables). Filenames may contain only alphanumeric characters and under‐
1335 scores and be in lowercase.
1336 Note that no warnings/errors are given if the files are unreadable, so
1338 creating files that only root can read may be confusing for users.
1339 Also note that only the first line will be read and all new line char‐
1341 acters are removed, as a convenience. However, no other checking is
1342 performed on the data. This means it is possible to have bad character
1343 data in any value.
1344
1347 /etc/yum.conf
1348 /etc/yum.repos.d/
1349 /etc/yum/pluginconf.d/
1350 /etc/yum/protected.d
1351 /etc/yum/vars
1352
1355 yum(8)
1356Seth Vidal yum.conf(5)