Re: cvs permissions
On Mon, Jul 23, 2001 at 05:50:19PM +0200, Martin F. Krafft wrote:
| i/we operate a number of remote servers, and sometimes, configuration
| is impossible because of slow links; then, vi takes 10 seconds to
| start, and a keystroke is echoed in 5... unacceptable.
|
| so i would like to change configuration remotely, and currently, i
| rsync the /etc trees to a local directory, update, then rsync back.
| however, this requires a lot of discipline, and is not a viable method
| with multiple maintainers.
|
| 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. 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.
Vim 6 has support for remote editing of files, so if you want to try
that it may help too.
-D
Reply to: