On Mon, March 11, 2013 16:56, Craig White wrote:
>
> ----
> develop good, consistent habits? postfix or whatever config files you
> edit, backup the distribution's version of the config file first
> before you ever edit?
>
> cp main.cf main.cf-dist
>
Alternatively:
yum install postfix
yum install git
cd /etc/posfix
git init
git add ./
git commit -m"Postfix config file initial commit"
Now all the default config files are stored as hashed blobs in
/etc/postfix/.git and you can modify them in place. Once you are
satisfied with your latest set of changes do this (always issue git
commands from the repository root, in this case /etc/postfix):
git add ./ or git add <filename>
git commit -m"explanation of why the changes were made"
If you screw up and need to get back what was there originally do this:
git checkout <filename>
If you want to see what was different between this config and the
previous version do this:
git diff <filename>
You can compare any previous version of any tracked file with any
other version of the same file by specifying the commit ids.
git diff <commit1_sha>..<commit2_sha> -- <filename>
Git also provides a blow by blow history of all changes applied to a
file and what logon id made them.
git blame <commit1_sha>..<commit2_sha> -- <filename>
See http://git-scm.com/ for details on what git is and how to use it.
I use git for version control of system config files on all my uptime
sensitive servers. It makes getting back to a working config trivial
when things turn ugly following a change.
--
*** E-Mail is NOT a SECURE channel ***
James B. Byrne mailto:ByrneJB@xxxxxxxxxxxxx
Harte & Lyne Limited http://www.harte-lyne.ca
9 Brockley Drive vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada L8E 3C3
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
