From owner-freebsd-isp Thu Mar 18 6:49:33 1999 Delivered-To: freebsd-isp@freebsd.org Received: from mars.comsys.com (mars.sopris.net [209.38.22.194]) by hub.freebsd.org (Postfix) with ESMTP id 6802C14C0B for ; Thu, 18 Mar 1999 06:49:31 -0800 (PST) (envelope-from alex@comsys.com) Received: from comsys.com (ptp24.sopris.net [209.38.22.24]) by mars.comsys.com (8.9.3/8.8.8) with ESMTP id HAA17246; Thu, 18 Mar 1999 07:53:20 -0700 (MST) Message-ID: <36F11257.691DE923@comsys.com> Date: Thu, 18 Mar 1999 07:48:55 -0700 From: Alex Huppenthal X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kurt Jaeger Cc: freebsd-isp@FreeBSD.ORG Subject: 10,000 plus /etc/passwd file - NIS+? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We are a mid-sized ISP, using FreeBSD for email, pop3, web hosting and dialin authentication. We're designing a set of systems that will handle up our current customer base, around 5,000 up to 10,000. FreeBSD's password file is a database, so I'm assuming lookups are relatively fast. My question is, has anyone used NIS or NIS+ or Bind to manage password files? We're about to start testing with our 5K user base, looking for performance and efficiency, and fault tolerance/high availability. The requirements are duplicate, in-sync copies of password/authentication files so that radius can run on at least 2 servers... Our historic approach as been to rsync off-line hot standby systems. This is simple, inexpensive and with one command and a reboot we can swap our failed unit out. The new system will tolerate a failure of one of our servers. Thoughts on this? Alex Sopris Surfers, LLC Carbondale, CO To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message