Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 2 Jul 2019 20:53:04 -0500
From:      "Matthew D. Fuller" <fullermd@over-yonder.net>
To:        "@lbutlr" <kremels@kreme.com>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: portsnap broken?
Message-ID:  <20190703015304.GB13599@over-yonder.net>
In-Reply-To: <C391EDBE-A515-4BE5-9E7D-661F1B515BB3@kreme.com>
References:  <c57a7126-bc18-2e67-9e26-b8406c3126d1@FreeBSD.org> <C391EDBE-A515-4BE5-9E7D-661F1B515BB3@kreme.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 02, 2019 at 07:45:26PM -0600 I heard the voice of
@lbutlr, and lo! it spake thus:
> 
> Out of date based on what? How often are you pulling portsnap?

With a little script to pull the snapdates:

% ./psinfo.pl 
            your-org: Sun Jun 30 19:26:35 2019  (2 days, 01:24:42 ago)
            metapeer: Sun Jun 30 19:26:35 2019  (2 days, 01:24:42 ago)
       ec2-eu-west-1: Sun Jun 30 19:26:35 2019  (2 days, 01:24:42 ago)
  ec2-ap-southeast-2: Sun Jun 30 19:26:35 2019  (2 days, 01:24:42 ago)
  ec2-ap-northeast-1: Sun Jun 30 19:26:35 2019  (2 days, 01:24:42 ago)
       ec2-sa-east-1: Sun Jun 30 19:26:35 2019  (2 days, 01:24:42 ago)



-- 
Matthew Fuller     (MF4839)   |  fullermd@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
           On the Internet, nobody can hear you scream.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190703015304.GB13599>