From owner-freebsd-hackers  Mon Jul  1 13:31:06 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id NAA06234
          for hackers-outgoing; Mon, 1 Jul 1996 13:31:06 -0700 (PDT)
Received: from post.io.org (post.io.org [198.133.36.6])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA06110;
          Mon, 1 Jul 1996 13:30:17 -0700 (PDT)
Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id QAA19774; Mon, 1 Jul 1996 16:29:43 -0400 (EDT)
Date: Mon, 1 Jul 1996 16:29:42 -0400 (EDT)
From: Brian Tao <taob@io.org>
To: Guido van Rooij <guido@gvr.win.tue.nl>
cc: freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG
Subject: Re: Increasing openinfo.cachesize in pwd_mkdb (was Re: Incremental [s]pwd.db updates?)
In-Reply-To: <199607011757.TAA07646@gvr.win.tue.nl>
Message-ID: <Pine.NEB.3.92.960701162415.10629B-100000@zap.io.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 1 Jul 1996, Guido van Rooij wrote:
>
> Wait a few days..I'll commit my diffs to -current then.

   I've come across some master.passwd files that cause my patched
version of pwd_mkdb to segfault, but work fine with the standard
binary.  It may not be possible to arbitrarily set the cachesize value
without tweaking some of the other parameters passed to the db hashing
functions.
--
Brian Tao (BT300, taob@io.org, taob@ican.net)
Systems and Network Administrator, Internet Canada Corp.
"Though this be madness, yet there is method in't"