From owner-freebsd-hackers  Wed Apr  2 01:14:00 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id BAA17164
          for hackers-outgoing; Wed, 2 Apr 1997 01:14:00 -0800 (PST)
Received: from ilink.nis.za (root@ilink.nis.za [196.6.121.10])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id BAA17158
          for <freebsd-hackers@freebsd.org>; Wed, 2 Apr 1997 01:13:55 -0800 (PST)
Received: (from keith4@localhost) by ilink.nis.za (8.6.12/8.6.6) id LAA03056 for freebsd-hackers@freebsd.org; Wed, 2 Apr 1997 11:13:45 +0200
From: keith waters <keith4@ilink.nis.za>
Message-Id: <199704020913.LAA03056@ilink.nis.za>
Subject: Unreasonable rebuild time on large password files
To: freebsd-hackers@freebsd.org
Date: Wed, 2 Apr 1997 11:13:44 +0200 (SAT)
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi all..

We've got rather a lot of users in our /etc/passwd and every time we change or add a password/login, we have to wait over TEN MINUTES for the 'database to rebuild'  [And yes, we have a pretty reasonably powerful machine]

This must be one of the worst cases of code/resourse optimisation, since changing a password means rebuilding EVERY SINGLE entry in the password databases.

Surely this can all be done with one quick write to the relevant files? 

Does anybody out there have a working solution ?  Please!

Thanks
Regards,
Keith Waters
(Interlink Internet Services)

[Please preferably use keith@nis.za]