From owner-freebsd-hackers Fri Dec 23 17:44:09 1994 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id RAA00337 for hackers-outgoing; Fri, 23 Dec 1994 17:44:09 -0800 Received: from physics.su.OZ.AU (dawes@physics.su.OZ.AU [129.78.129.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id BAA00331 for ; Sat, 24 Dec 1994 01:44:07 GMT Received: by physics.su.OZ.AU id AA16035 (5.67b/IDA-1.4.4 for freebsd-hackers@freebsd.org); Sat, 24 Dec 1994 12:43:27 +1100 From: David Dawes Message-Id: <199412240143.AA16035@physics.su.OZ.AU> Subject: Re: A lighter sup -v? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sat, 24 Dec 1994 12:43:26 +1100 (EST) Cc: mdavis@io.cts.com, freebsd-hackers@freebsd.org In-Reply-To: <20143.788220071@time.cdrom.com> from "Jordan K. Hubbard" at Dec 23, 94 02:01:11 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 897 Sender: hackers-owner@freebsd.org Precedence: bulk >> In using sup, I found that -v is the only way for it to report which >> files have been received. However, in addition to that, it wants to >> tell you all the files that have been "updated" as well. I assume >> that "updated" simply means that "Hey, we checked your file and the >> host's file and you don't need to update it." > >No, actually not. It means "I checked the file and the dates didn't >match, even if the contents did, so I'm stamping it again and >recording the fact in my sup logs." In most stable situations, you >shouldn't even see that most of the time! It means that the ctime of the file is more recent that the previous sup date, but the mtimes are the same. The actual file contents (and file size) are not checked. A common cause of these updates is if the sup server's collection has been restored from a backup, or moved to a different filesystem, etc. David