Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: Mirror cleanup
Date: Sat, 13 Nov 2004 11:44:34 -0000
Message-ID: 
 <E7F85A1B5FF8D44C8A1AF6885BC9A0E430711A@ratbert.vale-housing.co.uk>
Thread-Topic: [pgsql-www] Mirror cleanup
Thread-Index: AcTJSNphYroZMtvVTB6vrbY8P+R9rAALMNCw
From: "Dave Page" <dpage@vale-housing.co.uk>
To: "Robert Treat" <xzilla@users.sourceforge.net>
Cc: <pgsql-www@postgresql.org>

=20

> -----Original Message-----
> From: Robert Treat [mailto:xzilla@users.sourceforge.net]=20
> Sent: 13 November 2004 06:18
> To: Dave Page
> Cc: pgsql-www@postgresql.org
> Subject: Re: [pgsql-www] Mirror cleanup
>=20
> On Thursday 11 November 2004 10:54, Dave Page wrote:
> > Hi guys,
> >
> > I was intending to cleanup all the mirror sites. Anyone object if I=20
> > delete every mirror that hasn't sync'd in, say, the last 3 months?
> >
>=20
> Are you just deleting the ones that don't synch up or are you=20
> planning on resequencing the remaining mirrors ?

I'm deleting those that clearly haven't sync'ed for a long time.
Renumbering is a whole different problem, because most have vhosts setup
for a specific hostname - only the newer ones are *.postgresql.org. I
forgot about that when I rehashed Vince's old code and we lost most of
the mirrors for a few days a couple of years back :-(

I'm also looking at rewriting the sync detection system to give much
better control over out of date or broken mirrors. I expect to be able
to add email warnings to tell admins (and us) that there is a problem,
and be able to detect broken ftp paths and vhost configs.

Regards, Dave.