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 logfile Full directory and file name for where yum should write
78 its log file.
79 gpgcheck Either `1' or `0'. This tells yum whether or not it
82 should perform a GPG signature check on packages. When this is
83 set in the [main] section it sets the default for all reposito‐
84 ries. This option also determines whether or not an install of a
85 package from a local RPM file will be GPG signature checked. The
86 default is `0'.
87 repo_gpgcheck Either `1' or `0'. This tells yum whether or not
90 it should perform a GPG signature check on the repodata. When
91 this is set in the [main] section it sets the default for all
92 repositories. The default is `0'.
93 skip_broken Either `1' or `0'. Resolve depsolve problems by
96 removing packages that are causing problems from the transac‐
97 tion.
98 assumeyes Either `1' or `0'. Determines whether or not yum
101 prompts for confirmation of critical actions. Default is `0' (do
102 prompt).
103 Command-line option: -y
104 alwaysprompt Either `1' or `0'. Without this option, yum will
107 not prompt for confirmation when the list of packages to be
108 installed exactly matches those given on the command line.
109 Unless assumeyes is enabled, it will still prompt for package
110 removal, or when additional packages need to be installed to
111 fulfill dependencies. Default is `1'.
112 tolerant Either `1' or `0'. If enabled, then yum will be toler‐
115 ant of errors on the command line with regard to packages. For
116 example: if you request to install foo, bar and baz and baz is
117 installed; yum won't error out complaining that baz is already
118 installed. Default to `0' (not tolerant).
119 Command-line option: -t
120 exclude List of packages to exclude from updates or installs.
123 This should be a space separated list. Shell globs using wild‐
124 cards (eg. * and ?) are allowed.
125 exactarch Either `1' or `0'. Set to `1' to make yum update only
128 update the architectures of packages that you have installed.
129 ie: with this enabled yum will not install an i686 package to
130 update an i386 package. Default is `1'.
131 installonlypkgs List of package provides that should only ever
134 be installed, never updated. Kernels in particular fall into
135 this category. Defaults to kernel, kernel-bigmem, kernel-enter‐
136 prise, kernel-smp, kernel-modules, kernel-debug, kernel-unsup‐
137 ported, kernel-source, kernel-devel, kernel-PAE, kernel-PAE-
138 debug.
139 Note that because these are provides, and not just package
141 names, kernel-devel will also apply to kernel-debug-devel, etc.
142 installonly_limit Number of packages listed in installonlypkgs
145 to keep installed at the same time. Setting to 0 disables this
146 feature. Default is '0'. Note that this functionality used to be
147 in the "installonlyn" plugin, where this option was altered via.
148 tokeep. Note that as of version 3.2.24, yum will now look in
149 the yumdb for a installonly attribute on installed packages. If
150 that attribute is "keep", then they will never be removed.
151 kernelpkgnames List of package names that are kernels. This is
154 really only here for the updating of kernel packages and should
155 be removed out in the yum 2.1 series.
156 showdupesfromrepos Either `0' or `1'. Set to `1' if you wish to
159 show any duplicate packages from any repository, from package
160 listings like the info or list commands. Set to `0' if you want
161 only to see the newest packages from any repository. Default is
162 `0'.
163 obsoletes This option only has affect during an update. It
166 enables yum's obsoletes processing logic. Useful when doing dis‐
167 tribution level upgrades. See also the yum upgrade command docu‐
168 mentation for more details (yum(8)). Default is `true'.
169 Command-line option: --obsoletes
170 overwrite_groups Either `0' or `1'. Used to determine yum's be‐
173 haviour if two or more repositories offer the package groups
174 with the same name. If overwrite_groups is `1' then the group
175 packages of the last matching repository will be used. If over‐
176 write_groups is `0' then the groups from all matching reposito‐
177 ries will be merged together as one large group.
178 groupremove_leaf_only Either `0' or `1'. Used to determine yum's
181 behaviour when the groupremove command is run. If groupre‐
182 move_leaf_only is `0' (default) then all packages in the group
183 will be removed. If groupremove_leaf_only is `1' then only
184 those packages in the group that aren't required by another
185 package will be removed.
186 enable_group_conditionals Either `0' or `1'. Determines whether
189 yum will allow the use of conditionals packages. Default is `1'
190 (package conditionals are allowed).
191 group_package_types List of the following: optional, default,
194 mandatory. Tells yum which type of packages in groups will be
195 installed when 'groupinstall' is called. Default is: default,
196 mandatory
197 installroot Specifies an alternative installroot, relative to
200 which all packages will be installed.
201 Command-line option: --installroot
202 distroverpkg The package used by yum to determine the "version"
205 of the distribution. This can be any installed package. Default
206 is `redhat-release'. You can see what provides this manually by
207 using: "yum whatprovides redhat-release".
208 diskspacecheck Either `0' or `1'. Set this to `0' to disable the
211 checking for sufficient diskspace before a RPM transaction is
212 run. Default is `1' (perform the check).
213 tsflags Comma or space separated list of transaction flags to
216 pass to the rpm transaction set. These include 'noscripts',
217 'notriggers', 'nodocs', 'test', with newer rpm versions. You
218 can set all/any of them. However, if you don't know what these
219 do in the context of an rpm transaction set you're best leaving
220 it alone. Default is an empty list.
221 recent Number of days back to look for `recent' packages added
224 to a repository. Used by the list recent command. Default is
225 `7'.
226 retries Set the number of times any attempt to retrieve a file
229 should retry before returning an error. Setting this to `0'
230 makes yum try forever. Default is `10'.
231 keepalive Either `0' or `1'. Set whether HTTP keepalive should
234 be used for HTTP/1.1 servers that support it. This can improve
235 transfer speeds by using one connection when downloading multi‐
236 ple files from a repository. Default is `1'.
237 timeout Number of seconds to wait for a connection before timing
240 out. Defaults to 30 seconds. This may be too short of a time for
241 extremely overloaded sites.
242 http_caching Determines how upstream HTTP caches are instructed
245 to handle any HTTP downloads that Yum does. This option can take
246 the following values:
247 `all' means that all HTTP downloads should be cached.
249 `packages' means that only RPM package downloads should be
251 cached (but not repository metadata downloads).
252 `none' means that no HTTP downloads should be cached.
254 The default is `all'. This is recommended unless you are experi‐
256 encing caching related issues. Try to at least use `packages' to
257 minimize load on repository servers.
258 throttle Enable bandwidth throttling for downloads. This option
261 can be expressed as a absolute data rate in bytes/sec. An SI
262 prefix (k, M or G) may be appended to the bandwidth value (eg.
263 `5.5k' is 5.5 kilobytes/sec, `2M' is 2 Megabytes/sec).
264 Alternatively, this option can specify the percentage of total
266 bandwidth to use (eg. `60%'). In this case the bandwidth option
267 should be used to specify the maximum available bandwidth.
268 Set to `0' to disable bandwidth throttling. This is the default.
270 bandwidth Use to specify the maximum available network bandwidth
273 in bytes/second. Used with the throttle option (above). If
274 throttle is a percentage and bandwidth is `0' then bandwidth
275 throttling will be disabled. If throttle is expressed as a data
276 rate (bytes/sec) then this option is ignored. Default is `0' (no
277 bandwidth throttling).
278 sslcacert Path to the directory containing the databases of the
281 certificate authorities yum should use to verify SSL certifi‐
282 cates. Defaults to none - uses system default
283 sslverify Boolean - should yum verify SSL certificates/hosts at
286 all. Defaults to True
287 sslclientcert Path to the SSL client certificate yum should use
290 to connect to repos/remote sites Defaults to none.
291 sslclientkey Path to the SSL client key yum should use to con‐
294 nect to repos/remote sites Defaults to none.
295 history_record Boolean - should yum record history entries for
298 transactions. This takes some disk space, and some extra time in
299 the transactions. But it allows how to know a lot of information
300 about what has happened before, and display it to the user with
301 the history info/list/summary commands. yum also provides the
302 history undo/redo commands. Defaults to True.
303 Note that if history is recorded, yum uses that information to
305 see if any modifications to the rpmdb have been done outside of
306 yum. These are always bad, from yum's point of view, and so yum
307 will issue a warning and automatically run some of "yum check"
308 to try and find some of the worst problems altering the rpmdb
309 might have caused.
310 This means that turning this option off will stop yum from being
312 able to detect when the rpmdb has changed and thus. it will
313 never warn you or automatically run "yum check". The problems
314 will likely still be there, and yumdb etc. will still be wrong
315 but yum will not warn you about it.
316 history_record_packages This is a list of package names that
319 should be recorded as having helped the transaction. yum plugins
320 have an API to add themselves to this, so it should not normally
321 be necessary to add packages here. Not that this is also used
322 for the packages to look for in --version. Defaults to rpm, yum,
323 yum-metadata-parser.
324 commands List of functional commands to run if no functional
327 commands are specified on the command line (eg. "update foo bar
328 baz quux"). None of the short options (eg. -y, -e, -d) are
329 accepted for this option.
330 syslog_ident Identification (program name) for syslog messages.
333 syslog_facility Facility name for syslog messages, see sys‐
336 log(3). Default is `LOG_USER'.
337 syslog_device Where to log syslog messages. Can be a local
340 device (path) or a host:port string to use a remote syslog. If
341 empty or points to a nonexistent device, syslog logging is dis‐
342 abled. Default is `/dev/log'.
343 proxy URL to the proxy server that yum should use.
346 proxy_username username to use for proxy
349 proxy_password password for this proxy
352 plugins Either `0' or `1'. Global switch to enable or disable
355 yum plugins. Default is `0' (plugins disabled). See the PLUGINS
356 section of the yum(8) man for more information on installing yum
357 plugins.
358 pluginpath A list of directories where yum should look for plug‐
361 in modules. Default is `/usr/share/yum-plugins' and
362 `/usr/lib/yum-plugins'.
363 pluginconfpath A list of directories where yum should look for
366 plugin configuration files. Default is `/etc/yum/pluginconf.d'.
367 metadata_expire Time (in seconds) after which the metadata will
370 expire. So that if the current metadata downloaded is less than
371 this many seconds old then yum will not update the metadata
372 against the repository. If you find that yum is not downloading
373 information on updates as often as you would like lower the
374 value of this option. You can also change from the default of
375 using seconds to using days, hours or minutes by appending a d,
376 h or m respectively. The default is 1.5 hours, to compliment
377 yum-updatesd running once an hour. It's also possible to use
378 the word "never", meaning that the metadata will never expire.
379 Note that when using a metalink file the metalink must always be
380 newer than the metadata for the repository, due to the valida‐
381 tion, so this timeout also applies to the metalink file.
382 mirrorlist_expire Time (in seconds) after which the mirrorlist
385 locally cached will expire. If the current mirrorlist is less
386 than this many seconds old then yum will not download another
387 copy of the mirrorlist, it has the same extra format as meta‐
388 data_expire. If you find that yum is not downloading the mir‐
389 rorlists as often as you would like lower the value of this
390 option.
391 mdpolicy You can select from different metadata download poli‐
394 cies depending on how much data you want to download with the
395 main repository metadata index. The advantages of downloading
396 more metadata with the index is that you can't get into situa‐
397 tions where you need to use that metadata later and the versions
398 available aren't compatible (or the user lacks privileges) and
399 that if the metadata is corrupt in any way yum will revert to
400 the previous metadata.
401 `instant' - Just download the new metadata index, this is
403 roughly what yum always did, however it now does some checking
404 on the index and reverts if it classifies it as bad.
405 `group:primary' - Download the primary metadata with the index.
407 This contains most of the package information and so is almost
408 always required anyway. This is the default.
409 `group:small' - With the primary also download the updateinfo
411 metadata, this is required for yum-security operations and it
412 also used in the graphical clients. This file also tends to be
413 significantly smaller than most others.
414 `group:main' - With the primary and updateinfo download the
416 filelists metadata and the group metadata. The filelists data is
417 required for operations like "yum install /bin/bash", and also
418 some dependency resolutions require it. The group data is used
419 in some graphical clients and for group operations like "yum
420 grouplist Base".
421 `group:all' - Download all metadata listed in the index, cur‐
423 rently the only one not listed above is the other metadata,
424 which contains the changelog information which is used by yum-
425 changelog. This is what "yum makecache" uses.
426 multilib_policy Can be set to 'all' or 'best'. All means install
429 all possible arches for any package you want to install. There‐
430 fore yum install foo will install foo.i386 and foo.x86_64 on
431 x86_64, if it is available. Best means install the best arch for
432 this platform, only.
433 bugtracker_url URL where bugs should be filed for yum. Config‐
436 urable for local versions or distro-specific bugtrackers.
437 color Display colorized output automatically, depending on the
440 output terminal, always (using ANSI codes) or never. Command-
441 line option: --color
442 color_list_installed_older The colorization/highlighting for
445 packages in list/info installed which are older than the latest
446 available package with the same name and arch. Default is
447 `bold'. Possible values are a comma separated list containing:
448 bold, blink, dim, reverse, underline, fg:black, fg:red,
449 fg:green, fg:yellow, fg:blue, fg:magenta, fg:cyan, fg:white,
450 bg:black, bg:red, bg:green, bg:yellow, bg:blue, bg:magenta,
451 bg:cyan, bg:white.
452 color_list_installed_newer The colorization/highlighting for
455 packages in list/info installed which are newer than the latest
456 available package with the same name and arch. Default is
457 `bold,yellow'. See color_list_installed_older for possible val‐
458 ues.
459 color_list_installed_reinstall The colorization/highlighting for
462 packages in list/info installed which is the same version as the
463 latest available package with the same name and arch. Default
464 is `normal'. See color_list_installed_older for possible val‐
465 ues.
466 color_list_installed_extra The colorization/highlighting for
469 packages in list/info installed which has no available package
470 with the same name and arch. Default is `bold,red'. See
471 color_list_installed_older for possible values.
472 color_list_available_upgrade The colorization/highlighting for
475 packages in list/info available which is an upgrade for the lat‐
476 est installed package with the same name and arch. Default is
477 `bold,blue'. See color_list_installed_older for possible val‐
478 ues.
479 color_list_available_downgrade The colorization/highlighting for
482 packages in list/info available which is a downgrade for the
483 latest installed package with the same name and arch. Default
484 is `dim,cyan'. See color_list_installed_older for possible val‐
485 ues.
486 color_list_available_install The colorization/highlighting for
489 packages in list/info available which has no installed package
490 with the same name and arch. Default is `normal'. See
491 color_list_installed_older for possible values.
492 color_list_available_reinstall The colorization/highlighting for
495 packages in list/info available which is the same version as the
496 installed package with the same name and arch. Default is
497 `bold,underline,green. See color_list_installed_older for pos‐
498 sible values.
499 color_search_match The colorization/highlighting for text
502 matches in search. Default is `bold'. See
503 color_list_installed_older for possible values.
504 color_update_installed The colorization/highlighting for pack‐
507 ages in the "updates list" which are installed. The updates list
508 is what is printed when you run "yum update", "yum list
509 updates", "yum list obsoletes" and "yum check-update". Default
510 is `normal'. See color_list_installed_older for possible val‐
511 ues.
512 color_update_local The colorization/highlighting for packages in
515 the "updates list" which are already downloaded. The updates
516 list is what is printed when you run "yum update", "yum list
517 updates", "yum list obsoletes" and "yum check-update". Default
518 is `bold'. See color_list_installed_older for possible values.
519 color_update_remote The colorization/highlighting for packages
522 in the "updates list" which need to be downloaded. The updates
523 list is what is printed when you run "yum update", "yum list
524 updates", "yum list obsoletes" and "yum check-update". Default
525 is `normal'. See color_list_installed_older for possible val‐
526 ues.
527
530 The repository section(s) take the following form:
531 Example: [repositoryid]
533 name=Some name for this repository
534 baseurl=url://path/to/repository/
535 repositoryid Must be a unique name for each repository, one
538 word.
539 name A human readable string describing the repository.
542 baseurl Must be a URL to the directory where the yum reposi‐
545 tory's `repodata' directory lives. Can be an http://, ftp:// or
546 file:// URL. You can specify multiple URLs in one baseurl state‐
547 ment. The best way to do this is like this:
548 [repositoryid]
549 name=Some name for this repository
550 baseurl=url://server1/path/to/repository/
551 url://server2/path/to/repository/
552 url://server3/path/to/repository/
553 If you list more than one baseurl= statement in a repository you
555 will find yum will ignore the earlier ones and probably act
556 bizarrely. Don't do this, you've been warned.
557 You can use HTTP basic auth by prepending "user:password@" to
559 the server name in the baseurl line. For example:
560 "baseurl=http://user:passwd@example.com/".
561 metalink Specifies a URL to a metalink file for the repomd.xml,
564 a list of mirrors for the entire repository are generated by
565 converting the mirrors for the repomd.xml file to a baseurl. The
566 metalink file also contains the latest timestamp from the data
567 in the repomd.xml, the length of the repomd.xml and checksum
568 data. This data is checked against any downloaded repomd.xml
569 file and all of the information from the metalink file must
570 match. This can be used instead of or with the baseurl option.
571 Substitution variables, described below, can be used with this
572 option. This option disables the mirrorlist option. As a spe‐
573 cial hack is the mirrorlist URL contains the word "metalink"
574 then the value of mirrorlist is copied to metalink (if metalink
575 is not set).
576 mirrorlist Specifies a URL to a file containing a list of
579 baseurls. This can be used instead of or with the baseurl
580 option. Substitution variables, described below, can be used
581 with this option. As a special hack is the mirrorlist URL con‐
582 tains the word "metalink" then the value of mirrorlist is copied
583 to metalink (if metalink is not set).
584 enabled Either `1' or `0'. This tells yum whether or not use
588 this repository.
589 gpgcheck Either `1' or `0'. This tells yum whether or not it
592 should perform a GPG signature check on the packages gotten from
593 this repository.
594 repo_gpgcheck Either `1' or `0'. This tells yum whether or not
597 it should perform a GPG signature check on the repodata from
598 this repository.
599 gpgkey A URL pointing to the ASCII-armored GPG key file for the
602 repository. This option is used if yum needs a public key to
603 verify a package and the required key hasn't been imported into
604 the RPM database. If this option is set, yum will automatically
605 import the key from the specified URL. You will be prompted
606 before the key is installed unless the assumeyes option is set.
607 Multiple URLs may be specified here in the same manner as the
609 baseurl option (above). If a GPG key is required to install a
610 package from a repository, all keys specified for that reposi‐
611 tory will be installed.
612 exclude Same as the [main] exclude option but only for this
615 repository. Substitution variables, described below, are hon‐
616 ored here.
617 includepkgs Inverse of exclude. This is a list of packages you
620 want to use from a repository. If this option lists only one
621 package then that is all yum will ever see from the repository.
622 Defaults to an empty list. Substitution variables, described
623 below, are honored here.
624 enablegroups Either `0' or `1'. Determines whether yum will
627 allow the use of package groups for this repository. Default is
628 `1' (package groups are allowed).
629 failovermethod Either `roundrobin' or `priority'.
632 `roundrobin' randomly selects a URL out of the list of URLs to
634 start with and proceeds through each of them as it encounters a
635 failure contacting the host.
636 `priority' starts from the first baseurl listed and reads
638 through them sequentially.
639 failovermethod defaults to `roundrobin' if not specified.
641 keepalive Either `1' or `0'. This tells yum whether or not
644 HTTP/1.1 keepalive should be used with this repository. See the
645 global option in the [main] section above for more information.
646 timeout Overrides the timeout option from the [main] section for
649 this repository.
650 http_caching Overrides the http_caching option from the [main]
653 section for this repository.
654 retries Overrides the retries option from the [main] section for
657 this repository.
658 throttle Overrides the throttle option from the [main] section
661 for this repository.
662 bandwidth Overrides the bandwidth option from the [main] section
665 for this repository.
666 sslcacert Overrides the sslcacert option from the [main] section
670 for this repository.
671 sslverify Overrides the sslverify option from the [main] section
674 for this repository.
675 sslclientcert Overrides the sslclientcert option from the [main]
678 section for this repository.
679 sslclientkey Overrides the sslclientkey option from the [main]
682 section for this repository.
683 metadata_expire Overrides the metadata_expire option from the
687 [main] section for this repository.
688 mirrorlist_expire Overrides the mirrorlist_expire option from
691 the [main] section for this repository.
692 proxy URL to the proxy server for this repository. Set to
695 '_none_' to disable the global proxy setting for this reposi‐
696 tory. If this is unset it inherits it from the global setting
697 proxy_username username to use for proxy. If this is unset it
700 inherits it from the global setting
701 proxy_password password for this proxy. If this is unset it
704 inherits it from the global setting
705 cost relative cost of accessing this repository. Useful for
708 weighing one repo's packages as greater/less than any other.
709 defaults to 1000
710 skip_if_unavailable If set to True yum will continue running if
713 this repository cannot be contacted for any reason. This should
714 be set carefully as all repos are consulted for any given com‐
715 mand. Defaults to False.
716
718 The inclusion of external configuration files is supported for
719 /etc/yum.conf and the .repo files in the /etc/yum.repos.d directory. To
720 include a URL, use a line of the following format:
721 include=url://to/some/location
723 The configuration file will be inserted at the position of the
725 "include=" line. Included files may contain further include lines. Yum
726 will abort with an error if an inclusion loop is detected.
727
730 Any of the configurations options which are a list of items can be
731 specfied using the glob syntax: glob:/etc/path/somewhere.d/*.conf. This
732 will read in all files matching that glob and include all lines in each
733 file (excluding comments and blank lines) as items in the list.
734
736 There are a number of variables you can use to ease maintenance of
737 yum's configuration files. They are available in the values of several
738 options including name, baseurl and commands.
739 $releasever This will be replaced with the value of the version
741 of the package listed in distroverpkg. This defaults to the ver‐
742 sion of `redhat-release' package.
743 $arch This will be replaced with your architecture as listed by
746 os.uname()[4] in Python.
747 $basearch This will be replaced with your base architecture in
750 yum. For example, if your $arch is i686 your $basearch will be
751 i386.
752 $uuid This will be replaced with a unique but persistent uuid
755 for this machine. The value that is first generated will be
756 stored in /var/lib/yum/uuid and reused until this file is
757 deleted.
758 $YUM0-$YUM9 These will be replaced with the value of the shell
761 environment variable of the same name. If the shell environment
762 variable does not exist then the configuration file variable
763 will not be replaced.
764 As of 3.2.28, any file in /etc/yum/vars is turned into a variable named
767 after the filename (or overrides any of the above variables).
768 Note that no warnings/errors are given if the files are unreadable, so
770 creating files that only root can read may be confusing for users.
771 Also note that only the first line will be read and all new line char‐
773 acters are removed, as a convenience. However, no other checking is
774 performed on the data. This means it is possible to have bad character
775 data in any value.
776
779 /etc/yum.conf
780 /etc/yum.repos.d/
781 /etc/yum/pluginconf.d/
782 /etc/yum/protected.d
783 /etc/yum/vars
784
787 yum(8)
788Seth Vidal yum.conf(5)