From owner-freebsd-hackers Sun Apr 20 18:23:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA03696 for hackers-outgoing; Sun, 20 Apr 1997 18:23:03 -0700 (PDT) Received: from agni.nuko.com ([207.82.229.31]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA03691 for ; Sun, 20 Apr 1997 18:22:57 -0700 (PDT) Received: (from vinay@localhost) by agni.nuko.com (8.7.5/8.6.12) id SAA18861 for freebsd-hackers@freebsd.org; Sun, 20 Apr 1997 18:22:44 -0700 (PDT) From: Vinay Bannai Message-Id: <199704210122.SAA18861@agni.nuko.com> Subject: Re: Need a common passwd file among machines To: freebsd-hackers@freebsd.org Date: Sun, 20 Apr 1997 18:22:44 -0700 (PDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks for several suggestions. Lots of cool ideas flying around. That is what I was afraid of. I wanted to make this task as simple as possible. Let's say I have scaled down my expectations and just would be content with having uid/gid consistency over all machines. (Since my cvs tree was exported and people could edit it on their machines, I saw a different user name/group when I looked at the files from my own machine because of the uid/gid mismatch). Considering all this, I am leaning towards NIS. As Terry mentioned in his e-mail, if I consider the network safe enough to do NFS exports, it should be safe enough for NIS. :-( BTW, at Stanford they use AFS systems with Kereberos for authentication. The number of accounts (my guess) would be around 25,000-35,000 accounts. The users are dispersed in differenet AFS cells based on their usernames. The mail being handled by several POP servers. The mail agents on all the machines were modified to use POP3 protocol to retreive the mail from the mail servers. Vinay -- Vinay Bannai E-mail: vinay@agni.nuko.com (408)-526-0280 x 275 (Work) http://agni.nuko.com/~vinay