Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!bellcore!ulysses!ucbvax!maynard.UUCP!campbell
From: campbell@maynard.UUCP
Newsgroups: mod.computers.vax
Subject: Re: aging files
Message-ID: <8606010118.AA18249@ucbvax.Berkeley.EDU>
Date: Sat, 31-May-86 14:57:29 EDT
Article-I.D.: ucbvax.8606010118.AA18249
Posted: Sat May 31 14:57:29 1986
Date-Received: Sun, 1-Jun-86 05:35:40 EDT
References: <8605310506.AA05550@ucbvax.Berkeley.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: maynard!campbell (Larry Campbell)
Organization: The Boston Software Works, Inc.
Lines: 23
Approved: info-vax@sri-kl.arpa

In article <8605310506.AA05550@ucbvax.Berkeley.EDU> JOANNE@MCMASTER.BITNET writes:
>The problem is aging files on our disks.  We have files that are a couple
>of years old but we don't know if they are still being used or not.
>VMS does not mark the file as accessed whenever it is read therefore
>we don't know whether to delete it or not.  We are trying to clean up
>the disks as best as we can but we seem to have a lot of these files
>around.  We could always find the owners and ask them but it would be
>time consuming.
>
>Joanne Templeton
>McMaster University,
>Hamilton, Canada

Just protect the files (S,O,G,W) (no access by anyone).  If anyone screams,
you just unprotect the file and they're happy.  After a month or so, you can
delete the files no one's screamed about yet.  If you like to fiddle with
ACLs and security alarms (I don't) you could even do it so they wouldn't
have to scream.  Just put a security alarm on the files in question.  Collect
the alarms and after a month, any file that hasn't been touched is fair game.
--
Larry Campbell                             The Boston Software Works, Inc.
ARPA: campbell%maynard.uucp@harvard.ARPA   120 Fulton Street, Boston MA 02109
UUCP: {alliant,wjh12}!maynard!campbell     (617) 367-6846