Date: Wed, 13 Sep 2017 02:03:53 +0200 From: Rainer Duffner <rainer@ultra-secure.de> To: Jason Tubnor <jason@tubnor.net> Cc: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: Mirror the freebsd-update server? Message-ID: <746F3D00-FE25-4784-BB5A-CD6A3D8147BC@ultra-secure.de> In-Reply-To: <CACLnyC%2B_khEYUrM4v5DtqmGYB5cLDqVpAvJNf5qrp%2BgWS5_-7Q@mail.gmail.com> References: <c58331f8b59d72ccd923411d6463c58a@ultra-secure.de> <38999763-9687-4FA2-9072-62A9606448EC@theory14.net> <20170912215219.GG81427@home.opsec.eu> <CACLnyC%2B_khEYUrM4v5DtqmGYB5cLDqVpAvJNf5qrp%2BgWS5_-7Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 13.09.2017 um 00:09 schrieb Jason Tubnor <jason@tubnor.net>: >=20 > I found this useful. I made some adjustments for what I needed but = those > updates are sweet now :-) > = https://wiki.freebsd.org/VladimirKrstulja/Guides/FreeBSDUpdateReverseProxy= = <https://wiki.freebsd.org/VladimirKrstulja/Guides/FreeBSDUpdateReverseProx= y> "This is a simple cache. That means it doesn't consider the files as a = whole repository, which in turn means updates to your cache are not = atomic. It'd be advised to nuke your cache before your update run, as = its point is only to retain the files in a local cache for some short = period of time required for all your machines to be updated.=E2=80=9C The problem is, my updates don=E2=80=99t work that way. These servers all belong to different customers (well, some have a = couple) and I can=E2=80=99t patch them in =E2=80=9Esome short period of = time=E2=80=9C. It=E2=80=99s continuous process. I have other stuff to do. And I have to negotiate downtimes etc.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?746F3D00-FE25-4784-BB5A-CD6A3D8147BC>