On Sun, 2007-10-07 at 13:16 +0930, Tim wrote: > Tim: > >> I've just remembered something: There's a yum.conf option for > >> keeping the cached files. Perhaps your caching option is off, and > >> it doesn't handle broken downloads very well. > > Ric Moore: > > more yum.conf > > [main] > > cachedir=/var/cache/yum > > keepcache=1 > > debuglevel=2 > > logfile=/var/log/yum.log > > exactarch=1 > > obsoletes=1 > > gpgcheck=1 > > plugins=1 > > metadata_expire=1800 > > > > I got it set correct with the "1" ? > > That's correct. > > The metadata_expire is the number of seconds it'll remember the > filelists for (what's available, updated, etc.). If you were issuing > yum commands one after another, and taking a while between each issue, > and it had already downloaded the list successfully, this is the amount > of time that it'll avoid getting the list again. You could increase it, > but it'd only have an effect if you've managed to get the list. Huh, in the old BBS days, when we ran all of the logs, shakedowns and FIDO NET updates at 3AM, that held us for the next 24 hours via a satellite dnlink. Are the mirrors file updated daily at a given specific time? Or, just whenever it happens to happen and propagates around in like fashion? I'm just asking here to know. If the former, why bother to expire if the file crc matches and has the same period of time and the date (24 hours worth)? If not, then expire. Just trying to get my head around it. It's how I learn stuff. Ric -- ================================================ My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome." R.I.P. Dad. Linux user# 44256 Sign up at: http://counter.li.org/ http://www.sourceforge.net/projects/oar http://www.wayward4now.net <---down4now too ================================================
