From: Haines Brown <brownh@hartford-hwp.com>
To: mdresser_l@windsormachine.com
Cc: revobild@revobild.net, linux-newbie@vger.kernel.org
Subject: Re: how to assess occupied space
Date: Sun, 15 Sep 2002 08:12:22 -0400 [thread overview]
Message-ID: <200209151212.g8FCCMF10511@hartford-hwp.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0209150039410.15231-100000@router.windsormachine.com> (message from Mike Dresser on Sun, 15 Sep 2002 00:40:38 -0400 (EDT))
Mike,
While du will provide that, you might want to control its output. I
put together a little command to pin down an enormous file, the name
and location of which I did not know. I've not used it enough to know
how reliable it is:
du -a <path and target directory> | sort -nr | head
This includes directories to help me locate the bloated file. The
output is sorted by size in reverse order, and that output is limited
to the ten biggest files.
Haines Brown
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2002-09-15 12:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-15 0:00 how to assess occupied space Revobild / Heimo Claasen
2002-09-15 4:40 ` Mike Dresser
2002-09-15 12:12 ` Haines Brown [this message]
2002-09-15 5:13 ` Ray Olszewski
-- strict thread matches above, loose matches on Subject: below --
2002-09-15 0:00 Heimo Claasen
2002-09-15 18:51 ` Mike Dresser
2002-09-15 19:05 ` Ray Olszewski
[not found] ` <Pine.LNX.4.33.0209151447040.23713-100000@router.windsormac hine.com>
2002-09-15 19:07 ` Ray Olszewski
2002-09-15 19:16 ` Mike Dresser
[not found] ` <Pine.LNX.4.33.0209151515110.2321-100000@router.windsormach ine.com>
2002-09-15 19:21 ` Ray Olszewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200209151212.g8FCCMF10511@hartford-hwp.com \
--to=brownh@hartford-hwp.com \
--cc=linux-newbie@vger.kernel.org \
--cc=mdresser_l@windsormachine.com \
--cc=revobild@revobild.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.