From owner-freebsd-hackers Mon Mar 9 23:10:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29616 for freebsd-hackers-outgoing; Mon, 9 Mar 1998 23:10:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tahiti.oss.uswest.net (tahiti.oss.uswest.net [204.147.85.151]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29513 for ; Mon, 9 Mar 1998 23:09:57 -0800 (PST) (envelope-from rantapaa@uswest.net) Received: (from rantapaa@localhost) by tahiti.oss.uswest.net (8.8.5/8.6.12) id BAA28400; Tue, 10 Mar 1998 01:09:45 -0600 (CST) Date: Tue, 10 Mar 1998 01:09:45 -0600 (CST) From: Erik E Rantapaa To: ken@mui.net cc: hackers@FreeBSD.ORG Subject: Re: radius? In-Reply-To: <199803092306.NAA16334@rocksalt.mui.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Mar 1998 ken@mui.net wrote: > There are going to be 2 locations. Site A and site B have 2 > different user databases. How does one set things up so that if they > aren't in site A, then it passes it to site B? or is there a better > way to handle this? The easiest way I've found is to merge the password files. Helpful tip: when building large db file (version 1.85), set the cache size (in the openinfo structure) to be as large as possible. The optimal seems to be a little less than the final size of the db file (oddly enough, having a cache larger than the db degrades performance slightly). This will greatly improve the speed of pwd_mkdb and yp_mkdb. The same holds true for DB2. > Does it have something to do with Radius? ??? Radius doesn't have anything to do with Unix user authentication. There are radius servers which will proxy requests, but it's not really anything close to logically merging two user databases. Regards, Erik Rantapaa rantapaa@uswest.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message