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: Sun, 3 Oct 2004 12:10:04 +1000
Message-ID: <5066E5A966339E42AA04BA10BA706AE561C8@rodrick.geeknet.com.au>
Thread-Topic: [pgsql-www] Problem with mirrorring
Thread-Index: AcSotQV0TK7xQieeRaS3d6HdK6we0AAAwVewAA1msAA=
From: "John Hansen" <john@geeknet.com.au>
To: "Dave Page" <dpage@vale-housing.co.uk>,
 "Devrim GUNDUZ" <devrim@gunduz.org>
Cc: "PostgreSQL WWW Mailing List" <pgsql-www@postgresql.org>

Ahemm,...=20

> >=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...
>=20
> Ahh, yes. Of course, that's actually rsync working correctly!=20
> No changes on the server, so no transfers.
>=20
> This does mean that our mirroring is quite innefficient. We=20
> really should diff the results of each build and only update=20
> the html files if there is a change. At the moment each=20
> mirror is probably pulling the whole site each time :-(


Don't you mean quite efficient... ?

I assume the email devrim receives is a list of files changed.
Rsync will do a diff on the files and copy the changes across.
If however the only difference is the timestamp, then the file=20
will still be listed in said email, since it's timestamp was updated.

I hope this weeds out any confusion.

... John