If you are changing the scripts, (which are contained in an rpm) it would seem the version of the rpm would change. So drop it in the repository and yum will grab it. This is the approach we are taking at Bank One for 'global' configs (like sudo, or security scripts). On Sat, 16 Aug 2003, seth vidal wrote: > > Since I'm sure it'll turn out to be more than just this one file > > (actually, its 2-3 already), I ended up writing a service that runs > > periodically on all these machines that makes secure (https) requests > > back to a central server (you can use a cacert to verify you are talking > > to your server) for a list of updated configuration files, then > > downloads and installs them. The server generates a custom XML file for > > each node with information about the updates for that particular node, > > including where to download the file, what permissions/ownership it > > should have, and what commands to run pre/post install. I have one RPM > > that I can install on all these machines to keep their config files up > > to date. > > I'd like to hear more about this too. > > -sv > > > _______________________________________________ > Yum mailing list > Yum@xxxxxxxxxxxxxxxxxxxx > https://lists.dulug.duke.edu/mailman/listinfo/yum > ------------------------------------------------------------------------ Jim Wildman, CISSP, RHCE jim@xxxxxxxxxxxxx http://www.rossberry.com
