From owner-freebsd-isp Sat Apr 12 16:57:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA02459 for isp-outgoing; Sat, 12 Apr 1997 16:57:59 -0700 (PDT) Received: from super-g.inch.com (super-g.com [204.178.32.161]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA02445 for ; Sat, 12 Apr 1997 16:57:54 -0700 (PDT) Received: from localhost (spork@localhost) by super-g.inch.com (8.8.5/8.6.9) with SMTP id UAA05891; Sat, 12 Apr 1997 20:07:01 -0400 (EDT) Date: Sat, 12 Apr 1997 20:07:01 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: "Jordan K. Hubbard" cc: "Jeffrey J. Mountin" , Vincent Poy , isp@freebsd.org Subject: Re: TS Holy War (was Re: Some advice needed.) In-Reply-To: <26230.860883125@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 12 Apr 1997, Jordan K. Hubbard wrote: > I know of one ISP who had 3 machines doing the work of one (everything > split out, as you say, but with only 200 customers) and it only increased > the maintainance headache to *no* gain whatsoever. 3 machines to secure, > 3 machines to maintain, it was evil. I stuck all the services back > on ONE machine again and made a 2nd one a redundant spare for the 1st, > with all of its important files rsync'd over nightly. The 3rd machine > then came free to go to someone's house or something. :-) But 200 customers is not an ISP, that's a hobby ;) As far as maintaining 3, well, seal them off to the world; the shell machine is really the major risk. Plus, if you standardize on one OS (like FBSD) and one release, things you folks provide us like CVSUP make maintenance a breeze. I maintain a dozen machines along with one other person, and it got really easy once we got an OS that worked. It's a nice learning environment that really pays off in the long run. You end up writing scripts to do such tasks as blowing your nose :) Charles