From owner-freebsd-hackers Sun May 17 15:09:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28614 for freebsd-hackers-outgoing; Sun, 17 May 1998 15:09:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28443 for ; Sun, 17 May 1998 15:09:15 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id PAA07702; Sun, 17 May 1998 15:08:54 -0700 (PDT) (envelope-from jdp) Message-Id: <199805172208.PAA07702@austin.polstra.com> To: Mike Smith cc: hackers@FreeBSD.ORG Subject: Re: nfs exported FreeBSD cvs repository, mounted on client, update problems In-reply-to: Your message of "Sat, 16 May 1998 20:18:55 PDT." <199805170318.UAA00865@antipodes.cdrom.com> Date: Sun, 17 May 1998 15:08:54 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > cvs -R > > > > > > 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. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message