[lug] Seeking recommendations for revision control

[Harris, James]

That actually sounds like the perfect solution.  There's only three of us
who are doing the edits, but we've had to do hundreds of edits a day
(company merger) and we're getting tired of file locking via yelling through
the walls of our cubes.  :-)

Is that wrapper script something you'd be willing to share?  The concept is
simple enough that I could probably kick something out, but I'm always open
to not reinventing the wheel.

I'd appreciate it enormously.

-----Original Message-----
From: Nate Duehr [mailto:nate at natetech.com]
Sent: Monday, April 30, 2001 21:24
To: lug at lug.boulder.co.us
Subject: Re: [lug] Seeking recommendations for revision control

Never seen one pre-written for locking zone files, etc.  We wrote our
own Perl wrapper scripts around editing stuff and we touch a lock file
when someone else is doing something (like editing /etc/named.conf) that
would break things if two people are doing it... called the script
"vinamed" for example... checks for lockfile, writes lockfile, starts vi
on the appropriate file, when you save and exit cleans up the lockfile.
Probably has race conditions, but seems to work with a limited number of
people.

-- 
Nate Duehr <nate at natetech.com>

GPG Key fingerprint = DCAF 2B9D CC9B 96FA 7A6D AAF4 2D61 77C5 7ECE C1D2
Public Key available upon request, or at wwwkeys.pgp.net and others.
_______________________________________________
Web Page:  http://lug.boulder.co.us
Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug