From owner-freebsd-hackers Fri May 26 6:14:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 1F0C637B8A2 for ; Fri, 26 May 2000 06:14:37 -0700 (PDT) (envelope-from babolo@links.ru) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id RAA14587; Fri, 26 May 2000 17:14:20 +0400 (MSD) Message-Id: <200005261314.RAA14587@aaz.links.ru> Subject: Re: file creation times ? In-Reply-To: <00May26.071523est.115206@border.alcanet.com.au> from "Peter Jeremy" at "May 26, 0 07:15:22 am" To: peter.jeremy@ALCATEL.COM.AU (Peter Jeremy) Date: Fri, 26 May 2000 17:14:20 +0400 (MSD) Cc: brian@Awfulhak.org, hackers@FreeBSD.ORG From: "Aleksandr A.Babaylov" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy writes: > On 2000-May-25 19:03:56 +1000, Brian Somers wrote: > >Of course access timestamps are usually useless anyway as most (?!!) > >people will back up their system from time to time.... OOPS ! I > >never realised before now - dump *doesn't* update the access time. > > This is because dump bypasses the filesystem (it reads the underlying > device). Therefore the filesystem doesn't see the access. > > Other backup tools (tar, pax, cpio etc) access the files through the > FS amd therefore alter the access time. Some have the ability to > reset the access time afterwards - but that updates the change time, > which is probably worse. This is probably good justification for a > O_NOTACCESS (ie, this isn't a real access) flag on open(2) to request > that the access time isn't updated. I check it in FreeBSD 4.0-R open do not change atime. > In general, access time is probably the least important of the > timestamps. This is reflected in the treatment of access time > updates - unlike all other inode updates, they are not written > synchronously (non-softupdates) and don't affect soft-updates > write-ordering (so atime updates can be lost). > > As I see it, the major use of access times would be for a true > hierarchical storage manager (which transparently migrated un- > referenced files to a tape-library or similar). It's also good > for things like deleting `old' files in /tmp. See ports/18813: new port: misc/deleted this daemon uses access times [skip]......... -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message