From: Jeffrey A Law <law@cygnus.com>
To: Chris Faylor <cgf@cygnus.com>
Cc: Stan Shebs <shebs@shebs.cnchost.com>, overseers@sourceware.cygnus.com
Subject: Re: [Fwd: ftp probs]
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <9742.961601687@upchuck> (raw)
In-Reply-To: <20000621011314.B13594@cygnus.com>
In message < 20000621011314.B13594@cygnus.com >you write:
> On Tue, Jun 20, 2000 at 10:13:58PM -0700, Stan Shebs wrote:
> >Are there any plans to solve this? When I go to test that the packages
> >really are downloadable, I can never get on either... -s
>
> Do I remember ftp stats somewhere? It would be nice to see what's eating
> up the bandwidth (I fear it's cygwin...)
I get a summary each week from one of Jason's scripts. The big hogs (in
order, highest to lowest) are cygwin, gcc, gdb. After that, nobody matters.
I don't have the report handy, but if anyone is interested I can forward it
when I get it this weekend.
jeff
WARNING: multiple messages have this Message-ID
From: Jeffrey A Law <law@cygnus.com>
To: Chris Faylor <cgf@cygnus.com>
Cc: Stan Shebs <shebs@shebs.cnchost.com>, overseers@sourceware.cygnus.com
Subject: Re: [Fwd: ftp probs]
Date: Wed, 21 Jun 2000 08:47:00 -0000 [thread overview]
Message-ID: <9742.961601687@upchuck> (raw)
Message-ID: <20000621084700.ddZ0dgCJmh6DaEyioEyVFimJuh9AHgmKAkZ-mZ-jzMw@z> (raw)
In-Reply-To: <20000621011314.B13594@cygnus.com>
In message < 20000621011314.B13594@cygnus.com >you write:
> On Tue, Jun 20, 2000 at 10:13:58PM -0700, Stan Shebs wrote:
> >Are there any plans to solve this? When I go to test that the packages
> >really are downloadable, I can never get on either... -s
>
> Do I remember ftp stats somewhere? It would be nice to see what's eating
> up the bandwidth (I fear it's cygwin...)
I get a summary each week from one of Jason's scripts. The big hogs (in
order, highest to lowest) are cygwin, gcc, gdb. After that, nobody matters.
I don't have the report handy, but if anyone is interested I can forward it
when I get it this weekend.
jeff
next prev parent reply other threads:[~2000-12-30 6:08 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 ` 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
2000-06-20 23:57 ` Jason Molenda
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 ` 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 ` DJ Delorie
2000-06-21 8:21 ` DJ Delorie
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 7:13 ` DJ Delorie
2000-12-30 6:08 ` DJ Delorie
2000-06-21 7:11 ` DJ Delorie
2000-12-30 6:08 ` Chris Faylor
2000-06-20 22:13 ` Chris Faylor
2000-12-30 6:08 ` Jim Kingdon
2000-06-20 22:36 ` Jim Kingdon
2000-12-30 6:08 ` Jeffrey A Law [this message]
2000-06-21 8:47 ` Jeffrey A Law
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=9742.961601687@upchuck \
--to=law@cygnus.com \
--cc=cgf@cygnus.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).