public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jason Molenda <jason-swarelist@molenda.com>
To: Chris Faylor <cgf@cygnus.com>
Cc: Jim Kingdon <kingdon@panix.com>,
	shebs@shebs.cnchost.com, overseers@sourceware.cygnus.com,
	DJ Delorie <dj@cygnus.com>
Subject: Re: [Fwd: ftp probs]
Date: Tue, 20 Jun 2000 23:57:00 -0000	[thread overview]
Message-ID: <20000620235656.A28894@shell17.ba.best.com> (raw)
Message-ID: <20000620235700.EnYFMW3Cu2JTg6tqIrs1j_kvBgS1-U1vkiPmmSp-y3Q@z> (raw)
In-Reply-To: <20000621013821.B13791@cygnus.com>

On Wed, Jun 21, 2000 at 01:38:21AM -0400, Chris Faylor wrote:

> Can we get any more detail about what is being downloaded and by whom?

Grope around /www/logs/ftp<something> - it's pretty clear.

The final field is a c or an i - it tells you whether the d/l was 
complete or incomplete.  Useful for a variety of purposes.

I probably have a script in /www/bin which can parse this file and
provide simple summaries  (I'm only on-line for a second right now),
but it's nothing more sophisticated than an awk grep sort type thing.


There are only three solutions.  One, allow only mirror sites to 
access gcc and cygwin.  Two, add a second T1 to sourceware - IanE set
up the Sourceware line so that additional T1s could be added in the
future, anticipating increased demand.  Three, colocate sourceware at
an ISP and pay by-the-byte for the traffic.

Or four, stop the cygwin project and remove all the files. :-)

The bandwidth usage could be reduced slightly - 10% ? - if someone
went around auditing usage.  You know, making periodic snapshots
available only in .bz2 format, adding compressed versions of _all_
web pages so that they'll be downloaded faster, staging mail archives
in a temp directory instead of an ftp directory, that kind of thing.
It's a lot of work and you'd have to know the system really well.
The other options are better.

Jason

  parent reply	other threads:[~2000-06-20 23:57 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 Stan Shebs
2000-06-20 22:05 ` Stan Shebs
2000-12-30  6:08 ` Chris Faylor
2000-06-20 22:13   ` Chris Faylor
2000-12-30  6:08   ` Jeffrey A Law
2000-06-21  8:47     ` Jeffrey A Law
2000-12-30  6:08   ` Jim Kingdon
2000-06-20 22:36     ` Jim Kingdon
2000-12-30  6:08 ` Jim Kingdon
2000-06-20 22:29   ` Jim Kingdon
2000-12-30  6:08   ` Chris Faylor
2000-06-20 22:38     ` Chris Faylor
2000-12-30  6:08     ` Jason Molenda [this message]
2000-06-20 23:57       ` Jason Molenda
2000-12-30  6:08       ` Jason Molenda
2000-06-21  0:09         ` Jason Molenda
2000-12-30  6:08         ` Gerald Pfeifer
2000-06-21  8:11           ` Gerald Pfeifer
2000-12-30  6:08           ` Jeffrey A Law
2000-06-21  8:30             ` Jeffrey A Law
2000-12-30  6:08             ` DJ Delorie
2000-06-21  8:39               ` DJ Delorie
2000-12-30  6:08             ` Gerald Pfeifer
2000-06-22 14:12               ` Gerald Pfeifer
2000-12-30  6:08           ` DJ Delorie
2000-06-21  8:21             ` DJ Delorie
2000-12-30  6:08         ` DJ Delorie
2000-06-21  7:13           ` DJ Delorie
2000-12-30  6:08       ` DJ Delorie
2000-06-21  7:54         ` DJ Delorie
2000-12-30  6:08         ` Chris Faylor
2000-06-21  8:00           ` Chris Faylor
2000-12-30  6:08           ` DJ Delorie
2000-06-21  8:19             ` DJ Delorie
2000-12-30  6:08     ` DJ Delorie
2000-06-21  7:11       ` DJ Delorie

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=20000620235656.A28894@shell17.ba.best.com \
    --to=jason-swarelist@molenda.com \
    --cc=cgf@cygnus.com \
    --cc=dj@cygnus.com \
    --cc=kingdon@panix.com \
    --cc=overseers@sourceware.cygnus.com \
    --cc=shebs@shebs.cnchost.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).