From owner-freebsd-net Thu Sep 14 23:52:10 2000 Delivered-To: freebsd-net@freebsd.org Received: from jason.argos.org (a1-3a105.neo.rr.com [24.93.180.105]) by hub.freebsd.org (Postfix) with ESMTP id BD66B37B422 for ; Thu, 14 Sep 2000 23:51:54 -0700 (PDT) Received: from localhost (mike@localhost) by jason.argos.org (8.10.1/8.10.1) with ESMTP id e8F6lC600378 for ; Fri, 15 Sep 2000 02:47:12 -0400 Date: Fri, 15 Sep 2000 02:47:12 -0400 (EDT) From: Mike Nowlin To: freebsd-net@freebsd.org Subject: NIS replacement 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 We've been using NIS for quite some time to provide auth info, home dir, and login shell info to a bunch of FBSD machines. So far, it's worked fairly well, but it's getting to be a pain to administer - we're looking for something different... In a nutshell, we're primarily using it to make sure that UIDs and GIDs stay the same across multiple machines so that the NFS-mounted directories don't have any ownership problems. This is accomplished through a SQL database with a perl program that queries the DB and builds the NIS maps. It works, but it's really ugly. I've been toying with using RADIUS to handle this, but that only provides the auth info - do any plans exist (or packages available) to handle home dirs and login shells via RADIUS? Or any other suggestions? (Yes, I realize this is kinda vague - it's been a long day...) Tnx - Mike - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Understated/funny man-page sentence of the current time period: From route(4) on FreeBSD-3.4, DESCRIPTION section: "FreeBSD provides some packet routing facilities." ...duh....... Mike Nowlin, N8NVW mike@argos.org http://www.viewsnet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message