Is there any possiblity that you called dba_open multiple times in a row without closing the database?
gdbm apparently automatically places a file lock on the target file when dba_open is called..
obviously attempting to dba_open a file which has been locked by the current process, or any other process or thread for that matter, will result in an error. (note: the only case it doesn't result in an error is when all of the locks are "read" locks)
Also notice that multiple dba_open calls, without matching close calls, don't necessarily have to appear in the same page for this error to occur. An apparently harmless page with matching open and close calls can just as well spew out this error if multiple users access it at the same time.
I found this case to be the most annoying of all since I haven't yet found a fool proof method of taking care of the problem.
Any suggestions?
Patrick wrote:
Hi,
I'm getting this error and I really don't know why, when I do phpinfo(); I have --with-gdbm so I guees my php 4.0.1 should support gdbm.
code,
dba_open("password","r","gdbm");
the error
Warning: driver initialization failed in /home/patrick/public_html/test/dbmtest/index.php on line 1
any ideas ?
I've searched but I have no clue I've even installed all the RPM packages with their name starting with gdb...
help!!
thanks.