Date: Sat, 16 Oct 1999 14:44:47 -0700 (PDT) From: Mike Meyer <mwm@phone.net> To: freebsd-smp@freebsd.org Subject: Re: SMP on 4 Pentium III(450NX) failed Message-ID: <Pine.BSF.4.10.9910161440100.31550-100000@guru.phone.net> In-Reply-To: <Pine.NEB.3.96.991016150043.57427C-100000@shell-3.enteract.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 16 Oct 1999, David Scheidt wrote: ;->On Sat, 16 Oct 1999, Mike Meyer wrote: ;->> The headache that comes with it is you have to manage all those ;->> systems. I've not found a clean approach yet. Is anyone working on one ;->> - or better yet, have one? ;->Hire good admins? Which leads to the obvious next question: anyone know a good way to find (and keep) good admins? :-) Throwing resources at a problem - especially when it's an expensive, hard-to-find resource - isn't what I'd call a clean solution. Or maybe this is a meta-solution: you keep hiring good admins until one comes up with a clean solution for you? ;->What I have tried to do is be as consistent as possible. Build machines ;->that are as close to identical as possible. Use the same hardware in ;->machines, this makes it easier to stock spares, and reduces the number of ;->awful this doesn't work with that problems you have to deal with. ;->Design the application so that the thing is split on logical boundries. ;->Make the sections look as much alike as possible. ;->Automate everything that can be possible automated. O That's the best I've run into as well. Extensive use of such tools as rdist or rsync helps a lot. Even better is using a SCM tool as a distribution mechanism, though that's stretching things a bit. It just seems like there ought to be a better way. <mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9910161440100.31550-100000>