Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 17 May 1998 19:10:01 -0700
From:      Mike Smith <mike@smith.net.au>
To:        John Polstra <jdp@polstra.com>
Cc:        Mike Smith <mike@smith.net.au>, hackers@FreeBSD.ORG
Subject:   Re: nfs exported FreeBSD cvs repository, mounted on client, update problems 
Message-ID:  <199805180210.TAA05964@antipodes.cdrom.com>
In-Reply-To: Your message of "Sun, 17 May 1998 15:08:54 PDT." <199805172208.PAA07702@austin.polstra.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
> > > > cvs -R <blah>
> > > >
> > > > Naturally, avoid doing this while CVSup is running.
> > >
> > > CVSup neither creates locks nor pays any attention to them.
> >
> > Exactly.
> 
> I figured you knew all about that.  But I wanted to make sure folks
> realized that the "-R" flag to CVS doesn't make any difference as far
> as CVSup is concerned.  In general, it's best to avoid CVS operations
> while CVSup is updating the repository.  CVSup is careful to update
> each individual file atomically.  But that's not always enough, e.g.,
> if you're trying to do a commit on the client side at the same time.

That was what I meant to infer, but you're right, more verbiage would 
have been better.

How difficult would it be for CVSup to lock the entire repository while 
it's running?  Is it worth the effort?

-- 
\\  Sometimes you're ahead,       \\  Mike Smith
\\  sometimes you're behind.      \\  mike@smith.net.au
\\  The race is long, and in the  \\  msmith@freebsd.org
\\  end it's only with yourself.  \\  msmith@cdrom.com



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805180210.TAA05964>