1yum.conf(5)                 yum configuration file                 yum.conf(5)
2
3
4

NAME

6       yum.conf - Configuration file for yum(8).
7

DESCRIPTION

9       Yum uses a configuration file at /etc/yum.conf.
10
11       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
15

PARAMETERS

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
23

[main] OPTIONS

25       The  [main]  section  must exist for yum to do anything. It consists of
26       the following options:
27
28
29              cachedir Directory where yum  should  store  its  cache  and  db
30              files. The default is `/var/cache/yum'.
31
32
33              cashe_root_dir  Directory  where yum would initialize the cashe,
34              should almost certainly be left  at  the  default.  The  default
35              is`/var/cache/CAShe'.  Note that unlike all other configuration,
36              this does not change with installroot, the  reason  is  so  that
37              multiple install root can share the same data. See man cashe for
38              more info.
39
40
41              persistdir Directory where yum  should  store  information  that
42              should    persist   over   multiple   runs.   The   default   is
43              `/var/lib/yum'.
44
45
46              keepcache Either `1' or `0'. Determines whether or not yum keeps
47              the cache of headers and packages after successful installation.
48              Default is '1' (keep files)
49
50
51              reposdir A list of directories where yum should look  for  .repo
52              files   which   define   repositories   to   use.   Default   is
53              `/etc/yum.repos.d'. Each file in this directory  should  contain
54              one  or  more  repository sections as documented in [repository]
55              options below.  These  will  be  merged  with  the  repositories
56              defined  in  /etc/yum.conf to form the complete set of reposito‐
57              ries that yum will use.
58
59
60              debuglevel Debug message output level. Practical range is  0-10.
61              Default is `2'.
62
63
64              errorlevel  Error message output level. Practical range is 0-10.
65              Default is `2'.
66
67
68              rpmverbosity  Debug  scriptlet  output  level.  'info'  is   the
69              default,  other  options  are: 'critical', 'emergency', 'error',
70              'warn' and 'debug'.
71
72
73              protected_packages This is a list of packages  that  yum  should
74              never  completely  remove.  They  are protected via Obsoletes as
75              well as user/plugin removals.
76
77              The default  is:  yum  glob:/etc/yum/protected.d/*.conf  So  any
78              packages which should be protected can do so by including a file
79              in /etc/yum/protected.d with their package name in it.
80
81              Also if this configuration is set to  anything,  then  yum  will
82              protect  the package corresponding to the running version of the
83              kernel.
84
85
86              protected_multilib Either `1' or `0'. This tells yum whether  or
87              not  it  should perform a check to make sure that multilib pack‐
88              ages are the same version. For example, if this  option  is  off
89              (rpm  behavior)  then  in  some  cases  it might be possible for
90              pkgA-1.x86_64 and pkgA-2.i386 to be installed at the same  time.
91              However this is very rarely desired. Install only packages, like
92              the kernel, are exempt from this check.  The default is `1'.
93
94
95              logfile Full directory and file name for where yum should  write
96              its log file.
97
98
99              gpgcheck  Either  `1'  or  `0'. This tells yum whether or not it
100              should perform a GPG signature check on packages. When  this  is
101              set  in the [main] section it sets the default for all reposito‐
102              ries.  The default is `0'.
103
104              localpkg_gpgcheck Either `1' or `0'. This tells yum  whether  or
105              not  it  should  perform a GPG signature check on local packages
106              (packages in a file, not in a repositoy).  The default is `0'.
107
108
109              repo_gpgcheck Either `1' or `0'. This tells yum whether  or  not
110              it  should  perform  a GPG signature check on the repodata. When
111              this is set in the [main] section it sets the  default  for  all
112              repositories. The default is `0'.
113
114
115              skip_broken  Either  `1'  or  `0'.  Resolve depsolve problems by
116              removing packages that are causing problems  from  the  transac‐
117              tion.
118
119
120              assumeyes  Either  `1'  or  `0'.  Determines  whether or not yum
121              prompts for confirmation of critical actions. Default is `0' (do
122              prompt).
123              Command-line option: -y --assumeyes
124
125
126              assumeno Either `1' or `0'. If yum would prompt for confirmation
127              of critical actions, assume the user chose no. This is basically
128              the  same  as  doing "echo | yum ..."  but is a bit more usable.
129              This  option  overrides  assumeyes,  but  is  still  subject  to
130              alwaysprompt.  Default is `0' (do prompt).
131              Command-line option: --assumeno
132
133
134              alwaysprompt  Either  `1'  or `0'. When set to `0', yum will not
135              prompt  for  confirmation  when  the  list  of  packages  to  be
136              installed  exactly  matches  those  given  on  the command line.
137              Unless assumeyes is enabled,  it  will  prompt  when  additional
138              packages need to be installed to fulfill dependencies regardless
139              of this setting. Note that older  versions  of  yum  would  also
140              always  prompt  for package removal, and that is no longer true.
141              Default is `1'.
142
143
144              tolerant Either `1' or `0'. If  enabled,  yum  will  go  slower,
145              checking  for  things  that shouldn't be possible making it more
146              tolerant of external errors.  Default to `0' (not tolerant).
147              Command-line option: -t
148
149
150              exclude List of packages to exclude from  all  repositories,  so
151              yum works as if that package was never in the repositories. This
152              should be a space separated list.  This is commonly  used  so  a
153              package  isn't  upgraded  or  installed accidentally, but can be
154              used to remove packages in any way that  "yum  list"  will  show
155              packages.   Shell  globs  using  wildcards  (eg.  *  and  ?) are
156              allowed.
157
158              Can be disabled  using  disable_excludes  or  --disableexcludes.
159              Command-line option: -x
160
161
162              disable_excludes  A way to permanently set the --disableexcludes
163              command line option.
164
165
166              query_install_excludes This applies  the  command  line  exclude
167              option  (only, not the configuration exclude above) to installed
168              packages  being  shown  in  some  query   commands   (currently:
169              list/info/search/provides).
170
171
172              installonlypkgs  List  of package provides that should only ever
173              be installed, never updated.  Kernels in  particular  fall  into
174              this  category. Defaults to kernel, kernel-bigmem, kernel-enter‐
175              prise, kernel-smp, kernel-modules,  kernel-debug,  kernel-unsup‐
176              ported,  kernel-source,  kernel-devel,  kernel-PAE,  kernel-PAE-
177              debug.
178
179              Note that because these  are  provides,  and  not  just  package
180              names, kernel-devel will also apply to kernel-debug-devel, etc.
181
182
183              installonly_limit  Number  of packages listed in installonlypkgs
184              to keep installed at the same time. Setting to 0  disables  this
185              feature. Default is '3'. Note that this functionality used to be
186              in the "installonlyn" plugin, where this option was altered  via
187              tokeep.   Note  that  as of version 3.2.24, yum will now look in
188              the yumdb for a installonly attribute on installed packages.  If
189              that attribute is "keep", then they will never be removed.
190
191
192              kernelpkgnames  List  of package names that are kernels. This is
193              really only here for the updating of kernel packages and  should
194              be removed out in the yum 2.1 series.
195
196
197              showdupesfromrepos  Either `0' or `1'. Set to `1' if you wish to
198              show any duplicate packages from any  repository,  from  package
199              listings  like the info or list commands. Set to `0' if you want
200              only to see the newest packages from any repository.  Default is
201              `0'.
202
203
204              obsoletes  This  option  only  has  affect  during an update. It
205              enables yum's obsoletes processing logic. Useful when doing dis‐
206              tribution level upgrades. See also the yum upgrade command docu‐
207              mentation for more details (yum(8)).  Default is `true'.
208              Command-line option: --obsoletes
209
210
211              remove_leaf_only Either `0' or `1'. Used to determine yum's  be‐
212              haviour  when  a package is removed.  If remove_leaf_only is `0'
213              (default) then packages, and their deps, will  be  removed.   If
214              remove_leaf_only  is  `1'  then  only those packages that aren't
215              required by another package will be removed.
216
217
218              repopkgsremove_leaf_only Either `0' or `1'.  Used  to  determine
219              yum's  behaviour  when  the  repo-pkg remove command is run.  If
220              repopkgremove_leaf_only is `0' (default) then  all  packages  in
221              the  repo.  will  be removed.  If repopkgremove_leaf_only is `1'
222              then only those packages in the repo. that  aren't  required  by
223              another package will be removed.  Note that this option does not
224              override remove_leaf_only, so enabling that  option  means  this
225              has almost no affect.
226
227
228              overwrite_groups  Either `0' or `1'. Used to determine yum's be‐
229              haviour if two or more repositories  offer  the  package  groups
230              with  the  same  name. If overwrite_groups is `1' then the group
231              packages of the last matching repository will be used. If  over‐
232              write_groups  is `0' then the groups from all matching reposito‐
233              ries will be merged together as one large group.  Note that this
234              option  does  not  override  remove_leaf_only,  so enabling that
235              option means this has almost no affect.
236
237
238              groupremove_leaf_only Either `0' or `1'. Used to determine yum's
239              behaviour  when  the  groupremove  command  is run.  If groupre‐
240              move_leaf_only is `0' (default) then all packages in  the  group
241              will  be  removed.   If  groupremove_leaf_only  is `1' then only
242              those packages in the group  that  aren't  required  by  another
243              package will be removed.
244
245
246              enable_group_conditionals  Either `0' or `1'. Determines whether
247              yum will allow the use of conditionals packages. Default is  `1'
248              (package conditionals are allowed).
249
250
251              group_package_types  List  of  the following: optional, default,
252              mandatory. Tells yum which type of packages in  groups  will  be
253              installed  when  'groupinstall' is called.  Default is: default,
254              mandatory
255
256
257              group_command List of the following:  simple,  compat,  objects.
258              Tells yum what to do for group install/upgrade/remove commands.
259
260              Simple  acts  like  you  did  yum  group cmd $(repoquery --group
261              --list group), so it is very easy to reason about what will hap‐
262              pen. Alas. this is often not what people want to happen.
263
264              Compat.  works much like simple, except that when you run "group
265              upgrade" it actually runs "group install" (this means  that  you
266              get  any new packages added to the group, but you also get pack‐
267              ages added that were there before and you didn't want).
268
269              Objects makes groups act like a real object, separate  from  the
270              packages  they  contain.  Yum keeps track of the groups you have
271              installed, so "group upgrade" will install new packages for  the
272              group  but  not install old ones. It also knows about group mem‐
273              bers that are installed but weren't installed  as  part  of  the
274              group,  and  won't remove those on "group remove".  Running "yum
275              upgrade" will also run "yum group  upgrade"  (thus.  adding  new
276              packages for all groups).
277
278              Default is: objects
279
280
281              upgrade_group_objects_upgrade Either `0' or `1'. Set this to `0'
282              to disable the automatic running of "group upgrade" when running
283              the  "upgrade"  command,  and group_command is set to "objects".
284              Default is `1' (perform the operation).
285
286
287              autocheck_running_kernel Either `0' or `1'. Set this to  `0'  to
288              disable  the  automatic  checking  of the running kernel against
289              updateinfo  ("yum  updateinfo  check-running-kernel"),  in   the
290              "check-update"  and  "updateinfo  summary" commands.  Default is
291              `1' (perform the check).
292
293
294              installroot Specifies an alternative  installroot,  relative  to
295              which all packages will be installed.
296              Command-line option: --installroot
297
298
299              config_file_path  Specifies  the  path to main the configuration
300              file.  Default is /etc/yum/yum.conf.
301
302
303              check_config_file_age Either `0' or `1'. Specifies  whether  yum
304              should  auto  metadata expire repos.  that are older than any of
305              the configuration files that led to them (usually  the  yum.conf
306              file  and  the  foo.repo  file).   Default  is  `1' (perform the
307              check).
308
309
310              distroverpkg The package used by yum to determine the  "version"
311              of  the  distribution,  this sets $releasever for use in config.
312              files. This can be any installed package.  Default  is  `system-
313              release(releasever)', `redhat-release'. Yum will now look at the
314              version provided by the provide, and if that is  non-empty  then
315              will  use  the  full V(-R), otherwise it uses the version of the
316              package.
317               You can see what provides this manually by using: "yum whatpro‐
318              vides  'system-release(releasever)'  redhat-release" and you can
319              see what $releasever is most easily by using: "yum version".
320
321
322              diskspacecheck Either `0' or `1'. Set this to `0' to disable the
323              checking for sufficient diskspace and inodes before a RPM trans‐
324              action is run. Default is `1' (perform the check).
325
326
327              tsflags Comma or space separated list of  transaction  flags  to
328              pass  to  the  rpm  transaction  set. These include 'noscripts',
329              'notriggers',  'nodocs',  'test',  'justdb'  and   'nocontexts'.
330              'repackage'  is  also available but that does nothing with newer
331              rpm versions.  You can set all/any  of  them.  However,  if  you
332              don't  know  what  these do in the context of an rpm transaction
333              set you're best leaving it alone.  Default  is  an  empty  list.
334              Also see the "yum fs" command, for excluding docs.
335
336
337              override_install_langs   This   is   a  way  to  override  rpm's
338              _install_langs macro. without having to change it  within  rpm's
339              macro file.  Default is nothing (so does nothing).  Also see the
340              "yum fs" command.
341
342
343              recent Number of days back to look for `recent'  packages  added
344              to  a  repository.   Used by the list recent command. Default is
345              `7'.
346
347
348              retries Set the number of times any attempt to retrieve  a  file
349              should  retry  before  returning  an  error. Setting this to `0'
350              makes yum try forever. Default is `10'.
351
352
353              keepalive Either `0' or `1'. Set whether HTTP  keepalive  should
354              be  used  for HTTP/1.1 servers that support it. This can improve
355              transfer speeds by using one connection when downloading  multi‐
356              ple files from a repository. Default is `1'.
357
358
359              timeout Number of seconds to wait for a connection before timing
360              out. Defaults to 30 seconds. This may be too short of a time for
361              extremely overloaded sites.
362
363
364              http_caching  Determines how upstream HTTP caches are instructed
365              to handle any HTTP downloads that Yum does. This option can take
366              the following values:
367
368              `all' means that all HTTP downloads should be cached.
369
370              `packages'  means  that  only  RPM  package  downloads should be
371              cached (but not repository metadata downloads).
372
373              `none' means that no HTTP downloads should be cached.
374
375              The default is `all'. This is recommended unless you are experi‐
376              encing caching related issues. Try to at least use `packages' to
377              minimize load on repository servers.
378
379
380              throttle Enable bandwidth throttling for downloads. This  option
381              can  be  expressed  as  a absolute data rate in bytes/sec. An SI
382              prefix (k, M or G) may be appended to the bandwidth  value  (eg.
383              `5.5k' is 5.5 kilobytes/sec, `2M' is 2 Megabytes/sec).
384
385              Alternatively,  this  option can specify the percentage of total
386              bandwidth to use (eg. `60%'). In this case the bandwidth  option
387              should be used to specify the maximum available bandwidth.
388
389              Set to `0' to disable bandwidth throttling. This is the default.
390
391              Note  that  when multiple downloads run simultaneously the total
392              bandwidth might exceed the throttle limit. You may want to  also
393              set max_connections=1 or scale your throttle option down accord‐
394              ingly.
395
396
397              minrate This sets the low speed threshold in bytes  per  second.
398              If  the  server  is  sending  data slower than this for at least
399              `timeout' seconds, Yum aborts the  connection.  The  default  is
400              `1000'.
401
402
403              bandwidth Use to specify the maximum available network bandwidth
404              in bytes/second.  Used with  the  throttle  option  (above).  If
405              throttle  is  a  percentage  and bandwidth is `0' then bandwidth
406              throttling will be disabled. If throttle is expressed as a  data
407              rate (bytes/sec) then this option is ignored. Default is `0' (no
408              bandwidth throttling).
409
410
411              ip_resolve Determines how yum resolves host names.
412
413              `4' or `IPv4': resolve to IPv4 addresses only.
414
415              `6' or `IPv6': resolve to IPv6 addresses only.
416
417
418              max_connections
419
420              The maximum number of simultaneous connections.  This  overrides
421              the  urlgrabber  default  of 5 connections.  Note that there are
422              also implicit per-mirror limits and the downloader honors  these
423              too.
424
425
426              deltarpm
427
428              When non-zero, delta-RPM files are used if available.  The value
429              specifies the maximum number of  "applydeltarpm"  processes  Yum
430              will spawn, if the value is negative then yum works out how many
431              cores you have  and  multiplies  that  by  the  value  (cores=2,
432              deltarpm=-2; 4 processes). (2 by default).
433
434              Note  that the "applydeltarpm" process uses a significant amount
435              of disk IO, so running too many instances can significantly slow
436              down  all  disk  IO  including  the  downloads that yum is doing
437              (thus. a too high value can make everything slower).
438
439
440              deltarpm_percentage When the relative size of delta  vs  pkg  is
441              larger  than  this,  delta  is  not  used.   Default value is 75
442              (Deltas must be at least 25% smaller than the pkg).  Use `0'  to
443              turn  off delta rpm processing. Local repositories (with file://
444              baseurl) have delta rpms turned off by default.
445
446
447              deltarpm_metadata_percentage When the relative size of  deltarpm
448              metadata  vs  pkgs is larger than this, deltarpm metadata is not
449              downloaded from the repo.  Default value is 100 (Deltarpm  meta‐
450              data must be smaller than the packages from the repo). Note that
451              you can give values over 100, so 200 means that the metadata  is
452              required  to  be half the size of the packages.  Use `0' to turn
453              off this check, and always download metadata.
454
455
456              sslcacert Path to the directory containing the databases of  the
457              certificate  authorities  yum  should use to verify SSL certifi‐
458              cates. Defaults to none - uses system default
459
460
461              sslverify Boolean - should yum verify SSL certificates/hosts  at
462              all. Defaults to True.
463
464              Note  that  the  plugin  yum-rhn-plugin will force this value to
465              true, and may alter other ssl settings (like hostname checking),
466              even if it the machine is not registered.
467
468
469              sslclientcert  Path to the SSL client certificate yum should use
470              to connect to repos/remote sites Defaults to none.
471
472              Note that if you are using curl compiled against NSS (default in
473              Fedora/RHEL),  curl  treats  sslclientcert  values with the same
474              basename as _identical_. This version of  yum  will  check  that
475              this  isn't true and output an error when the repositories "foo"
476              and "bar" violate this, like so:
477
478              sslclientcert basename shared between foo and bar
479
480
481              sslclientkey Path to the SSL client key yum should use  to  con‐
482              nect to repos/remote sites Defaults to none.
483
484
485              ssl_check_cert_permissions  Boolean  -  Whether yum should check
486              the permissions on the paths for the certificates on the reposi‐
487              tory  (both remote and local). If we can't read any of the files
488              then yum will force skip_if_unavailable to  be  true.   This  is
489              most  useful for non-root processes which use yum on repos. that
490              have  client  cert  files  which  are  readable  only  by  root.
491              Defaults to True.
492
493
494              history_record  Boolean  - should yum record history entries for
495              transactions. This takes some disk space, and some extra time in
496              the transactions. But it allows how to know a lot of information
497              about what has happened before, and display it to the user  with
498              the  history  info/list/summary  commands. yum also provides the
499              history undo/redo commands. Defaults to True.
500
501              Note that if history is recorded, yum uses that  information  to
502              see  if any modifications to the rpmdb have been done outside of
503              yum. These are always bad, from yum's point of view, and so  yum
504              will  issue  a warning and automatically run some of "yum check"
505              to try and find some of the worst problems  altering  the  rpmdb
506              might have caused.
507
508              This means that turning this option off will stop yum from being
509              able to detect when the rpmdb has  changed  and  thus.  it  will
510              never  warn  you  or automatically run "yum check". The problems
511              will likely still be there, and yumdb etc. will still  be  wrong
512              but yum will not warn you about it.
513
514
515              history_record_packages  This  is  a  list of package names that
516              should be recorded as having helped the transaction. yum plugins
517              have an API to add themselves to this, so it should not normally
518              be necessary to add packages here. Not that this  is  also  used
519              for the packages to look for in --version. Defaults to rpm, yum,
520              yum-metadata-parser.
521
522
523              history_list_view Which column of information to display in  the
524              "yum  history  list" command. There are currently three options:
525              users, cmds (or commands), auto.
526
527              Older versions of yum acted like "users", which  always  outputs
528              the  user who initiated the yum transaction. You can now specify
529              "commands" which will instead always output the command line  of
530              the  transaction.  You  can  also specify "single-user-commands"
531              which will display the users if there are more than one,  other‐
532              wise it will display the command line.
533
534              You  can also specify "default" which currently selects "single-
535              user-commands".
536
537
538              commands List of functional commands to  run  if  no  functional
539              commands  are specified on the command line (eg. "update foo bar
540              baz quux").  None of the short options  (eg.  -y,  -e,  -d)  are
541              accepted for this option.
542
543
544              syslog_ident Identification (program name) for syslog messages.
545
546
547              syslog_facility  Facility  name  for  syslog  messages, see sys‐
548              log(3).  Default is `LOG_USER'.
549
550
551              syslog_device Where to log  syslog  messages.  Can  be  a  local
552              device  (path) or a host:port string to use a remote syslog.  If
553              empty or points to a nonexistent device, syslog logging is  dis‐
554              abled.  Default is `/dev/log'.
555
556
557              proxy  URL to the proxy server that yum should use.  Set this to
558              `libproxy' to enable  proxy  auto  configuration  via  libproxy.
559              Defaults to direct connection.
560
561
562              proxy_username username to use for proxy
563
564
565              proxy_password password for this proxy
566
567
568              username  username  to use for basic authentication to a repo or
569              really any url.
570
571
572              password password to use with the username for basic authentica‐
573              tion.
574
575
576              plugins  Either  `0'  or `1'. Global switch to enable or disable
577              yum plugins. Default is `0' (plugins disabled). See the  PLUGINS
578              section of the yum(8) man for more information on installing yum
579              plugins.
580
581
582              pluginpath A list of directories where yum should look for plug‐
583              in    modules.    Default    is   `/usr/share/yum-plugins'   and
584              `/usr/lib/yum-plugins'.
585
586
587              pluginconfpath A list of directories where yum should  look  for
588              plugin configuration files.  Default is `/etc/yum/pluginconf.d'.
589
590
591              metadata_expire  Time (in seconds) after which the metadata will
592              expire. So that if the current metadata downloaded is less  than
593              this  many  seconds  old  then  yum will not update the metadata
594              against the repository.  If you find that yum is not downloading
595              information  on  updates  as  often  as you would like lower the
596              value of this option. You can also change from  the  default  of
597              using  seconds to using days, hours or minutes by appending a d,
598              h or m respectively.  The default is 6 hours, to compliment yum-
599              updatesd  running  once  an hour.  It's also possible to use the
600              word "never", meaning that the metadata will never expire.  Note
601              that  when  using  a  metalink  file the metalink must always be
602              newer than the metadata for the repository, due to  the  valida‐
603              tion,  so  this timeout also applies to the metalink file.  Also
604              note that "never" does not override "yum clean expire-cache"
605
606
607              metadata_expire_filter Filter the metadata_expire time, allowing
608              a  trade  of speed for accuracy if a command doesn't require it.
609              Each yum command can specify that it requires a certain level of
610              timeliness  quality  from  the  remote repos. from "I'm about to
611              install/upgrade, so this better be current" to "Anything  that's
612              available is good enough".
613
614              `never' - Nothing is filtered, always obey metadata_expire.
615
616              `read-only:past'  -  Commands that only care about past informa‐
617              tion are filtered from metadata expiring.  Eg. yum history  info
618              (if  history  needs to lookup anything about a previous transac‐
619              tion, then by definition the remote package was available in the
620              past).
621
622              `read-only:present'  -  Commands  that are balanced between past
623              and future.  This is the default.  Eg. yum list yum
624
625              `read-only:future' - Commands that are likely to result in  run‐
626              ning  other commands which will require the latest metadata. Eg.
627              yum check-update
628
629              Note that this option  does  not  override  "yum  clean  expire-
630              cache".
631
632
633              mirrorlist_expire  Time  (in seconds) after which the mirrorlist
634              locally cached will expire.  If the current mirrorlist  is  less
635              than  this  many  seconds old then yum will not download another
636              copy of the mirrorlist, it has the same extra  format  as  meta‐
637              data_expire.   If  you find that yum is not downloading the mir‐
638              rorlists as often as you would like  lower  the  value  of  this
639              option.
640
641
642              mdpolicy  You  can select from different metadata download poli‐
643              cies depending on how much data you want to  download  with  the
644              main  repository  metadata  index. The advantages of downloading
645              more metadata with the index is that you can't get  into  situa‐
646              tions where you need to use that metadata later and the versions
647              available aren't compatible (or the user lacks  privileges)  and
648              that  if  the  metadata is corrupt in any way yum will revert to
649              the previous metadata.
650
651              `instant' - Just  download  the  new  metadata  index,  this  is
652              roughly  what  yum always did, however it now does some checking
653              on the index and reverts if it classifies it as bad.
654
655              `group:primary' - Download the primary metadata with the  index.
656              This  contains  most of the package information and so is almost
657              always required anyway.
658
659              `group:small' - With the primary also  download  the  updateinfo
660              metadata, groups, and pkgtags. This is required for yum-security
661              operations and it also used in the graphical clients. This  file
662              also tends to be significantly smaller than most others. This is
663              the default.
664
665              `group:main' - With the  primary  and  updateinfo  download  the
666              filelists metadata and the group metadata. The filelists data is
667              required for operations like "yum install /bin/bash",  and  also
668              some  dependency  resolutions require it. The group data is used
669              in some graphical clients and for  group  operations  like  "yum
670              grouplist Base".
671
672              `group:all'  -  Download  all metadata listed in the index, cur‐
673              rently the only one not listed  above  is  the  other  metadata,
674              which  contains  the changelog information which is used by yum-
675              changelog. This is what "yum makecache" uses.
676
677
678              mddownloadpolicy You can select  which  kinds  of  repodata  you
679              would prefer yum to download:
680
681              `sqlite'  -  Download  the  .sqlite files, if available. This is
682              currently slightly faster, once  they  are  downloaded.  However
683              these  files  tend  to be bigger, and thus. take longer to down‐
684              load.
685
686              `xml' - Download the .XML files, which yum will do anyway  as  a
687              fallback  on  the other options. These files tend to be smaller,
688              but they require parsing/converting locally after  download  and
689              some  aditional  checks are performed on them each time they are
690              used.
691
692
693              multilib_policy Can be set to 'all' or 'best'. All means install
694              all  possible arches for any package you want to install. There‐
695              fore yum install foo will install  foo.i386  and  foo.x86_64  on
696              x86_64, if it is available. Best means install the best arch for
697              this platform, only.
698
699
700              requires_policy Can be set to 'strong', 'weak' or info'.  Strong
701              means  install  just  the  needed  requirements. Weak means also
702              install any weak requirements. Info means install  all  require‐
703              ments.  This  only  happens on install/reinstall, upgrades/down‐
704              grades do not consult this at all.  Note that yum  will  try  to
705              just drop weak and info requirements on errors.
706
707
708              bugtracker_url  URL  where bugs should be filed for yum. Config‐
709              urable for local versions or distro-specific bugtrackers.
710
711
712              color Whether to display colorized output automatically, depend‐
713              ing on the output terminal, can be changed to always (using ANSI
714              codes) or never.  Default is `auto'.  Possible values are: auto,
715              never, always.  Command-line option: --color
716
717
718              color_list_installed_older   The  colorization/highlighting  for
719              packages in list/info installed which are older than the  latest
720              available  package  with  the  same  name  and arch.  Default is
721              `bold'.  Possible values are a comma separated list  containing:
722              bold,   blink,   dim,   reverse,  underline,  fg:black,  fg:red,
723              fg:green, fg:yellow,  fg:blue,  fg:magenta,  fg:cyan,  fg:white,
724              bg:black,  bg:red,  bg:green,  bg:yellow,  bg:blue,  bg:magenta,
725              bg:cyan, bg:white.
726
727
728              color_list_installed_newer  The  colorization/highlighting   for
729              packages  in list/info installed which are newer than the latest
730              available package with the  same  name  and  arch.   Default  is
731              `bold,yellow'.  See color_list_installed_older for possible val‐
732              ues.
733
734
735              color_list_installed_reinstall The colorization/highlighting for
736              packages in list/info installed which is the same version as the
737              latest available package with the same name and  arch.   Default
738              is  `normal'.   See color_list_installed_older for possible val‐
739              ues.
740
741
742              color_list_installed_running_kernel The  colorization/highlight‐
743              ing for kernel packages in list/info installed which is the same
744              version as the running kernel.  Default is `bold,underline.  See
745              color_list_installed_older for possible values.
746
747
748              color_list_installed_extra   The  colorization/highlighting  for
749              packages in list/info installed which has no  available  package
750              with  the  same  name  and  arch.   Default  is `bold,red'.  See
751              color_list_installed_older for possible values.
752
753
754              color_list_available_upgrade The  colorization/highlighting  for
755              packages in list/info available which is an upgrade for the lat‐
756              est installed package with the same name and arch.   Default  is
757              `bold,blue'.   See  color_list_installed_older for possible val‐
758              ues.
759
760
761              color_list_available_downgrade The colorization/highlighting for
762              packages  in  list/info  available  which is a downgrade for the
763              latest installed package with the same name and  arch.   Default
764              is `dim,cyan'.  See color_list_installed_older for possible val‐
765              ues.
766
767
768              color_list_available_install The  colorization/highlighting  for
769              packages  in  list/info available which has no installed package
770              with  the  same  name  and  arch.   Default  is  `normal'.   See
771              color_list_installed_older for possible values.
772
773
774              color_list_available_reinstall The colorization/highlighting for
775              packages in list/info available which is the same version as the
776              installed  package  with  the  same  name  and arch.  Default is
777              `bold,underline,green.  See color_list_installed_older for  pos‐
778              sible values.
779
780
781              color_list_available_running_kernel  The colorization/highlight‐
782              ing for kernel packages in list/info available which is the same
783              version as the running kernel.  Default is `bold,underline.  See
784              color_list_installed_older for possible values.
785
786
787              color_search_match  The   colorization/highlighting   for   text
788              matches     in     search.      Default    is    `bold'.     See
789              color_list_installed_older for possible values.
790
791
792              color_update_installed The colorization/highlighting  for  pack‐
793              ages in the "updates list" which are installed. The updates list
794              is what  is  printed  when  you  run  "yum  update",  "yum  list
795              updates",  "yum list obsoletes" and "yum check-update".  Default
796              is `normal'.  See color_list_installed_older for  possible  val‐
797              ues.
798
799
800              color_update_local The colorization/highlighting for packages in
801              the "updates list" which are  already  downloaded.  The  updates
802              list  is  what  is  printed when you run "yum update", "yum list
803              updates", "yum list obsoletes" and "yum check-update".   Default
804              is `bold'.  See color_list_installed_older for possible values.
805
806
807              color_update_remote  The  colorization/highlighting for packages
808              in the "updates list" which need to be downloaded.  The  updates
809              list  is  what  is  printed when you run "yum update", "yum list
810              updates", "yum list obsoletes" and "yum check-update".   Default
811              is  `normal'.   See color_list_installed_older for possible val‐
812              ues.
813
814
815              ui_repoid_vars When a repository id is displayed,  append  these
816              yum variables to the string if they are used in the baseurl/etc.
817              Variables are appended in the order listed (and found).  Default
818              is 'releasever basearch'.
819
820
821              clean_requirements_on_remove When removing packages (by removal,
822              update or obsoletion) go through each package's dependencies. If
823              any  of  them  are  no longer required by any other package then
824              also mark them to be removed.  Boolean (1, 0, True, False,  yes,
825              no) Defaults to False
826
827
828              upgrade_requirements_on_install       When      installing/rein‐
829              stalling/upgrading packages go through each package's  installed
830              dependencies  and  check  for  an  update.  Boolean (1, 0, True,
831              False, yes,no) Defaults to False
832
833
834              recheck_installed_requires  When  upgrading  a  package  do   we
835              recheck  any requirements that existed in the old package. Turn‐
836              ing this on shouldn't do anything but slow yum depsolving  down,
837              however  using  rpm  --nodeps  etc. can break the rpmdb and then
838              this will help.  Boolean (1, 0, True, False, yes,no) Defaults to
839              False
840
841
842              reset_nice  If  set  to true then yum will try to reset the nice
843              value to zero, before running an rpm  transaction.  Defaults  to
844              True.
845
846              exit_on_lock  Should  the yum client exit immediately when some‐
847              thing else has the lock.  Boolean (1, 0, True, False,  yes,  no)
848              Defaults to False
849
850
851              loadts_ignoremissing  Should the load-ts command ignore packages
852              that are missing.  This  includes  packages  in  the  TS  to  be
853              removed,  which  aren't  installed, and packages in the TS to be
854              added, which aren't available.  If this is set to true,  and  an
855              rpm  is missing then loadts_ignorenewrpm is automatically set to
856              true.  Boolean (1, 0, True, False, yes, no) Defaults to False
857
858
859              loadts_ignorerpm Should the load-ts  command  ignore  the  rpmdb
860              version  (yum  version nogroups) or abort if there is a mismatch
861              between the TS file and the current machine.  If this is set  to
862              true,  then  loadts_ignorenewrpm  is  automatically set to true.
863              Boolean (1, 0, True, False, yes, no) Defaults to False
864
865
866              loadts_ignorenewrpm Should the load-ts command ignore the future
867              rpmdb  version  or  abort  if there is a mismatch between the TS
868              file and what will happen on the current machine.  Note that  if
869              loadts_ignorerpm is True, this option does nothing.  Boolean (1,
870              0, True, False, yes, no) Defaults to False
871
872
873              fssnap_automatic_pre Should yum try to  automatically  create  a
874              snapshot  before  it  runs  a transaction.  Boolean (1, 0, True,
875              False, yes, no) Defaults to False
876
877
878              fssnap_automatic_post Should yum try to automatically  create  a
879              snapshot  after  it  runs  a  transaction.  Boolean (1, 0, True,
880              False, yes, no) Defaults to False
881
882
883              fssnap_automatic_keep How many old  snapshots  should  yum  keep
884              when trying to automatically create a new snapshot. Setting to 0
885              disables this feature. Default is '1'.
886
887
888              fssnap_automatic_percentage The size of new snaphosts, expressed
889              as  a percentage of the old origin device.  Any number between 1
890              and 100. Default is '100'.
891
892
893              fssnap_automatic_devices The origin LVM devices to use for snap‐
894              shots. Wildcards and negation are allowed, first match (positive
895              or   negative)   wins.    Default   is:    !*/swap    !*/lv_swap
896              glob:/etc/yum/fssnap.d/*.conf
897
898
899              fssnap_abort_on_errors When fssnap_automatic_pre or fssnap_auto‐
900              matic_post is enabled, it's possible  to  specify  which  fssnap
901              errors should make the transaction fail. The default is `any'.
902
903              `broken-setup'  -  Abort current transaction if snapshot support
904              is unavailable because lvm is missing or broken.
905
906              `snapshot-failure' - Abort current  transaction  if  creating  a
907              snapshot  fails  (e.g.  there is not enough free space to make a
908              snapshot).
909
910              `any' - Abort current transaction if any of the above occurs.
911
912              `none' - Never abort a transaction in case of errors.
913
914
915              depsolve_loop_limit Set the number of times any attempt to  dep‐
916              solve  before  we  just give up. This shouldn't be needed as yum
917              should always solve or fail, however it has been  observed  that
918              it  can  loop  forever  with very large system upgrades. Setting
919              this to `0' (or "<forever>") makes yum try forever.  Default  is
920              `100'.
921
922
923              usr_w_check  Either  `0'  or `1'. Set this to `0' to disable the
924              checking for writability on /usr in the installroot (when  going
925              into the depsolving stage). Default is `1' (perform the check).
926
927

[repository] OPTIONS

929       The repository section(s) take the following form:
930
931              Example: [repositoryid]
932              name=Some name for this repository
933              baseurl=url://path/to/repository/
934
935
936              repositoryid  Must  be  a  unique  name for each repository, one
937              word.
938
939
940              name A human readable string describing the repository.
941
942
943              baseurl Must be a URL to the directory  where  the  yum  reposi‐
944              tory's  `repodata' directory lives. Can be an http://, ftp:// or
945              file:// URL. You can specify multiple URLs in one baseurl state‐
946              ment. The best way to do this is like this:
947              [repositoryid]
948              name=Some name for this repository
949              baseurl=url://server1/path/to/repository/
950                      url://server2/path/to/repository/
951                      url://server3/path/to/repository/
952
953              If you list more than one baseurl= statement in a repository you
954              will find yum will ignore the  earlier  ones  and  probably  act
955              bizarrely. Don't do this, you've been warned.
956
957              You  can  use  HTTP basic auth by prepending "user:password@" to
958              the  server  name   in   the   baseurl   line.    For   example:
959              "baseurl=http://user:passwd@example.com/".
960
961
962              metalink  Specifies a URL to a metalink file for the repomd.xml,
963              a list of mirrors for the entire  repository  are  generated  by
964              converting the mirrors for the repomd.xml file to a baseurl. The
965              metalink file also contains the latest timestamp from  the  data
966              in  the  repomd.xml,  the  length of the repomd.xml and checksum
967              data. This data is checked  against  any  downloaded  repomd.xml
968              file  and  all  of  the  information from the metalink file must
969              match. This can be used instead of or with the  baseurl  option.
970              Substitution  variables,  described below, can be used with this
971              option. This option disables the mirrorlist option.  As  a  spe‐
972              cial  hack  is  the  mirrorlist URL contains the word "metalink"
973              then the value of mirrorlist is copied to metalink (if  metalink
974              is not set).
975
976
977              mirrorlist  Specifies  a  URL  to  a  file  containing a list of
978              baseurls. This can be  used  instead  of  or  with  the  baseurl
979              option.  Substitution  variables,  described  below, can be used
980              with this option.  As a special hack is the mirrorlist URL  con‐
981              tains the word "metalink" then the value of mirrorlist is copied
982              to metalink (if metalink is not set).
983
984
985
986              enabled Either `1' or `0'. This tells yum  whether  or  not  use
987              this repository.
988
989
990              keepcache Overrides the keepcache option from the [main] section
991              for this repository.
992
993
994              gpgcheck Either `1' or `0'. This tells yum  whether  or  not  it
995              should perform a GPG signature check on the packages gotten from
996              this repository.
997
998
999              repo_gpgcheck Either `1' or `0'. This tells yum whether  or  not
1000              it  should  perform  a  GPG signature check on the repodata from
1001              this repository.
1002
1003
1004              gpgkey A URL pointing to the ASCII-armored GPG key file for  the
1005              repository.  This  option  is  used if yum needs a public key to
1006              verify a package and the required key hasn't been imported  into
1007              the  RPM database. If this option is set, yum will automatically
1008              import the key from the specified  URL.  You  will  be  prompted
1009              before the key is installed unless the assumeyes option is set.
1010
1011              Multiple  URLs  may  be specified here in the same manner as the
1012              baseurl option (above). If a GPG key is required  to  install  a
1013              package  from  a repository, all keys specified for that reposi‐
1014              tory will be installed.
1015
1016
1017              gpgcakey A URL pointing to the ASCII-armored CA key file for the
1018              repository.  This is a normal gpg public key - but this key will
1019              be used to validate detached signatures of all other  keys.  The
1020              idea is you are asked to confirm import for this key. After that
1021              any other gpg key needed for package or repository verification,
1022              if  it  has  a detached signature which matches this key will be
1023              automatically imported without user confirmation.
1024
1025
1026              exclude Same as the [main] exclude  option  but  only  for  this
1027              repository.   Substitution  variables, described below, are hon‐
1028              ored here.
1029
1030              Can be disabled using --disableexcludes.
1031
1032
1033              includepkgs Inverse of exclude, yum will exclude any package  in
1034              the  repo.  that doesn't match this list. This works in conjunc‐
1035              tion  with  exclude  and  doesn't  override  it,   so   if   you
1036              exclude=*.i386 and includepkgs=python* then only packages start‐
1037              ing with python that do not have an i386 arch. will be  seen  by
1038              yum in this repo.
1039
1040              Substitution variables, described below, are honored here.
1041
1042              Can be disabled using --disableexcludes.
1043
1044
1045              enablegroups  Either  `0'  or  `1'.  Determines whether yum will
1046              allow the use of package groups for this repository. Default  is
1047              `1' (package groups are allowed).
1048
1049
1050              failovermethod Either `roundrobin' or `priority'.
1051
1052              `roundrobin'  randomly  selects a URL out of the list of URLs to
1053              start with and proceeds through each of them as it encounters  a
1054              failure contacting the host.
1055
1056              `priority'  starts  from  the  first  baseurl  listed  and reads
1057              through them sequentially.
1058
1059              failovermethod defaults to `roundrobin' if not specified.
1060
1061
1062              keepalive Either `1' or `0'.  This  tells  yum  whether  or  not
1063              HTTP/1.1  keepalive should be used with this repository. See the
1064              global option in the [main] section above for more information.
1065
1066
1067              timeout Overrides the timeout option from the [main] section for
1068              this repository.
1069
1070
1071              http_caching  Overrides  the http_caching option from the [main]
1072              section for this repository.
1073
1074
1075              retries Overrides the retries option from the [main] section for
1076              this repository.
1077
1078
1079              throttle  Overrides  the throttle option from the [main] section
1080              for this repository.
1081
1082
1083              bandwidth Overrides the bandwidth option from the [main] section
1084              for this repository.
1085
1086
1087              ip_resolve  Overrides the ip_resolve option from the [main] sec‐
1088              tion for this repository.
1089
1090
1091              deltarpm_percentage  Overrides  the  deltarpm_percentage  option
1092              from the [main] section for this repository.
1093
1094
1095              deltarpm_metadata_percentage    Overrides   the   deltarpm_meta‐
1096              data_percentage option from the [main] section for this  reposi‐
1097              tory.
1098
1099
1100              sslcacert Overrides the sslcacert option from the [main] section
1101              for this repository.
1102
1103
1104              sslverify Overrides the sslverify option from the [main] section
1105              for this repository.
1106
1107
1108              sslclientcert Overrides the sslclientcert option from the [main]
1109              section for this repository.
1110
1111
1112              sslclientkey Overrides the sslclientkey option from  the  [main]
1113              section for this repository.
1114
1115
1116              ssl_check_cert_permissions  Overrides the ssl_check_cert_permis‐
1117              sions option from the [main] section for this repository.
1118
1119
1120              metadata_expire Overrides the metadata_expire  option  from  the
1121              [main] section for this repository.
1122
1123
1124              metadata_expire_filter   Overrides   the  metadata_expire_filter
1125              option from the [main] section for this repository.
1126
1127
1128              mirrorlist_expire Overrides the  mirrorlist_expire  option  from
1129              the [main] section for this repository.
1130
1131
1132              proxy  URL  to  the  proxy  server  for  this repository. Set to
1133              '_none_' to disable the global proxy setting  for  this  reposi‐
1134              tory. If this is unset it inherits it from the global setting
1135
1136
1137              proxy_username  username  to use for proxy.  If this is unset it
1138              inherits it from the global setting
1139
1140
1141              proxy_password password for this proxy.  If  this  is  unset  it
1142              inherits it from the global setting
1143
1144
1145
1146              username  username  to use for basic authentication to a repo or
1147              really any url.  If this is unset it inherits it from the global
1148              setting
1149
1150
1151              password password to use with the username for basic authentica‐
1152              tion.  If this is unset it inherits it from the global setting
1153
1154
1155              cost relative cost of  accessing  this  repository.  Useful  for
1156              weighing  one  repo's  packages  as greater/less than any other.
1157              defaults to 1000
1158
1159
1160              skip_if_unavailable If set to True yum will continue running  if
1161              this  repository cannot be contacted for any reason. This should
1162              be set carefully as all repos are consulted for any  given  com‐
1163              mand. Defaults to False.
1164
1165
1166              async  If  set  to  True Yum will download packages and metadata
1167              from this repo in parallel, if possible.  Defaults to True.
1168
1169
1170              ui_repoid_vars Overrides  the  ui_repoid_vars  option  from  the
1171              [main] section for this repository.
1172
1173

URL INCLUDE SYNTAX

1175       The   inclusion  of  external  configuration  files  is  supported  for
1176       /etc/yum.conf and the .repo files in the /etc/yum.repos.d directory. To
1177       include a URL, use a line of the following format:
1178
1179       include=url://to/some/location
1180
1181       The  configuration  file  will  be  inserted  at  the  position  of the
1182       "include=" line.  Included files may contain further include lines. Yum
1183       will abort with an error if an inclusion loop is detected.
1184
1185

GLOB: FOR LIST OPTIONS

1187       Any  of  the  configurations  options  which are a list of items can be
1188       specfied using the glob syntax: glob:/etc/path/somewhere.d/*.conf. This
1189       will read in all files matching that glob and include all lines in each
1190       file (excluding comments and blank lines) as items in the list.
1191

VARIABLES

1193       There are a number of variables you can  use  to  ease  maintenance  of
1194       yum's  configuration files. They are available in the values of several
1195       options including name, baseurl and commands.
1196
1197              $releasever This will be replaced with the value of the  version
1198              of the package listed in distroverpkg. This defaults to the ver‐
1199              sion of `redhat-release' package.
1200
1201
1202              $arch This will be replaced with the architecture or your system
1203              as detected by yum.
1204
1205
1206              $basearch  This  will be replaced with your base architecture in
1207              yum. For example, if your $arch is i686 your $basearch  will  be
1208              i386.
1209
1210
1211              $uuid  This  will  be replaced with a unique but persistent uuid
1212              for this machine.  The value that is  first  generated  will  be
1213              stored  in  /var/lib/yum/uuid  and  reused  until  this  file is
1214              deleted.
1215
1216
1217              $YUM0-$YUM9 These will be replaced with the value of  the  shell
1218              environment  variable of the same name. If the shell environment
1219              variable does not exist then  the  configuration  file  variable
1220              will not be replaced.
1221
1222
1223       As of 3.2.28, any properly named file in /etc/yum/vars is turned into a
1224       variable named after the filename (or overrides any of the above  vari‐
1225       ables).   Filenames may contain only alphanumeric characters and under‐
1226       scores and be in lowercase.
1227
1228       Note that no warnings/errors are given if the files are unreadable,  so
1229       creating files that only root can read may be confusing for users.
1230
1231       Also  note that only the first line will be read and all new line char‐
1232       acters are removed, as a convenience. However,  no  other  checking  is
1233       performed  on the data. This means it is possible to have bad character
1234       data in any value.
1235
1236

FILES

1238       /etc/yum.conf
1239       /etc/yum.repos.d/
1240       /etc/yum/pluginconf.d/
1241       /etc/yum/protected.d
1242       /etc/yum/vars
1243
1244

SEE ALSO

1246       yum(8)
1247
1248
1249
1250
1251Seth Vidal                                                         yum.conf(5)
Impressum