Actually, I have adopted the "current solution" I was refering to, from our productive code, but it turns out that is was used there only for controlling shared regions between different Windows hosts. I had not expected that there would be a problem when combining Windows and Unix hosts, but indeed, you are right: I wrote the small test program which you suggested and could verify that locking does not work when one process runs on Windows and the other one on Linux. Thanks for pointing this out!!! This will safe me a lot of debugging work.
In reply to Re^10: locking over the network (flock)
by rovf
in thread locking over the network
by rovf
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |