ports.tar update frequency on new mirror

[Clemens Lang]

Hi Ryan,

I'm wondering what update frequency I can expect for ports.tar on the
new main mirror.

I have a cronjob set up that regularly checks whether ports.tar has not
been updated in a while; it came in handy a couple of times because most
developers usually sync using SVN and would not notice the rsync mirror
becoming stale. For the last few days, it has been sending me a regular
stream of emails warning me about old tarballs, even though eventually a
new update was pushed.

The top spot is a mail from around noon today, where ports.tar had not
been updated for 12.5 hours. Is this normal? Should I change my warning
level?

----- Forwarded message from Cron Daemon <XOXOXO.neverpanic.de> -----

Date: Wed, 10 Aug 2016 13:37:01 +0200
From: Cron Daemon <BABA at XOXOXO.neverpanic.de>
To: DADADADA at XOXOXO.neverpanic.de
Subject: Cron <DADADADA at XOXOXO> nice -n20 ionice -c3 /var/www/virtual/macports/home/portsynccheck.sh

rsync://rsync.macports.org/release/tarballs/ports.tar is outdated:
  last updated 12h 35m 17s ago
  at 2016-08-10 01:01:44.000000000 +0200

----- End forwarded message -----

-- 
Clemens