So... Would it work if you made /var/cache/yum a read-only NFS mount exported/updated by the "master"? In some cases rpms needed by the clients might not be present in the cache and they would try to download new ones and it would blow up. But then you could have the master download the proper rpms and start again. There might be a more elegant way to check whether the cache was complete (yum checkupdate piped into... ?) before trying to update. Or just have the master constantly updating and have all the rpms. At which point you might as well make it a local mirror? Dave > What I do is have a small bash script that rsync's the packages and headers in > the /var/cache/yum area from the one machine, where they are downloaded during > its own update, to the others. > > Then I run a normal yum update on the other machines in the LAN after the rsync, -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
