From owner-freebsd-current Sat Aug 12 7:23:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail5.svr.pol.co.uk (mail5.svr.pol.co.uk [195.92.193.20]) by hub.freebsd.org (Postfix) with ESMTP id 77DAE37B6E6 for ; Sat, 12 Aug 2000 07:23:27 -0700 (PDT) (envelope-from markk@knigma.org) Received: from modem-237.sodium.dialup.pol.co.uk ([62.136.10.237] helo=lap.knigma.org) by mail5.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 13NcC5-0007kb-00 for freebsd-current@freebsd.org; Sat, 12 Aug 2000 15:23:26 +0100 Message-ID: Date: Sat, 12 Aug 2000 15:22:53 +0100 To: freebsd-current@freebsd.org From: Mark Knight Subject: Re: -current kernel causes CVSup SetAttrs flood (was: cvsup overzealous) References: <200008120221.TAA60376@vashon.polstra.com> In-Reply-To: <200008120221.TAA60376@vashon.polstra.com> MIME-Version: 1.0 X-Mailer: Turnpike Integrated Version 5.01 U Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200008120221.TAA60376@vashon.polstra.com>, John Polstra writes >[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 yes > - are logged in as the same user yes > - are using the same cvsup command line and supfile yes It was repeatable over several reboots, switching between the two kernels. I've just performed a new sup, and with a new kernel everything is fine again... I'll put it down to a bad snapshot for want of a better explanation. Thanks! -- Mark Knight PGP Public Key: finger mkn@knigma.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message