From: Jason Molenda <jason-swarelist@molenda.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Jim Kingdon <kingdon@redhat.com>, DJ Delorie <dj@delorie.com>,
overseers@sourceware.cygnus.com
Subject: Re: ftp mirrors
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <20000610010132.A20997@shell17.ba.best.com> (raw)
In-Reply-To: <3941CC03.B74B3373@cygnus.com>
On Sat, Jun 10, 2000 at 03:02:59PM +1000, Andrew Cagney wrote:
> And (shameless plug) cvsup :-)
For Buddha's sake Cagney, you'd read your mail with cvsup if you
could figure out how. :-)
> With rsync, I've wondered about creating a hidden shaddow of the FTP
> area that didn't contain gz/bz files.
We don't have the disk space for that. (try a df on sourceware and
imagine what the 3GB of ftp would expand to when uncompressed)
More importantly, rsync has support for this problem already.
dont compress
The "dont compress" option allows you to select
filenames based on wildcard patterns that should
not be compressed during transfer. Compression is
expensive in terms of CPU usage so it is usually
good to not try to compress files that won't com-
press well, such as already compressed files.
The "dont compress" option takes a space separated
list of case-insensitive wildcard patterns. Any
source filename matching one of the patterns will
not be compressed during transfer.
The default setting is
*.gz *.tgz *.zip *.z *.rpm *.deb
Looks like setting 'dont compress' to include .bz2 would be enough.
J
WARNING: multiple messages have this Message-ID
From: Jason Molenda <jason-swarelist@molenda.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Jim Kingdon <kingdon@redhat.com>, DJ Delorie <dj@delorie.com>,
overseers@sourceware.cygnus.com
Subject: Re: ftp mirrors
Date: Sat, 10 Jun 2000 01:02:00 -0000 [thread overview]
Message-ID: <20000610010132.A20997@shell17.ba.best.com> (raw)
Message-ID: <20000610010200.DxfG-r8K9E40NEjW3Ygv6OalV329t5m_FXiLEy3WD2k@z> (raw)
In-Reply-To: <3941CC03.B74B3373@cygnus.com>
On Sat, Jun 10, 2000 at 03:02:59PM +1000, Andrew Cagney wrote:
> And (shameless plug) cvsup :-)
For Buddha's sake Cagney, you'd read your mail with cvsup if you
could figure out how. :-)
> With rsync, I've wondered about creating a hidden shaddow of the FTP
> area that didn't contain gz/bz files.
We don't have the disk space for that. (try a df on sourceware and
imagine what the 3GB of ftp would expand to when uncompressed)
More importantly, rsync has support for this problem already.
dont compress
The "dont compress" option allows you to select
filenames based on wildcard patterns that should
not be compressed during transfer. Compression is
expensive in terms of CPU usage so it is usually
good to not try to compress files that won't com-
press well, such as already compressed files.
The "dont compress" option takes a space separated
list of case-insensitive wildcard patterns. Any
source filename matching one of the patterns will
not be compressed during transfer.
The default setting is
*.gz *.tgz *.zip *.z *.rpm *.deb
Looks like setting 'dont compress' to include .bz2 would be enough.
J
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200006091545.LAA00938.cygnus.project.sourcemaster@envy.delorie.com>
2000-12-30 6:08 ` Jim Kingdon
2000-06-09 14:53 ` Jim Kingdon
2000-12-30 6:08 ` Andrew Cagney
2000-06-09 22:05 ` Andrew Cagney
2000-12-30 6:08 ` Jason Molenda [this message]
2000-06-10 1:02 ` Jason Molenda
2000-12-30 6:08 ` Andrew Cagney
2000-06-10 4:19 ` Andrew Cagney
2000-12-30 6:08 ` Andrew Cagney
2000-06-10 18:03 ` Andrew Cagney
2000-12-30 6:08 ` Jason Molenda
2000-06-10 23:55 ` Jason Molenda
2000-12-30 6:08 ` Jim Kingdon
2000-06-11 8:24 ` Jim Kingdon
2000-12-30 6:08 ` Jason Molenda
2000-06-11 15:08 ` Jason Molenda
2000-12-30 6:08 ` Jason Molenda
2000-06-10 9:39 ` Jason Molenda
2000-12-30 6:08 ` Jason Molenda
2000-06-10 1:08 ` Jason Molenda
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=20000610010132.A20997@shell17.ba.best.com \
--to=jason-swarelist@molenda.com \
--cc=ac131313@cygnus.com \
--cc=dj@delorie.com \
--cc=kingdon@redhat.com \
--cc=overseers@sourceware.cygnus.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).