You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-dev@apache.org by sebb <se...@gmail.com> on 2012/10/04 17:12:17 UTC
[Mirrors] suggestions for tracking problems with mirrors
Some suggestions for making it easier to track problems with mirror sites.
It would be useful to be able to track which ASF mirror was last used.
This would help us if there are issues with one of our mirrors.
This could be done by creating a timestamp file with the name of the
mirror, e.g.
aurora_time.txt
eos_time.txt
This would show which ASF mirror was being used by the 3rd party mirror sites.
Re: [Mirrors] suggestions for tracking problems with mirrors
Posted by sebb <se...@gmail.com>.
On 4 October 2012 19:41, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
> sebb wrote on Thu, Oct 04, 2012 at 19:01:35 +0100:
>> On 4 October 2012 16:35, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
>> > +1 (concept), though I think having a separate file for that would be
>> > cleaner and simpler to implement.
>>
>> I don't understand - you mention having a separate file, which is what
>> I was proposing anyway?
>>
>> e.g. EU mirror would create aurora_time.txt, US => eos_time.txt
>> (or they could create eu_time.txt/us_time.txt)
>>
>> What is different about your idea?
>
> % ls -1 zzz
> hostname
> time.txt
> % cat hostname
> aurora.apache.org
So can I add the following to the end of runmirmon.sh ?
--- cut here ---
#update the hostname in dist/$HOST
HOST=zzz/hostname.txt
hostname > $DIST/$HOST.tmp
mv -f $DIST/$HOST.tmp $DIST/$HOST
--- cut here ---
I don't think there's any point having a copy of the file under ooo/.
Re: [Mirrors] suggestions for tracking problems with mirrors
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
sebb wrote on Thu, Oct 04, 2012 at 19:01:35 +0100:
> On 4 October 2012 16:35, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
> > +1 (concept), though I think having a separate file for that would be
> > cleaner and simpler to implement.
>
> I don't understand - you mention having a separate file, which is what
> I was proposing anyway?
>
> e.g. EU mirror would create aurora_time.txt, US => eos_time.txt
> (or they could create eu_time.txt/us_time.txt)
>
> What is different about your idea?
% ls -1 zzz
hostname
time.txt
% cat hostname
aurora.apache.org
Re: [Mirrors] suggestions for tracking problems with mirrors
Posted by sebb <se...@gmail.com>.
On 4 October 2012 16:35, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
> +1 (concept), though I think having a separate file for that would be
> cleaner and simpler to implement.
I don't understand - you mention having a separate file, which is what
I was proposing anyway?
e.g. EU mirror would create aurora_time.txt, US => eos_time.txt
(or they could create eu_time.txt/us_time.txt)
What is different about your idea?
> sebb wrote on Thu, Oct 04, 2012 at 16:12:17 +0100:
>> Some suggestions for making it easier to track problems with mirror sites.
>>
>> It would be useful to be able to track which ASF mirror was last used.
>> This would help us if there are issues with one of our mirrors.
>>
>> This could be done by creating a timestamp file with the name of the
>> mirror, e.g.
>>
>> aurora_time.txt
>> eos_time.txt
>>
>> This would show which ASF mirror was being used by the 3rd party mirror sites.
Re: [Mirrors] suggestions for tracking problems with mirrors
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
+1 (concept), though I think having a separate file for that would be
cleaner and simpler to implement.
sebb wrote on Thu, Oct 04, 2012 at 16:12:17 +0100:
> Some suggestions for making it easier to track problems with mirror sites.
>
> It would be useful to be able to track which ASF mirror was last used.
> This would help us if there are issues with one of our mirrors.
>
> This could be done by creating a timestamp file with the name of the
> mirror, e.g.
>
> aurora_time.txt
> eos_time.txt
>
> This would show which ASF mirror was being used by the 3rd party mirror sites.