From owner-freebsd-hackers Fri Jan 9 21:55:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA23098 for hackers-outgoing; Fri, 9 Jan 1998 21:55:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mutara.noc.erols.net (gjp@mutara.noc.erols.net [207.172.25.12]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA23084 for ; Fri, 9 Jan 1998 21:55:44 -0800 (PST) (envelope-from gjp@mutara.noc.erols.net) Received: (from gjp@localhost) by mutara.noc.erols.net (8.8.8/8.8.7) id AAA01049; Sat, 10 Jan 1998 00:55:42 -0500 (EST) Date: Sat, 10 Jan 1998 00:55:42 -0500 (EST) Message-Id: <199801100555.AAA01049@mutara.noc.erols.net> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 References: From: gjp@erols.com (Gary Palmer) Subject: Re: How are people handling lots of accounts? X-Original-Newsgroups: lists.freebsd.hackers To: hackers@FreeBSD.ORG Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk In article , mrcpu@cdsnet.net (Jaye Mathisen) writes: > Is there anything that can be done to speed this up? Changing the > password isn't too bad, only about 30 seconds, but adding takes forever. Use CDB instead of Berkeley DB. A competent programmer could do this in less than a day. You could probably rebuild a 50,000 user password file in less than a minute. Unfortunately, single-user password changes will need to be un-done and the entire file rebuilt, rather than the optimization in passwd/pwd_mkdb which doesn't rebuild the file for a single user change. (Unless you hack CDB to allow the data to be changed without the key being changed .. since the data (the password) will be the same length, in theory, its possible) Gary