From: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: "(ding)" <ding@gnus.org>
Subject: Re: nnml compression: state of the art?
Date: 29 Mar 2001 09:12:24 -0800 [thread overview]
Message-ID: <m1d7b0qz2f.fsf@halfdome.holdit.com> (raw)
In-Reply-To: <01Mar29.105117est.115281@gateway.intersys.com>
>>>>> "Rat" == Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
Rat> The most efficient thing would be to occasionally run a find command like
Rat> this:
Rat> find $HOME/Mail \
Rat> -name ".overview" -prune -o \
Rat> -name "*.gz" -prune -o \
Rat> -type f -size +4k -print | xargs gzip -1
Rat> substituting your filesystem's block size in the +4k segment. This will
Rat> skip compressing .overview files and files that are already compressed.
Rat> Anything more than minimal compression will not gain you much.
#!/usr/bin/perl
use strict;
$|++;
use File::Find;
find sub {
return unless /^(\d+)$/ and -f and -s _ > 65535 and -A _ > 0.1;
system '/bin/gzip', "-9v", $File::Find::name;
}, "/home/merlyn/Mail";
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2001-03-29 17:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-29 8:22 Bill White
2001-03-29 13:04 ` Karl Kleinpaste
2001-03-29 15:47 ` Stainless Steel Rat
2001-03-29 17:12 ` Randal L. Schwartz [this message]
2001-03-29 19:15 ` Stainless Steel Rat
2001-03-29 19:21 ` Paul Jarc
2001-03-29 22:01 ` Stainless Steel Rat
2001-03-30 13:01 ` Randal L. Schwartz
2001-03-29 19:46 ` Michael Livshin
2001-03-29 19:47 ` Alan Shutko
2001-03-29 22:26 ` Stainless Steel Rat
2001-03-30 10:44 ` Bill White
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=m1d7b0qz2f.fsf@halfdome.holdit.com \
--to=merlyn@stonehenge.com \
--cc=ding@gnus.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).