From owner-freebsd-hackers Wed Apr 2 15:08:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA02508 for hackers-outgoing; Wed, 2 Apr 1997 15:08:50 -0800 (PST) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA02496 for ; Wed, 2 Apr 1997 15:08:45 -0800 (PST) Received: from localhost (taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP id SAA07257; Wed, 2 Apr 1997 18:07:50 -0500 (EST) Date: Wed, 2 Apr 1997 18:07:50 -0500 (EST) From: Brian Tao To: Joerg Wunsch cc: freebsd-hackers@freebsd.org, keith waters Subject: Re: Unreasonable rebuild time on large password files In-Reply-To: <19970402212443.OT00003@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 2 Apr 1997, J Wunsch wrote: > > No need. It's already there. Guido once implemented incremental > updates to the password database if only a single user's entry has > been changed. They seem to be non-optional (much to my surprise :), > and the default in FreeBSD 2.2 and above. Ah, geez, that's right... I even remember pestering him about it a long time ago. :) So the patches have been integrated? I didn't see any mention of them in the man pages, so I presumed it was still necessary to patch it separately. How do you enable the feature? -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't"