From owner-freebsd-hackers  Wed Aug 30 00:26:09 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id AAA15616
          for hackers-outgoing; Wed, 30 Aug 1995 00:26:09 -0700
Received: from critter.tfs.com ([140.145.230.252])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id AAA15606
          for <hackers@freebsd.org>; Wed, 30 Aug 1995 00:25:52 -0700
Received: from localhost (localhost [127.0.0.1]) by critter.tfs.com (8.6.11/8.6.9) with SMTP id AAA00343; Wed, 30 Aug 1995 00:25:06 -0700
X-Authentication-Warning: critter.tfs.com: Host localhost didn't use HELO protocol
To: Mark Hittinger <bugs@ns1.win.net>
cc: hackers@freebsd.org
Subject: Re: pwd_mkdb is intense 
In-reply-to: Your message of "Tue, 29 Aug 1995 14:15:46 EDT."
             <199508291815.OAA02459@ns1.win.net> 
Date: Wed, 30 Aug 1995 00:25:05 -0700
Message-ID: <341.809767505@critter.tfs.com>
From: Poul-Henning Kamp <phk@critter.tfs.com>
Sender: hackers-owner@freebsd.org
Precedence: bulk

> We have a rather large password file and I can hear the system groaning
> whenever someone changes their password.  Top shows the process go to
> about 20-30% of the P90 for around 2 or 3 minutes.  Swap space in use
> increases by around 15% during this period.
> 
> chpass/passwd all pass the buck to pwd_mkdb which recreates the entire
> file.
> 
> Is there a utility which updates the various keys in the db for just one
> particular user id?  Would the db routines that pwd_mkdb calls actually
> support the in-place update of a particular record? :-)

You should probably check the cache parameters for the db(3) code.

--
Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
whois: [PHK]                | phk@ref.tfs.com       TRW Financial Systems, Inc.
Just that: dried leaves in boiling water ?