Hello,
just to add some info to my previous e-mail...
I have followed each step in my example reading the file /proc/locks,
and I can see that my kernel follow the POSIX lock. No problem with the
kernel.
Operation are like you say, "close" release all locks. Therefore
probably it is correct tha
...uhm...
I am using a CENTOS 5.3 and I suppose that kernel do not have bug... I
have updated system regularly.
Really I am a little confused
Using my wrong "filebuf.c" (that do not use hb_fileFind()) I have tried
to run the following program.
function main()
set exclusive off
dbcreate("t
On Mon, 20 Jul 2009, Marco Bernardi wrote:
Hi,
I think I was not clear enough and confused you so I'll try to be more
precise because it may be source of some serious problems.
> I am using linux 2.6 and seems it is like you say, close() didn't release
> lock.
It for sure release the fcntl() lo
Hello,
I am using linux 2.6 and seems it is like you say, close() didn't
release lock.
I have done following test: I have modified "filebuf.c" blocking the
hb_findFile() function... so any use command create a new handle and it
should create problems in POSIX locks.
I created a short programs
On Sat, 18 Jul 2009, be...@alice.it wrote:
Hi,
> thank you very much for your detailed answer. Now the situation is clear.
> In my programs the duplicate aliases are usually open in READONLY and in
> case of update I open the table again in RW, I make the update and I
> reclose the alias.
> It s
