comment on

I'm a sysadmin and I use versioning for two things: development and active configs. I use subversion & CVS for stuff I'm developing (slowly migrating to svn). I use bazaar for config files.

I have scripts that run every X minutes to check in any config changes into bazaar. This way, if someone else makes an edit or if I forget to do a check-in, I have a history I can play back. If I discover that some obscure web page stopped working 2 months ago (not unlikely, some people never check their own pages), and I need to figure out what I changed, my bazaar diffs are great. I almost never actually roll back, but it's a fantastic diagnostic resource. If someone says I broke the web server and I think they broke their own web code, I can show exactly what edits I've made in the timeframe in question. It's awesome.

In reply to Re: My preferred version control system is... by pileofrogs
in thread My preferred version control system is... by Arunbear

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks