Date: Fri, 25 Oct 2013 14:22:24 -0700 From: David Newman <dnewman@networktest.com> To: freebsd-questions@freebsd.org Subject: Re: (de)centralized ports management with portsnap Message-ID: <526AE110.9030105@networktest.com> In-Reply-To: <CAHHBGkqRQBcs1RKKaysMgfd8TiuiVgch6PkwB8uF6FRKo%2BUZyA@mail.gmail.com> References: <526AC748.6010805@networktest.com> <CAHHBGkqRQBcs1RKKaysMgfd8TiuiVgch6PkwB8uF6FRKo%2BUZyA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/25/13 2:18 PM, illoai@gmail.com wrote: > On 25 October 2013 15:32, David Newman <dnewman@networktest.com> wrote: >> I'm setting up a group of FreeBSD servers that use 'portsnap fetch' and >> then 'portsnap update' to refresh their ports trees. >> >> Can I set up a local master to avoid pulling updates multiple times? If >> portsnap isn't the right tool for this, what is? >> >> Apologies if this has been asked before; this seems like a standard >> problem, but I didn't see an answer in a web search, the portsnap >> manpage, or in the Michael W. Lucas FreeBSD book. > > It's probably simplest to simply pull with one machine & then use > rsync or some such to push the updates out to the client machines > which would then run "portsnap update" as needed. Thanks. What directories would get rsync'd over for the updates? Is it really as simple as just copying over /usr/ports to each machine? thanks again dn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?526AE110.9030105>