GCC mirror changing IPs (fwd)

GCC mirror changing IPs (fwd)

[Gerald Pfeifer]

Hi Guys,

who of you is familiar with the setup we provide to mirrors?  I remember
we *did* have something special at least at some point in the past, but
don't remember specifics.

Gerald

---------- Forwarded message ----------
From: Joe Laffey <joe@laffey.tv>
To: gcc@gcc.gnu.org
Date: Sun, 24 Feb 2008 11:16:41 -0600 (CST)
Subject: GCC mirror changing IPs

Hi,

We operate a GCC release mirror in St. Louis, MO (mirrors.laffeycomputer.com).

This server has changed IP addresses, which is normally no worry on your end.
But the old IP had special access to the master server to be able to download
the releases right when they came out, and thus take some load off of your
servers. This new IP address does not seem to have that.

The old IP was 66.165.104.114 and the new IP is 71.91.230.170. Both should have
a revers DNS PTR of pong.laffeycomputer.com.

If you could enable the mirror access for the new IP I would appreciate it. Note
that the old IP may be active for a little while as well. I am using it to get
the latest release right now.

Thanks,

--
Joe Laffey                |       Visual Effects for Film and Video
LAFFEY Computer Imaging   |     -------------------------------------
St. Louis, MO             |       Show Reel http://LAFFEY.tv/?e09280
USA                       |     -------------------------------------
.                         |        -*- Digital Fusion Plugins -*-
--------------------------------------------------------------------------

Re: GCC mirror changing IPs (fwd)

[Jonathan Larmour]

> ---------- Forwarded message ----------
> From: Joe Laffey <joe@laffey.tv>
> To: gcc@gcc.gnu.org
> Date: Sun, 24 Feb 2008 11:16:41 -0600 (CST)
> Subject: GCC mirror changing IPs
> 
> Hi,
> 
> We operate a GCC release mirror in St. Louis, MO (mirrors.laffeycomputer.com).
> 
> This server has changed IP addresses, which is normally no worry on your end.
> But the old IP had special access to the master server to be able to download
> the releases right when they came out, and thus take some load off of your
> servers. This new IP address does not seem to have that.
> 
> The old IP was 66.165.104.114 and the new IP is 71.91.230.170. Both should have
> a revers DNS PTR of pong.laffeycomputer.com.

Looking at the current mirror setup, there's already an entry in the 
mirrors class:
   From *.laffeycomputer.com

However looking more closely, all the mirrors only help access to cygwin 
releases, not any others. There is no priority access for GCC releases (at 
least not in the FTPD configuration), and the timestamp on the file is 
July last year so this has been the case at least since then, but probably 
ever.

Jifl
-- 
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["The best things in life aren't things."]------      Opinions==mine

Re: GCC mirror changing IPs (fwd)

[Christopher Faylor]

On Sun, Feb 24, 2008 at 10:09:34PM +0000, Jonathan Larmour wrote:
>> ---------- Forwarded message ----------
>> Date: Sun, 24 Feb 2008 11:16:41 -0600 (CST)
>> Subject: GCC mirror changing IPs
>> Hi,
>> We operate a GCC release mirror in St. Louis, MO 
>> (mirrors.laffeycomputer.com).
>> This server has changed IP addresses, which is normally no worry on your 
>> end.
>> But the old IP had special access to the master server to be able to 
>> download
>> the releases right when they came out, and thus take some load off of your
>> servers. This new IP address does not seem to have that.
>> The old IP was 66.165.104.114 and the new IP is 71.91.230.170. Both should 
>> have
>> a revers DNS PTR of pong.laffeycomputer.com.
>
> Looking at the current mirror setup, there's already an entry in the 
> mirrors class:
>   From *.laffeycomputer.com
>
>However looking more closely, all the mirrors only help access to
>cygwin releases, not any others.  There is no priority access for GCC
>releases (at least not in the FTPD configuration), and the timestamp on
>the file is July last year so this has been the case at least since
>then, but probably ever.

Right.  We were limiting access to only certain sites for cygwin
releases because ftp access was swamping the old sourceware's
connection.

AFAIK, there is nothing that needs to be done for a mirror.  I think
that most mirrors these days use rsync, though.

cgf