Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: Moving services to a new server / IP ...
Date: Mon, 5 Apr 2004 16:21:17 +0100
Message-ID: <03AF4E498C591348A42FC93DEA9661B889F96B@mail.vale-housing.co.uk>
Thread-Topic: [pgsql-www] Moving services to a new server / IP ...
thread-index: AcQbGDm1zPQwEQbqRFeDTR7Nc3jRBQACTYVQ
From: "Dave Page" <dpage@vale-housing.co.uk>
To: "Marc G. Fournier" <scrappy@postgresql.org>
Cc: <pgsql-www@postgresql.org>, <pgsql-core@postgresql.org>

=20

> -----Original Message-----
> From: Marc G. Fournier [mailto:scrappy@postgresql.org]=20
> Sent: 05 April 2004 15:14
> To: Dave Page
> Cc: scrappy@postgresql.org; pgsql-www@postgresql.org;=20
> pgsql-core@postgresql.org
> Subject: Re: [pgsql-www] Moving services to a new server / IP ...
>=20
> True, but all that means is that the script to do the updates=20
> just needs to copy over the appropriate rsyncd.conf file that=20
> gets generated, no?
> That is, I believe, the only part that is database driven?

No, there is a C prog that periodically scans the rsync logfile and sets
the last sync timestamp in the DB based on when it sees connections from
the mirrors. That's how we keep track of which mirrors are up to date.

Regards, Dave