diff options
author | sunpoet <sunpoet@FreeBSD.org> | 2011-09-20 14:43:16 +0800 |
---|---|---|
committer | sunpoet <sunpoet@FreeBSD.org> | 2011-09-20 14:43:16 +0800 |
commit | 8a268ebf6ae3cbfd2d6d23acf0dd373fa509a0f1 (patch) | |
tree | 06379381b17f4245b0bfa17979646dc2ab9e02c5 /sysutils | |
parent | 6c149e69e1e56b199300d099796021f57ea28c8f (diff) | |
download | freebsd-ports-gnome-8a268ebf6ae3cbfd2d6d23acf0dd373fa509a0f1.tar.gz freebsd-ports-gnome-8a268ebf6ae3cbfd2d6d23acf0dd373fa509a0f1.tar.zst freebsd-ports-gnome-8a268ebf6ae3cbfd2d6d23acf0dd373fa509a0f1.zip |
- Add agedu 9251
Unix provides the standard du utility, which scans your disk and tells you which
directories contain the largest amounts of data. That can help you narrow your
search to the things most worth deleting.
However, that only tells you what's big. What you really want to know is what's
too big. By itself, du won't let you distinguish between data that's big because
you're doing something that needs it to be big, and data that's big because you
unpacked it once and forgot about it.
Most Unix file systems, in their default mode, helpfully record when a file was
last accessed. Not just when it was written or modified, but when it was even
read. So if you generated a large amount of data years ago, forgot to clean it
up, and have never used it since, then it ought in principle to be possible to
use those last-access time stamps to tell the difference between that and a
large amount of data you're still using regularly.
agedu is a program which does this. It does basically the same sort of disk scan
as du, but it also records the last-access times of everything it scans. Then it
builds an index that lets it efficiently generate reports giving a summary of
the results for each subdirectory, and then it produces those reports on demand.
WWW: http://www.chiark.greenend.org.uk/~sgtatham/agedu/
Diffstat (limited to 'sysutils')
-rw-r--r-- | sysutils/Makefile | 1 | ||||
-rw-r--r-- | sysutils/agedu/Makefile | 23 | ||||
-rw-r--r-- | sysutils/agedu/distinfo | 2 | ||||
-rw-r--r-- | sysutils/agedu/pkg-descr | 22 |
4 files changed, 48 insertions, 0 deletions
diff --git a/sysutils/Makefile b/sysutils/Makefile index b2d5ddcc75f4..562d788c422b 100644 --- a/sysutils/Makefile +++ b/sysutils/Makefile @@ -16,6 +16,7 @@ SUBDIR += afbinit SUBDIR += afflib SUBDIR += afio + SUBDIR += agedu SUBDIR += agef SUBDIR += ah-tty SUBDIR += aimage diff --git a/sysutils/agedu/Makefile b/sysutils/agedu/Makefile new file mode 100644 index 000000000000..46837e446363 --- /dev/null +++ b/sysutils/agedu/Makefile @@ -0,0 +1,23 @@ +# New ports collection makefile for: agedu +# Date created: 2011-08-17 +# Whom: Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org> +# +# $FreeBSD$ +# + +PORTNAME= agedu +PORTVERSION= 9251 +CATEGORIES= sysutils +MASTER_SITES= http://www.chiark.greenend.org.uk/~sgtatham/${PORTNAME}/ \ + LOCAL/sunpoet +DISTNAME= ${PORTNAME}-r${PORTVERSION} + +MAINTAINER= sunpoet@FreeBSD.org +COMMENT= A Unix utility for tracking down wasted disk space + +GNU_CONFIGURE= yes + +MAN1= ${PORTNAME}.1 +PLIST_FILES= bin/${PORTNAME} + +.include <bsd.port.mk> diff --git a/sysutils/agedu/distinfo b/sysutils/agedu/distinfo new file mode 100644 index 000000000000..ac495564de6e --- /dev/null +++ b/sysutils/agedu/distinfo @@ -0,0 +1,2 @@ +SHA256 (agedu-r9251.tar.gz) = abeb9940bd6af6ad151a764f5e58876114bf556eefa161ff25604ce372de8a9b +SIZE (agedu-r9251.tar.gz) = 150270 diff --git a/sysutils/agedu/pkg-descr b/sysutils/agedu/pkg-descr new file mode 100644 index 000000000000..832844418e16 --- /dev/null +++ b/sysutils/agedu/pkg-descr @@ -0,0 +1,22 @@ +Unix provides the standard du utility, which scans your disk and tells you which +directories contain the largest amounts of data. That can help you narrow your +search to the things most worth deleting. + +However, that only tells you what's big. What you really want to know is what's +too big. By itself, du won't let you distinguish between data that's big because +you're doing something that needs it to be big, and data that's big because you +unpacked it once and forgot about it. + +Most Unix file systems, in their default mode, helpfully record when a file was +last accessed. Not just when it was written or modified, but when it was even +read. So if you generated a large amount of data years ago, forgot to clean it +up, and have never used it since, then it ought in principle to be possible to +use those last-access time stamps to tell the difference between that and a +large amount of data you're still using regularly. + +agedu is a program which does this. It does basically the same sort of disk scan +as du, but it also records the last-access times of everything it scans. Then it +builds an index that lets it efficiently generate reports giving a summary of +the results for each subdirectory, and then it produces those reports on demand. + +WWW: http://www.chiark.greenend.org.uk/~sgtatham/agedu/ |