yum.conf after the recent updates

[Ed Greshko]

Ed Greshko wrote:
> Tim wrote:
>   
>> Hi,
>>
>> Below is the yum.conf I found after the recent key updates.  The
>> descriptive comments are sadly lacking a vital bit of information (what
>> particular value/attribute "this" is).
>>
>> If we make *what* bigger?  It can't mean the installonly_limit.  I'm
>> guessing it refers to metadata_expire, but that's a guess, and it's not
>> used in the provided file.
>>
>> Anyone have any comments before I bugzilla it?
>>
>> [main]
>> cachedir=/var/cache/yum
>> keepcache=0
>> debuglevel=2
>> logfile=/var/log/yum.log
>> exactarch=1
>> obsoletes=1
>> gpgcheck=1
>> plugins=1
>> installonly_limit=3
>>
>> #  This is the default, if you make this bigger yum won't see if the metadata
>> # is newer on the remote and so you'll "gain" the bandwidth of not having to
>> # download the new metadata and "pay" for it by yum not having correct
>> # information.
>> #  It is esp. important, to have correct metadata, for distributions like
>> # Fedora which don't keep old packages around. If you don't like this checking
>> # interupting your command line usage, it's much better to have something
>> # manually check the metadata once an hour (yum-updatesd will do this).
>> # metadata_expire=90m
>>
>> # PUT YOUR REPOS HERE OR IN separate files named file.repo
>> # in /etc/yum.repos.d
>>
>>   
>>     
> An older yum.conf has as its last line....
>
> metadata_expire=1800
>
> This seems to match the comment
>
>   
Oh, besides....the last line in the "comment" is "commented out" and
that is the line I bet is being talked about...

-- 
Many people resent being treated like the person they really are.