Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: Problem with mirrorring
Date: Sat, 2 Oct 2004 20:46:07 +0100
Message-ID: 
 <E7F85A1B5FF8D44C8A1AF6885BC9A0E430687F@ratbert.vale-housing.co.uk>
Thread-Topic: [pgsql-www] Problem with mirrorring
Thread-Index: AcSotQV0TK7xQieeRaS3d6HdK6we0AAAwVew
From: "Dave Page" <dpage@vale-housing.co.uk>
To: "Devrim GUNDUZ" <devrim@gunduz.org>
Cc: "PostgreSQL WWW Mailing List" <pgsql-www@postgresql.org>

=20

> -----Original Message-----
> From: Devrim GUNDUZ [mailto:devrim@gunduz.org]=20
> Sent: 02 October 2004 20:21
> To: Dave Page
> Cc: PostgreSQL WWW Mailing List
> Subject: Re: [pgsql-www] Problem with mirrorring
>=20
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
>=20
> Merhaba, (heh it means 'hello' in Turkish)
>=20
> On Sat, 2 Oct 2004, Dave Page wrote:
>=20
> > There was a lockfile from this morning, but it won't stop you=20
> > mirroring
> > - you actually mirror from a completely different box. The=20
> lockfile is=20
> > only on the master site and is used to stop lot's of site builds=20
> > running at once if for some reason the database server=20
> slows right down.
> >
> > Do you get any errors when you rsync?
>=20
> :( Sorry to bother you but what I meant was the problem that=20
> has happened
> before:
>=20
> http://archives.postgresql.org/pgsql-www/2004-09/msg00149.php
> and your reply:
> http://archives.postgresql.org/pgsql-www/2004-09/msg00152.php
>=20
> There was not an 'error' exactly...

Ahh, yes. Of course, that's actually rsync working correctly! No changes
on the server, so no transfers.

This does mean that our mirroring is quite innefficient. We really
should diff the results of each build and only update the html files if
there is a change. At the moment each mirror is probably pulling the
whole site each time :-(

Regards, Dave.