From owner-freebsd-database@FreeBSD.ORG Mon Dec 5 15:50:07 2005 Return-Path: X-Original-To: freebsd-database@freebsd.org Delivered-To: freebsd-database@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E47F616A43D for ; Mon, 5 Dec 2005 15:50:07 +0000 (GMT) (envelope-from julesg@shilohyrc.com) Received: from proc5.arainc.com (proc5.arainc.com [66.254.6.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78B9443D55 for ; Mon, 5 Dec 2005 15:50:07 +0000 (GMT) (envelope-from julesg@shilohyrc.com) Received: from localhost ([127.0.0.1]) by proc5.arainc.com (Merak 7.5.2) with SMTP id IWG74382; Mon, 05 Dec 2005 09:50:06 -0600 Date: Mon, 05 Dec 2005 09:50:06 -0600 From: "Julesg" To: freebsd-database@freebsd.org Message-ID: X-Mailer: Webmail 5.3.0 X-Originating-IP: 66.92.66.128 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: a problem with the btree facility in FreeBSD X-BeenThere: freebsd-database@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Database use and development under FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 15:50:08 -0000 (Please excuse my recent post to 'questions' -- I didn't realize that a database oriented mailgroup existed.) A friend and I needed a DB for our application. We chose the binary-tree organization and went to work; (Our problem has been confirmed on both release 5.2.1 and 5.3.1) During processing the permissions line on the file is all ZERO's (a horizontal line of dashes) and is unchanged after the file is closed (we do a DB-close, not our own close, nor do we simply exit the application.) But the permissions don't change, and we can't (in a subsequent application,) running another job, open the DB and either read or write the existing DB file. Our application, DB-wise, is pretty simple. We'd just like to show a few lines to a real DB programmer (someone with experience using these tools) and learn what the fix is. We built a six line program (might be a little longer, but not much) that exhibits the identical error profile. I am trying to get a copy of the small example program now and should have it available soon to show an interested party. --jg