Date: Wed, 18 Apr 2001 14:13:47 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "S. Seven" <seniseven AT yahoo DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: gdbm
In-Reply-To: <20010418072432.14170.qmail@web617.mail.yahoo.com>
Message-ID: <Pine.SUN.3.91.1010418141105.27491A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 18 Apr 2001, S. Seven wrote:

> Tracing the steps, there is a point where file locking
> is tested with fcntl(), which the djgpp system always
> returns as nonzero, and so the test cannot effectively
> complete.

Simply disable the code which locks the data base, or make it always 
return a success status, and it will all work.  File locking on MS-DOS is 
a joke.

Anyway, someone wrote code which implements somewhat limited locking for 
the next version of DJGPP.  When djdev204.zip is released, it will have 
this.