Date: Thu, 9 Nov 2006 18:21:59 +0000 From: Daniel Bye <freebsd-questions@slightlystrange.org> To: freebsd-questions@freebsd.org Subject: Re: multiple ports trees Message-ID: <20061109182159.GA30626@catflap.slightlystrange.org> In-Reply-To: <8153bba90611090710p75da2bcdja1d989ca002eed54@mail.gmail.com> References: <8153bba90611090710p75da2bcdja1d989ca002eed54@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 09, 2006 at 09:10:49AM -0600, Christopher Hobbs wrote: > This message may inadvertently get sent twice. For some reason, > mx1.freebsd.org has been rejecting messages from my work address. Here's > the message that I originally attempted to post: >=20 > Thanks! > cmh >=20 > -- BEGIN SNIP -- >=20 > Hello, list! >=20 > I've got about six production servers and a couple of workstations > running FreeBSD 6.1-STABLE and 6.2-PRERELEASE. Some of these machines > are sitting in DMZ, the others are internal. Currently, each of them > has their own ports tree. >=20 > How terrible of an idea would it be to take one of the production > servers that isn't really doing a whole lot of work, and make it's > /usr/ports available over NFS to the other machines? Am I headed in a > bad direction here? No, this is not a bad idea at all. Just be careful about allowing hosts in the DMZ to mount disks on secure internal machines. You will need to set WRKDIRPREFIX to somewhere local on each machine - not doing so will result in your clients trying to build their ports under the NFS exported file system on the server, leading to enormous amounts of traffic over=20 your network. You might also consider using the unused box to build packages of all=20 the ports your other machines need, and then use pkg_add on the target=20 boxes to install them. If you do this, you'll probably want to make sure that /usr/ports/packages exists on the build host before you start, or you'll end up with packages splattered around the ports tree. You'll also need an ftp server running on the build host, but with appropriate=20 firewall rules this needn't be a gaping hole into your network. >=20 > Also, what about user accounts between machines? I got to thinking that > because some of the servers have the same user accounts, would it be > possible to share a password file or home directories? Should I build > another box strictly for this purpose? If so, could you point me to > some documentation for achieving such a goal? Take a look at http://www.uk.freebsd.org/doc/en_US.ISO8859-1/books/handbook= /network-nis.html. It sounds to me as if it is pretty close to what you wa= nt. As for sharing home directories, this is in the handbook as one of the advantages of NFS: There is no need for users to have separate home directories on every= =20 network machine. Home directories could be set up on the NFS server=20 and made available throughout the network. You might want to look at using AMD to manage this, to avoid having lots of unused permanent NFS mounts hanging around. It very much depends on you network usage, though. HTH Dan --=20 Daniel Bye PGP Key: http://www.slightlystrange.org/pgpkey-dan.asc PGP Key fingerprint: D349 B109 0EB8 2554 4D75 B79A 8B17 F97C 1622 166A --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFU3HHixf5fBYiFmoRAumpAJ0b+rHs4QrFpci7MEh37TuYJx4JfQCePQd9 lxtjEM/CCHieo4k85HZKaTc= =hZsj -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061109182159.GA30626>