From owner-freebsd-current  Thu Jan 28 01:07:33 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA11852
          for freebsd-current-outgoing; Thu, 28 Jan 1999 01:07:33 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11844
          for <freebsd-current@FreeBSD.ORG>; Thu, 28 Jan 1999 01:07:29 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA27849;
	Thu, 28 Jan 1999 20:06:58 +1100
Date: Thu, 28 Jan 1999 20:06:58 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901280906.UAA27849@godzilla.zeta.org.au>
To: axl@iafrica.com, pantzer@ludd.luth.se
Subject: Re: NIS with HPUX 10.20
Cc: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> Why _not_ use -C? What is the point in replacing a file with the same file? 
>> install -C will replace the file if the new file is diffrent.
>
>Aaaaaaaah, thank you. I misread the manpage description of -C and didn't
>notice "and the files are the same"...
>
>Cleared up, head back on straight. :-)

This is not so clear :-).  -C always does a complete replacement of the
file, as does -c, but the man page bogusly claims that the target file
is overwritten.  The complete replacement is necessary to snap any links
(another undocumented feature).

Someday -C should avoid touching the file if possible, so that it
doesn't clobber the file's ctime and backups based on ctimes don't do
unnecessary work.  This is possible if none of the attributes except
the file times would change, and fairly easy to implement if the file
doesn't have any links.

Bruce

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