Assuming that you already have the rpms in one place, you can use yum-arch to build the header information. Assuming that if the rpm gets updated, you want to just push it out, if you have your yum.conf pointing to that repo, and have yum running out of cron, anytime there is an updated rpm, the clients will update as updates are available. So, * Run yum-arch for the location of your RPM's. * Install yum on your clients. * Set up the cron job to run at the desired frequency. * Set the yum.conf on the clients to point at your mounted repository. * As new RPM's get installed, re-run yum-arch. --Chris On Wed, 2004-02-25 at 14:39, Steve Swanekamp (Contractor) wrote: > I have Red Hat Enterprise WS3 installed on a cluster with only one > node connected to the internet. I want to use up2date on the node > with an external connection to download the rpm's necessary to keep my > systems up to date. I have the rpms stored on a disk that is cross > mounted to all of the nodes using NFS so that the compute nodes can > see all of the rpms. The problem I have is how to determine which > packages need to be updated on the compute nodes? Can I use yum to do > this? If so can someone tell me how to configure the main node to be > a server for the updates? Thanks... > ~ ,__o > ~ _-\ <, > (*)/ (*) ~ > ---------- > Dr. Stephen B. Swanekamp > Plasma Physics Division, Code 6771 > Naval Research Laboratory > Washington, DC 20375 > (202)-404-4361 (voice) > (202)-767-0436 (fax) > swane@xxxxxxxxxxxxxxxxxxx > > > > > > ______________________________________________________________________ > _______________________________________________ > Yum mailing list > Yum@xxxxxxxxxxxxxxxxxxxx > https://lists.dulug.duke.edu/mailman/listinfo/yum
