I'm a build master at my company. As part of my responsibilities, I have an automated job that builds our entire product every night, packages the install image and a considerable amount of debug and support information into a single directory (a build package). This is then rsync'ed to several remote sites for use by our developers. Since this build package is getting up to 6Gb each, this consumes an ever increasing amount of network (WAN) bandwidth. It's always bugged me that we end up transmitting all this data to the remote sites, where is may, or may not get used so I have been looking around for something like cachefilesd. I've set up a Linux machine (RHEL6) at a remote site (mine) and set up cachedfilesd on it. Seems to be working great. One issue I've run into though. I would like to have one cached copy at each remote site that will server all the developers and their respective machines. Since cachefilesd appears to work within the NFS client it will cache for that machine, and hopefully serve those users using Windows via Samba. But what about the remote Unix/Linux users? I can't export an NFS mounted filesystem (AFAIK). Any suggestions on how to provide a cache for folks using NFS (short of giving them each their own caches). --- Wayne Johnson, | There are two kinds of people: Those 3943 Penn Ave. N. | who say to God, "Thy will be done," Minneapolis, MN 55412-1908 | and those to whom God says, "All right, (612) 522-7003 | then, have it your way." --C.S. Lewis -- Linux-cachefs mailing list Linux-cachefs@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cachefs
