On Fri, Jul 27, 2001 at 02:14:07PM -0400, dman wrote: > On Mon, Jul 23, 2001 at 05:50:19PM +0200, Martin F. Krafft wrote: > | CVS is pretty much exactly what i am looking for. i would love to > | create a CVS repository each for every one of the remote machines. > | then everyone could checkout and commit, and a cron job on the actual > | remote machine could bring the local /etc up to date with the CVS > | repository every 4 hours or so. > > CVS is designed for concurrent development -- you don't "checkout" > files, you just modify and then merge your changes with someone else's > concurrent changes. Hmm ... so what's "cvs edit" for? :) > Perhaps you could use RCS (because with RCS you > checkout/lock files) on the remote system and rsync between the > checkout directory on the remote system and a temp directory on your > local system. This would prevent people from simultaneously making > changes to files. RCS works well when you have good access to the machine in question. Sounds like that's part of the problem in Martin's case. -- Nathan Norman - Staff Engineer | A good plan today is better Micromuse Ltd. | than a perfect plan tomorrow. mailto:nnorman@micromuse.com | -- Patton
Attachment:
pgpCDhz0G6grU.pgp
Description: PGP signature