Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.6.2.17 $; site uiucdcs.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!inuxc!pur-ee!uiucdcs!acheng
From: acheng@uiucdcs.UUCP
Newsgroups: net.unix-wizards
Subject: Re: how many blocks are how old?
Message-ID: <13700092@uiucdcs.UUCP>
Date: Tue, 29-Jan-85 10:27:00 EST
Article-I.D.: uiucdcs.13700092
Posted: Tue Jan 29 10:27:00 1985
Date-Received: Thu, 31-Jan-85 02:07:26 EST
References: <297@pertec.UUCP>
Lines: 20
Nf-ID: #R:pertec:-29700:uiucdcs:13700092:000:1048
Nf-From: uiucdcs!acheng    Jan 29 09:27:00 1985

>/* ---------- "how many blocks are how old?" ---------- */
>Does anyone have any sort of utility that can be used on a filesystem
>to give you a run-down on file/block aging?  I'd like to be able to
>run it on, say, /usr/spool, to let me know how many blocks are one day
>old, two days old, 30 days old, etc.
>
>Something that gave other statistics of interest might be useful as well.
>-- 

In 4.2, there is an undocumented (at least not in our version) option, -v,
in /etc/quot that will give you 3 more columns of blocks for files not
accessed 30+, 60+, 90+ days.  The "quot" lists them out by uid and it
makes life easy for system people to locate "disk hogs" and/or "idle hogs".
Of course, the user may turn around and touch all his files but we still
assume we are in a friendly, cooperative environment.
One of our gurus modified the "du" to give a similar but more general
feature of disk blocks not accessed by *directories*.  This one would be
helpful for users to locate his idle files.  We may post it if there is a big
demand for it.