I've got a network with a few score RPM-based machines, and need to standardize and sometimes en masse update some predictable *NIX configuration files:
(I control what settings I can at boot-time, and veil most network changes with sly A record changes, but sometimes I do need to reach into the machines and turn a knob.)
Now, I can revise existing and introduce new packages into these boxen' RPM repositories, and my thought is to standardize their configuration by introducing "configuration-only" RPMs
The idea of summarily replacing
/etc files owned by some other RPM gives me pause, however. Does anyone have practical guidance for this endeavour, particularly recommendations for doing this safely?