Received: (from majordom@localhost) by hyperreal.org (8.8.5/8.8.5) id QAA16887; Mon, 21 Jul 1997 16:45:09 -0700 (PDT) Received: from valis.worldgate.com (marcs@valis.worldgate.com [198.161.84.2]) by hyperreal.org (8.8.5/8.8.5) with ESMTP id QAA16797 for ; Mon, 21 Jul 1997 16:45:01 -0700 (PDT) Received: from localhost (marcs@localhost) by valis.worldgate.com (8.8.5/8.8.5) with SMTP id RAA24896 for ; Mon, 21 Jul 1997 17:44:53 -0600 (MDT) Date: Mon, 21 Jul 1997 17:44:53 -0600 (MDT) From: Marc Slemko To: new-httpd@apache.org Subject: Re: dbmmanage overhaul In-Reply-To: <3.0.3.32.19970721161259.0082d620@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org On Mon, 21 Jul 1997, Brian Behlendorf wrote: > > Well I personally liked that fact the old one was still perl 4 compatible, > but maybe I'm the only one still in the dark ages with /usr/local/bin/perl > = perl4. At any rate I won't protest it. > > Since there are now a myriad of dbm file formats, is there any way to > distinguish between them when presented with a file of unknown dbm type? > I.e. if I have a file called passwd.db, how can I tell whether it's ndbm, > gdbm, sdbm, etc? Could we have that be an option in the dbmmanage program? file(1) works. pagetabl.db: Berkeley DB Hash file (Version 2, Little Endian, Bucket Size 4096, Directory Size 12, Segment Size 256, Segment Shift 256, Overflow Point 8, Last Freed 3, Max Bucket 2, High Mask 0x6, Low Mask 0x7, Fill Factor 3, Number of Keys 40)