22 Oct
2020
22 Oct
'20
4:28 p.m.
---------- Forwarded Message ----------
Subject: Re: [trinity-devel] UK Mirror Service mirrors
Date: Thu October 22 2020, 07:27:34
From: Tim Bishop <tdb(a)mirrorservice.org>
To: Mike Bird <mgb-trinity(a)yosemite.net>
Hi Mike,
On Thu, Oct 22, 2020 at 01:47:58AM -0700, Mike Bird wrote:
On Sun July 19 2020 03:25:35 Tim Bishop wrote:
Looks like the sync on both machines had hung. I don't know if that's a
network issue, or an issue at one end or the other. Eventually our "sync
reaper" script notices and kills the sync which lets another start. That
happened for copernicus already, but kuiper was still hung - I've kicked
it now so it'll catch up soon.
Tim.
--
Tim Bishop,
Computing Officer, School of Computing, University of Kent.
PGP Key: 0x6C226B37FDF38D55
-------------------------------------------------------
The two servers sync independently. Whilst this
is not an ideal
situation, and can lead to them having slightly out of step content,
it's the simplest approach and requires the least development and
maintenance work. In theory they should sync within an hour of each
other, so the likely reason for them to have different files for an
extended period is that one of them is failing to sync. Obviously this
is something that's quite easy to investigate at the time, but
impossible to work out later. So if you see this please let us know at
the time so we can see why it's happening.
The primary mirror daily report issued an hour ago included this:
0 files missing from copernicus.mirrorservice.org::trinitydesktop.org/
33495 files missing from kuiper.mirrorservice.org::trinitydesktop.org/ 
22 Oct
22 Oct
5:12 p.m.
On Thursday 22 of October 2020 18:28:42 Mike Bird via tde-devels wrote:
---------- Forwarded Message ----------
Subject: Re: [trinity-devel] UK Mirror Service mirrors
Date: Thu October 22 2020, 07:27:34
From: Tim Bishop <tdb(a)mirrorservice.org>
To: Mike Bird <mgb-trinity(a)yosemite.net>
Hi Mike,
On Thu, Oct 22, 2020 at 01:47:58AM -0700, Mike Bird wrote:
Thank you Mike for your vigilance when synchronizing mirrors! This is a
very meritorious activity at this time, when packages for the upcoming
R14.0.9 are gradually being uploaded.
Note: As you can see, I have not yet made the intended modification of the
mirror list processing. So there are still these mirrors listed
individually. But I didn't forget it. I hope that after the release there
could be some time that I will be able to devote to the modification.
Cheers
--
Slávek
On Sun July 19 2020 03:25:35 Tim Bishop wrote:
Looks like the sync on both machines had hung. I don't know if that's a
network issue, or an issue at one end or the other. Eventually our "sync
reaper" script notices and kills the sync which lets another start. That
happened for copernicus already, but kuiper was still hung - I've kicked
it now so it'll catch up soon.
Tim. The two servers sync independently. Whilst this
is not an ideal
situation, and can lead to them having slightly out of step content,
it's the simplest approach and requires the least development and
maintenance work. In theory they should sync within an hour of each
other, so the likely reason for them to have different files for an
extended period is that one of them is failing to sync. Obviously
this is something that's quite easy to investigate at the time, but
impossible to work out later. So if you see this please let us know
at the time so we can see why it's happening.
The primary mirror daily report issued an hour ago included this:
0 files missing from copernicus.mirrorservice.org::trinitydesktop.org/
33495 files missing from kuiper.mirrorservice.org::trinitydesktop.org/ 
11:48 p.m.
New subject: 回复：[trinity-devel] Re: Fwd: Re: [trinity-devel] UK Mirror Service mirrors
1280
days inactive
1280
days old
2 comments
3 participants
participants (3)
-
chang_1275＠163.com -
Mike Bird -
Slávek Banko