Xref: utzoo comp.unix.wizards:8207 comp.os.misc:422 comp.os.vms:5901
Path: utzoo!utgpu!water!watmath!clyde!bellcore!faline!thumper!ulysses!terminus!rolls!mtuxo!mtgzz!avr
From: avr@mtgzz.UUCP (XMRP50000[jcm]-a.v.reed)
Newsgroups: comp.unix.wizards,comp.os.misc,comp.os.vms
Subject: Re: Uses for access time
Summary: removing frequently used executables
Message-ID: <4054@mtgzz.UUCP>
Date: 29 Apr 88 18:05:23 GMT
References: <3672@lynx.UUCP> <8726@oberon.USC.EDU> <4876@cup.portal.com>
Distribution: na
Organization: AT&T, Middletown NJ
Lines: 19

In article <4876@cup.portal.com>, DGD@cup.portal.com writes:
> The most useful aspect of "access time" is for a system administrator.
> I was once so unfortunate as to be on a large system where the users
> woould squirrel away copies of large programs (.c's .o's .a's ,etc.)
> and very rarely use them.  When the disk crunch hit, as it had to, a simple
> "find" of files not accessed for 6 months showed about 200 megabytes
> of files which were candidates for purging/backup-to-tape/whatever.
>     "If you haven't used it for 6 months, you don't need it on-line!"

Unfortunately, "access time" is NOT updated when an executable is
executed. I was once on a system whose very clever administrator wrote a
demon to archive any file not "accessed" in the last month. He soon
archived an executable I was exec'ing every day from my .profile.
The only way to restore an archived file was from one's own shell - and
since my .profile was bombing, I could not get one. I finally managed to
move the .profile after su'ing from a friend's login. I then retrieved
the missing executables, and put in code to touch all my executables
periodically. Ugh.
				Adam Reed (mtgzz!avr)