<sorry if you see this twice. possible user error.> > 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). I was going to do this, but the problem is that the scripts are data driven. If just the data for a single host out of 1000 changes, then I'd have to rev the version on an otherwise unchanged RPM, and each host would download this RPM. The data that's driving these scripts would not be in the RPM, since it's private and I don't want each host knowing about the other's configuration. I think I'll go with a solution like Aaron's, where each host grabs its config files from a central server, which generates the config files as needed. Eric.