On 18:13 Mon 31 Jan , Dale wrote: > Nils Holland wrote: > > > > In fact, what I always do is sync one of my machines with an official > > Gentoo mirror via "emerge --sync", and then I just use rsync to > > distribute the updated tree to all my other local machines as in: > > > > rsync --delete -trmv /usr/portage/ <user>@<dest_host>:/usr/portage > > > > One might want to ask rsync to exclude the distfiles directory, > > but I always include it as it oftentimes saves me the download of a > > file I've already downloaded during an emerge on another machine. > > Maybe I am missing something but I have two machines here. I sync to > the Gentoo servers with the main rig and then sync the second rig from > the main rig. All you have to do is start the rsync service and set the > IP address in the SYNC line in make.conf on the second rig. This is my > rsyncd.conf on the main rig: > [...]
That actually makes sense, it would mean that rsyncd would have to be running and appropriately configured on the local "master" machine, and then it would provide the advantage of being able to sync all other local machines with the local master via a standard "emerge --sync" instead of a relatively long rsync command. Indeed, I guess I'll start doing this here as well. However, I have a server hosted at some hosting company as well, and I prefer not to sync it with an official Gentoo mirror, but with my local portage tree, in order to be sure that I have the exact same version of the portage tree on the server that I also use locally. For that case, NAT would prevent my server from contacting an rsync daemon on a local machine, so I'm actually using a locally invoked rsync to "shove" the tree to the server (vs. having the server "fetch" it). I guess that can't easily be changed, but it's not a problem anyway, as my current mode of operation works well. Greetings, Nils -- Nils Holland * Ti Systems, Wunsorf-Luthe (Germany) Powered by GNU/Linux since 1998
