Re: One Hour Later Pup Fails

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Benjy Grogan wrote:
On 6/9/06, pribyl@xxxxxxxxxxx <pribyl@xxxxxxxxxxx> wrote:
Take a look here e.g.:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=189483

Interesting.  So it should actually keep a cache of anything it
downloads.
if keepcache=0 then
  nothing is kept (in simple terms)
else
  kept forever.
Maybe I didn't notice that the second try at updating was
a little quicker.
For me I prefer the older default where all headers/packages are kept, and you manually clean the cache with yum clean z.
So I set keepcache=1 in /etc/yum.conf
If you install a cpu/disk/network monitor like gkrellm, you can get a good idea about when yum is mainly cpu, disk or network intensive.

Another conf item to look for is metadata_expire=1800 (by default). see man yum.conf, /{search} ,metadata, n {ext}, to find out about it. To save yum regetting the repo metadata on a repeated run that occurs after the expire time, you can set the time a lot longer, eg a day; don't forget to set it back to the default afterwards.

DaveT.

--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list

[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]