[Yum] Multiple machines & timeliness of updates.

Harvey J. Stein hjstein at covad.net
Sun Dec 7 18:47:39 UTC 2003

"nathan r. hruby" <nhruby at uga.edu> writes:

> On Thu, 4 Dec 2003, Harvey J. Stein wrote:
> > 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.
> > 
> This seems like a recipe for trouble.

This works fine with up2date because it doesn't store machine specific
stuff in /var/spool/up2date.  I understand this won't work with yum
because yum does put machine specific stuff in the same dir that it
downloads the RPMs to.

> 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.

That's an idea.  The only thing is that this will download more than I
need, mirroring everything in the update directory instead of just
pulling down updates for packages I have installed.  I guess I could
only mirror the things I need, but that'd effectively be doing yum
check-update | xargs wget ; yum-arch ; yum update, in which case, why
not just tweak yum a little so that it stores downloaded RPMs in a way
that's compatible with yum-arch, or at least so that the cache can be

> > 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.
> 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.

Yes.  Does anyone know of any public yum servers which run yum-arch
immediately after the mirror process runs?


Harvey J. Stein
hjstein at covad.net

More information about the Yum mailing list