From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 21 03:49:50 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0254137B401; Mon, 21 Apr 2003 03:49:50 -0700 (PDT) Received: from snark.ratmir.ru (snark.ratmir.ru [213.24.248.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8948943F85; Mon, 21 Apr 2003 03:49:48 -0700 (PDT) (envelope-from freebsd@snark.ratmir.ru) Received: from snark.ratmir.ru (freebsd@localhost [127.0.0.1]) by snark.ratmir.ru (8.12.9/8.12.9) with ESMTP id h3LAnkC2077910; Mon, 21 Apr 2003 14:49:46 +0400 (MSD) (envelope-from freebsd@snark.ratmir.ru) Received: (from freebsd@localhost) by snark.ratmir.ru (8.12.9/8.12.9/Submit) id h3LAnkAG077909; Mon, 21 Apr 2003 14:49:46 +0400 (MSD) Date: Mon, 21 Apr 2003 14:49:46 +0400 From: Alex Semenyaka To: Doug Barton Message-ID: <20030421104946.GA77853@snark.ratmir.ru> References: <20030419062121.GA70121@snark.ratmir.ru> <20030420140851.H631@znfgre.tberna.bet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030420140851.H631@znfgre.tberna.bet> User-Agent: Mutt/1.5.4i cc: freebsd-hackers@freebsd.org cc: freebsd-gnats-submit@freebsd.org cc: Alex Semenyaka cc: freebsd-stable@freebsd.org Subject: Re: bin/51148 Slow vipw and fast pwd_mkdb X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Apr 2003 10:49:50 -0000 Hi, On Sun, Apr 20, 2003 at 02:11:34PM -0700, Doug Barton wrote: > Having been in a "mondo huge master.passwd file" situation myself, my > comment is that people in this situation should probably not be relying on > tools like vipw to manage their stuff. Actually, there is a such corporative policy in the ISP I've taken that huge master.passwd for the test. The main ideas: 1) no automatic changes in the master.passwd 2) time to time visual check and fix of users' data in master.passwd (heh, column from 'master.passwd's). May be good, may be bad, but it exists. > However, my feelings aren't strong > enough to prompt me to close your PR, so good luck. :) Thanks :) SY, Alex