On Mon, 29 Jan 2007 17:38:07 +0100, Harm Geerts wrote: > > I use a slightly different approach here, with an NFS mounted $DISTDIR > > for all machines and one of them doing emerge -f world each morning. > > it's simpler to set up that http-replicator but is less scalable > > since you'll get problems if one machines tries to download a file > > while another is partway through downloading it. > > portage uses locking for distfiles so if your share is writeable you > wouldn't have any need for http-replicator. The locks are kept in > $DISTDIR/.locks/ > > I'm sharing my distfiles over nfs myself and I haven't had any problems. > portage also takes care of stale lockfiles, the masterclient truncates > the lockfile and the other clients fill the lockfile with data. If a > threshold is met the lock is discarded.
You're absolutely right. I set things up like this a long time ago, when portage's lockfiles didn't work over NFS. I've been avoiding the "problem" for so long I'd forgotten it was fixed :( -- Neil Bothwick Computer apathy error: don't bother striking any key.
signature.asc
Description: PGP signature
