From owner-freebsd-current Fri Aug 11 19:21:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 496E937BD15 for ; Fri, 11 Aug 2000 19:21:32 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id TAA27025; Fri, 11 Aug 2000 19:21:27 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id TAA60376; Fri, 11 Aug 2000 19:21:26 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Fri, 11 Aug 2000 19:21:26 -0700 (PDT) Message-Id: <200008120221.TAA60376@vashon.polstra.com> To: current@freebsd.org Cc: markk@knigma.org Subject: Re: -current kernel causes CVSup SetAttrs flood (was: cvsup overzealous) In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [I changed the subject to something more represenative.] In article , Mark Knight wrote: > With world and kernel of 10th August, 01:00 GMT cvsup is reporting > 'SetAttrs' adjustments for every file it encounters on repeated runs > against a server that has not been updated. > > Running under an old kernel, cvsup is not performing any updates. Stranger things have happened, but still I am skeptical of this. Please make sure that the kernel is really the only difference. Especially check that on each run you: - have the same umask - are logged in as the same user - are using the same cvsup command line and supfile Thanks, John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message