On Thu, May 3, 2012 at 11:21 AM, John BORIS <[email protected]> wrote:
> The documents were created years ago and each year they have just been
> edited. My issues normally are with someone deleting a .\} or a \{\ or
> add an errant one of these. Things work fine until the perfect storm and
> bingo pages print on top of each other.
Wouldn't just putting the files under some form of version control
make fixing this much easier? Then you only have to look at what
changed using the tool's built in version difference command to narrow
down the problem. That would seem to be much less painful.
Note that you don't have to tie this in directly to the work flow- a
cronjob that copies the files to a secondary location periodically and
does automated checkins will suffice. I used to do this with my NIS
maps once a day (using the YYYYMMDD value as the version) and it
allowed me to track down when defects occurred.
Pretty much any versioning tool should work for this- RCS, CVS, git,
SCCS, SVN, commercial stuff.
_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
