[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RCS & Config files
-----BEGIN PGP SIGNED MESSAGE-----
We'll I'm making a decision: critical system config files should be
managed via RCS. Too many people making too many changes means things
will get broken and we need a way to quickly determine what changed and
who did it so we can ask them why.
Hence, if you come to a config file, before you go editing away, please:
1) Add the following comments to the head of the file:
- --- CUT HERE ---
# NOTE:
# This config file is managed via RCS! The appropriate method to edit
# this file is to:
# co -l <filename> # checks out the file for editing
# edit the file
# ci -I -u <filename> # checks the file back in, and leaves a RO version
# $Id: $
# $Log: $
- --- END CUT ---
2) Create a ./RCS directory in the local path of the file
3) Run `ci -i -u <filename>` to initalize the file
If you follow the simple directions in the note above we should have a
nice way of keeping track of things. Also, if the file needs to be edited
by root, *please* `su R<username>` *not* `su -` so that RCS can properly
keep track of who you are.
Also don't forget to add descriptive notes regarding what you did when you
check in. Already I have RCS'ed:
/etc/{hosts|hosts.allow|hosts.deny|ssh_config|sshd_config|fstab|sudoers|
raidtab|resolv.conf}
httpd.conf
linuxkb.org master zone file and named.conf
- --
Aaron Turner | Either which way, one half dozen or another.
aturner@pobox.com | Check out the Red Hat Linux User's FAQ Online!
www.pobox.com/~aturner | http://www.pobox.com/~aturner/RedHat-FAQ/
All emails from this account are PGP signed. Lack of a signature is "bad".
PGP Key fingerprint = FB E1 CE ED 57 E4 AB 80 59 6E 60 BF 45 1B 20 E8
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBNqA8hzM3jpXy1kJtAQF+7wP+Mrtpp9ikNHkbnMerPu35XczP7+IFwxJv
vwnS/Tgkmy4mko1ZRFrOQfedUzB1rzqT6RsO6S8Ymz+PHZ0RMOic0UDx0uOA54WZ
3RiZ1E26VLfaldUSGOpb85TzMdF9c+lAoy5djWvuuxiZ5ZWjYh81ZT5n7Hmyub5h
IDepJf9R8uY=
=FaYO
-----END PGP SIGNATURE-----