On Tue, 18 Dec 2018, Julien Cristau wrote:
> On 12/18/18 2:26 PM, Scott Ehas wrote:
> > Hello Peter,
> >
> > We have updated the ftpsync.conf, and have reconfigured the cronjob.
> > I'll check in a few hours to see if the sync has finished.
> >
> > 00 03 * * * /opt/debiansync/bin/ftpsync sync:a
On 12/18/18 2:26 PM, Scott Ehas wrote:
> Hello Peter,
>
> We have updated the ftpsync.conf, and have reconfigured the cronjob.
> I'll check in a few hours to see if the sync has finished.
>
> 00 03 * * * /opt/debiansync/bin/ftpsync sync:all
> 00 06 * * * /opt/debiansync/bin/ftpsync sync:all
> 00
Hello Peter,
We have updated the ftpsync.conf, and have reconfigured the cronjob. I'll
check in a few hours to see if the sync has finished.
00 03 * * * /opt/debiansync/bin/ftpsync sync:all
00 06 * * * /opt/debiansync/bin/ftpsync sync:all
00 12 * * * /opt/debiansync/bin/ftpsync sync:all
00 21 *
ping?
On Tue, 11 Dec 2018, Peter Palfrader wrote:
> On Mon, 10 Dec 2018, Scott Ehas wrote:
>
> > We performed an entirely new sync, and I haven't found any errors within
> > the ftpsync logs. Can you confirm everything is correct?
>
> http://mirrors.gigenet.com/debian/project/trace/mirrors.gig
On Mon, 10 Dec 2018, Scott Ehas wrote:
> We performed an entirely new sync, and I haven't found any errors within
> the ftpsync logs. Can you confirm everything is correct?
http://mirrors.gigenet.com/debian/project/trace/mirrors.gigenet.com
says it's from Saturday, December 8.
So the file has t
Hello,
We performed an entirely new sync, and I haven't found any errors within
the ftpsync logs. Can you confirm everything is correct?
Thank you,
Scott E
On Thu, Dec 6, 2018 at 3:23 AM Peter Palfrader wrote:
> On Wed, 05 Dec 2018, Scott Ehas wrote:
>
> > We have removed the straight Rsync c
s
>
> On Wed, Nov 28, 2018 at 2:57 AM Ameen Pishdadi
> wrote:
>
>>
>>
>> -- Forwarded message -
>> From: Peter Palfrader
>> Date: Wed, Nov 28, 2018 at 1:53 AM
>> Subject: Re: Bug#874487: Debian mirror mirrors.gigenet.com:
>> missing-
On Wed, 05 Dec 2018, Scott Ehas wrote:
> We have removed the straight Rsync command, and implemented the ftpsync.
> Please let us know if you spot any issues.
Hm.
It seems it's still running since there's Archive-Update-* flagfiles in
http://mirrors.gigenet.com/debian/
and http://mirrors.gigenet
Peter,
Ill reach out to scott for an update
On Tue, Dec 4, 2018 at 6:10 AM Peter Palfrader wrote:
> ping.
>
> On Wed, 28 Nov 2018, Peter Palfrader wrote:
>
> > Hi!
> >
> > Can you switch to ftpsync and thus cause a tracefile named
> > mirrors.gigenet.com to exist?
> >
> > Cheers,
> >
> > cf.
>
ping.
On Wed, 28 Nov 2018, Peter Palfrader wrote:
> Hi!
>
> Can you switch to ftpsync and thus cause a tracefile named
> mirrors.gigenet.com to exist?
>
> Cheers,
>
> cf.
> https://mirror-master.debian.org/status/mirror-info/mirrors.gigenet.com.html
>
> On Mon, 18 Sep 2017, Peter Palfrader wr
Hi!
Can you switch to ftpsync and thus cause a tracefile named
mirrors.gigenet.com to exist?
Cheers,
cf.
https://mirror-master.debian.org/status/mirror-info/mirrors.gigenet.com.html
On Mon, 18 Sep 2017, Peter Palfrader wrote:
> On Wed, 06 Sep 2017, Peter Palfrader wrote:
>
> > I was checking
Ping.
While there is a tracefile again, we still ask you please switch to a
(modern) version of ftpsync.
Aloha,
Peter
On Wed, 06 Sep 2017, Peter Palfrader wrote:
> I was checking some things in the Debian mirror universe and noticed
> a problem with your mirror:
>
> o trace file:
> I notice
Package: mirrors
User: mirr...@packages.debian.org
Usertags: mirror-problem may-auto-close
Hi,
I was checking some things in the Debian mirror universe and noticed
a problem with your mirror:
o trace file:
I notice that right now there is no tracefile matching your site name in
http://mirror
13 matches
Mail list logo
