Port Management on a larger scale

[Roland Smith]

On Tue, Jul 22, 2008 at 12:41:46AM -0400, Derek Belrose wrote:
> What is the recommended way of doing port management? 

There doesn't seem to be a single standard way of doing this. There are
several things you could do, assuming that all servers use identically
configured software.

Probably the least effort would be to update and test the ports one
server, then use rsync to push /usr/local from that server to all
others. This is efficient because you only have to build stuff once, an
can then easily push it to other machines.

Alternatively you could use one server to build packages which are then
stored on a shared filesystem to install on all others, but that sounds
like more work to me.

Or you could mount /usr/local from a single NFS server on all others,
keeping them automatically in sync but that might strain the NFS server
and make it a single point of failure which is undesirable. Maybe it
would be better to use the Coda filesystem in this case. 

I'd favor the rsync approach, because it keeps data and programs locally
accessible on each machine while making in easy and efficient to
syncronize from a test machine to others.

Roland
-- 
R.F.Smith                                   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20080723/3e830ca1/attachment.pgp