Originally Posted by gdizzle
I was wondering if any admins have implemented a CVS on there Linux Servers for change control. E.g: if admins were to alter config files, which caused sporadic changes you could go back to the prior config file.
I am old school and always take a copy of a config file before editing however I would like to see if/how other organisations have anything like this in place as it seems like a bit of overhead when proper security and administration would make better sense.
I think CVS for config files seems like overkill. For every program you added, you'd have to include the configs into CVS, and woe be unto you if the software gets updated, and the config file location/name changes.
I make sure my backups are good, and keep three versions of all my files, regardless of what they are. I can always roll back three versions, plus the backup copy I make manually before making changes.