From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Molenda To: Chris Faylor Cc: Jim Kingdon , shebs@shebs.cnchost.com, overseers@sourceware.cygnus.com, DJ Delorie Subject: Re: [Fwd: ftp probs] Date: Sat, 30 Dec 2000 06:08:00 -0000 Message-id: <20000620235656.A28894@shell17.ba.best.com> References: <39504F15.461AA569@shebs.cnchost.com> <200006210529.BAA13670@panix3.panix.com> <20000621013821.B13791@cygnus.com> X-SW-Source: 2000/msg00668.html 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 - 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Molenda To: Chris Faylor Cc: Jim Kingdon , shebs@shebs.cnchost.com, overseers@sourceware.cygnus.com, DJ Delorie Subject: Re: [Fwd: ftp probs] Date: Tue, 20 Jun 2000 23:57:00 -0000 Message-ID: <20000620235656.A28894@shell17.ba.best.com> References: <39504F15.461AA569@shebs.cnchost.com> <200006210529.BAA13670@panix3.panix.com> <20000621013821.B13791@cygnus.com> X-SW-Source: 2000-q2/msg00361.html Message-ID: <20000620235700.EnYFMW3Cu2JTg6tqIrs1j_kvBgS1-U1vkiPmmSp-y3Q@z> 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 - 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