From owner-freebsd-net Thu Feb 25 14:15:19 1999 Delivered-To: freebsd-net@freebsd.org Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (Postfix) with ESMTP id 370D414DFA for ; Thu, 25 Feb 1999 14:15:16 -0800 (PST) (envelope-from mike@seidata.com) Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with ESMTP id RAA25213; Thu, 25 Feb 1999 17:14:58 -0500 (EST) Date: Thu, 25 Feb 1999 17:14:57 -0500 (EST) From: To: Brian Cully Cc: GVB , freebsd-net@FreeBSD.ORG Subject: Re: RADIUS Solutions In-Reply-To: <19990225123427.C10052@kublai.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 25 Feb 1999, Brian Cully wrote: > Not at all. The provisioning system pushes out new password databases > every four hours, and those databases are used in the majority of [snip] Thanks for the explanation, I figured I was misunderstanding something. > the cases. However, we wanted instant provisioning as well, so when > we don't find an account in our local password database, we check > the provisioning system directly. This means that we only rarely > hit the network for account validation, and if the provisioning > system is down the only thing that fails is new account login. This sounds like a viable alternative... Out of curiosity, however, has anyone done something similar by actually using NIS? I'd be interested in hearing any success or horror stories. -- Mike Hoskins Systems/Network Administrator SEI Data Network Services, Inc. http://www.seidata.com "In a world where an admin is rendered useless when the ball in his mouse has been taken out, its good to know that I know UNIX." -- toaster.sun4c.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message