Xref: utzoo comp.unix.wizards:8048 comp.os.misc:407 comp.os.vms:5812
Path: utzoo!mnetor!uunet!vsi!friedl
From: friedl@vsi.UUCP (Stephen J. Friedl)
Newsgroups: comp.unix.wizards,comp.os.misc,comp.os.vms
Subject: Re: Uses for access time
Message-ID: <609@vsi.UUCP>
Date: 26 Apr 88 06:23:30 GMT
References: <3672@lynx.UUCP>
Distribution: na
Organization: V-Systems, Inc. -- Santa Ana, CA
Lines: 18
Summary: question on readonly filesystems

In article <3672@lynx.UUCP>, m5@lynx.UUCP (Mike McNally ) writes:
> I am trying to convince some of my ``colleagues'' here that keeping track
> of last-access times of files is a useful pursuit for an operating system.
> [...]
> Are these reasons enough to justify the overhead (I think so)?  Are there
> other reasons that I am overlooking?

Starting on a related topic:

I believe the access time of a UNIX file must be updated after
each read (not just at the open).  Since mounting a filesystem
readonly turns this update mechanism off because the inode is not
writable, I would assume that this would speed up a filesystem
slightly: does anybody have any experience on this?

-- 
Steve Friedl           V-Systems, Inc.        Spaf for president!
friedl@vsi.com   {backbones}!vsi.com!friedl    attmail!vsi!friedl