On Thu, 4 Dec 2003, Harvey J. Stein wrote: > None the less, two issues have come up. One is that I have 2 > machines. With up2date, I was able to easily set it up so that I > didn't have to download things more than once. I did this by NFS > mounting /var/spool/up2date on the 2nd machine. I would update the > 1st machine with up2date configured to not delete the downloaded RPMs. > Then I'd update the 2nd machine, which would see the RPMs in the NFS > mounted /var/spool/up2date, so it wouldn't download them again. The > 2nd machine is configured to delete RPMs after installation. Thus, > the RPMs would be around for as long as necessary, and would get > cleaned up at the end (except for pkgs on the 1st machine that aren't > on the 2nd, which I'd periodically clean up manually). This scales to > N machines by only configuring 1 to delete rpms, and always updating > that machine last. > This seems like a recipe for trouble. If you want to only download updates once, I'd suggest just running a mirror script to monitor an updates directory somplace and running yum-arch on that, and adding it to your local yum.conf's You can still NFS mount the directory you're mirroring and use a file:// url for baseurl in yum.conf. > The other issue is speed of updates. up2date shows me that > rsync-2.5.7-0.9 is now available, but yum isn't pulling it down. My > (unchanged, stock) yum.conf shows: > > http://mirror.dulug.duke.edu/pub/yum-repository/redhat/updates/$releasever/ > > as my default update repository. Taking a look at > > http://mirror.dulug.duke.edu/pub/yum-repository/redhat/updates/9/x86/i386/ > > I see that rsync-2.5.7-0.9.i386.rpm just showed up ~2 hrs ago. But, > there's no header file for it in > > http://mirror.dulug.duke.edu/pub/yum-repository/redhat/updates/9/headers/ > > Judging from the file dates in the latter directory, it appears that > the headers are only regenerated once a day. Is this the case? Any > possibility of getting the headers updated as the RPMs arrive? Are > there any mirror repositories around that do that? > yum-arch is different from whatever mirroring process is used at individual sites. Duke seems to run yum one a day, as do I except we only remirror once a day to the changes are always reflected. Using my suggestion from above, this would never be an issue for you, as you could simply run yum-arch on the mirrored directory after every update. -n -- ------------------------------------------- nathan hruby <nhruby@xxxxxxx> uga enterprise information technology services production systems support metaphysically wrinkle-free -------------------------------------------
