Has anyone run Pervasive SQL 8.5 on Linux and experienced any issues
regarding failing to handle file locks or corruption of indexes. I am
using Fedora Core 2 (kernel V2.6). To get mkded (the linux btreive
engine) to stay up I had to put this line;
export LD_ASSUME_KERNEL=2.4.18 into the psql user .bash_profile
(as recommended by Pervasive KM article psql6087)

But now when we do multi user access to files we get the above
problems.

Any thoughts would be appreciated,

Craig Talbot.

Pervasive.SQL V8.6 (SP2) should take care of the engine running in
that environment.
http://www.pervasive.com/support/updates/index.asp
specifically
http://www.pervasive.com/support/updates/v8_sp2.asp

I can not think of anything specific with the engine.
I have seen some instances where more than one database engine is able
to open the same file (or open on more than one path by a single
engine). As they each expect to have exclusive access to the file and
cache heavily if that does happen bad things occur.

Are all the users accessing the file client / server through the
single database engine? Double check the Pervasive Monitor utility to
make sure, MicroKernel -> Active Users.

Are the files open on only one path? I do not think the paths get
normalized very well on Linux. This can be caused by some users
accessing a file through links (soft or hard) or even relative paths
in DDF files. Again double check the Pervasive Monitor utility,
MicroKernel -> Active Files screen.

Leonard

On Fri, 20 Aug 2004 09:53:36 +0800, Craig Talbot
<nospam (AT) nospam (DOT) com.au> wrote: