From owner-freebsd-hackers  Mon Mar  4 12:08:25 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA23850
          for hackers-outgoing; Mon, 4 Mar 1996 12:08:25 -0800 (PST)
Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA23814
          for <hackers@freebsd.org>; Mon, 4 Mar 1996 12:07:37 -0800 (PST)
Received: by gvr.win.tue.nl (8.6.12/1.53)
    id VAA14023; Mon, 4 Mar 1996 21:06:59 +0100
From: guido@gvr.win.tue.nl (Guido van Rooij)
Message-Id: <199603042006.VAA14023@gvr.win.tue.nl>
Subject: Re: pwd_mkdb - really slow :(
To: julian@ref.tfs.com (JULIAN Elischer)
Date: Mon, 4 Mar 1996 21:06:59 +0100 (MET)
Cc: rashid@rk.ios.com, hackers@freebsd.org
In-Reply-To: <199603040341.TAA27629@ref.tfs.com> from "JULIAN Elischer" at Mar 3, 96 07:41:43 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-hackers@freebsd.org
Precedence: bulk


> As I understand it, changes were made to do single-point
> changes, and to speed all this up in the 'passwd' case.
> 

yep. That's what I did. It is still hanging around here, but I want
to commit it soon, possible protected with an #ifdef.

I made patches for every command that changes a single user at a time,
chpass and friends, passwd, yppasswdd, pwd_mkdb. I did not do adduser (yet).

Things are harder for vipw, as:

> to speed up mkpwd you would need a 'diff' file of 
> before and after' and do the changes as a set of single-point changes.
> This requires that you trust the passwd.master and the database
> files to be correctly in sync.
> 

And you should calculate a turnaround point where it is more wise to
completely rebuild the databases.
> 
> > 
> > 
> > 	I have quite afew systems here with ~10.00 accounts
> > 	on ea ... and pwd_mkdb is _very slow now ... Takes
> > 	2+ minutes to rebuild the damn databases every time.

This should go back to a few seconds, depending on the size of your
*pwd.db files.

-Guido