From owner-freebsd-questions@FreeBSD.ORG Fri Mar 9 12:33:58 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 84ED816A407 for ; Fri, 9 Mar 2007 12:33:58 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from mail.potentialtech.com (internet.potentialtech.com [66.167.251.6]) by mx1.freebsd.org (Postfix) with ESMTP id 5134D13C4B8 for ; Fri, 9 Mar 2007 12:33:58 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from vanquish.pgh.priv.collaborativefusion.com (pr40.pitbpa0.pub.collaborativefusion.com [206.210.89.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.potentialtech.com (Postfix) with ESMTP id ABB7FEBC62; Fri, 9 Mar 2007 07:33:57 -0500 (EST) Date: Fri, 9 Mar 2007 07:33:50 -0500 From: Bill Moran To: Noah Message-Id: <20070309073350.4cf9c338.wmoran@potentialtech.com> In-Reply-To: <45F0D9A7.8000201@enabled.com> References: <45F0D9A7.8000201@enabled.com> X-Mailer: Sylpheed 2.3.1 (GTK+ 2.10.9; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: User Questions Subject: Re: syncing user passwd information between servers X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2007 12:33:58 -0000 In response to Noah : > Hi, > > I am trying to figure out the Best admininstrative way to do the following: > > We have two FreeBSD 6.2 servers and want to keep the passwd files in > sync so all the same users can log into each machine, their UID's match, > and when the update the password on one machine the other machine gets > the password. When we add the user to one machine then the other > machine has an additional user too. > > What is the best scheme that we can devise to get this working > technically well? In addition to the other options that have been presented, you may want to consider Kerberos. -- Bill Moran http://www.potentialtech.com