Save yourself with RCS revisions
Inevitably, you will break things so horribly that you have no hope of getting them back again. Suppose you've just done a complicated edit to your httpd.conf , and you get the error message that strikes fear (and occasionally heartburn) in the heart of admins everywhere:
root@catlin:/usr/local/apache/conf# ../bin/apachectl restart apachectl restart: httpd not running, trying to start apachectl restart: httpd could not be started
Oh, dear. What have you done? With the web server down, people aren't even getting your friendly 404 page, they're seeing Connection Refused errors. You could dig into httpd.conf desperately with vi to figure out exactly what you (or perhaps the admin before you) did to deserve this.
But if you're using RCS, things aren't so bleak. To see what has changed between your last checkout and this one, use rcsdiff :
root@catlin:/usr/local/apache/conf# rcsdiff httpd.conf =================================================================== RCS file: RCS/httpd.conf,v retrieving revision 1.1 diff -r1.1 httpd.conf 458c458 < ErrorLog /usr/local/apache/logs/error_log --- > ErrorLog :wq/usr/local/apache/logs/error_log
There we are. Evidently, a
:wq accidentally got
inserted at line 458. Ah, must have missed that ESC key. Make your
fix, start Apache, and check it back in.
But what if the changes were more extensive than that? Suppose you make a big change to a configuration file on Tuesday ...