Suggested workarounds?I take it the suggested workarounds in your link is no good for some reason?
This one: "to create a "lockfile" in the same directory as the file being opened."
They actually recommend fcntl() and say: "By using advisory locking, your application will be able to work in a cooperative manner with Carbon, Classic, and other applications in the future."
I tried adding O_EXLOCK + O_NONBLOCK to open() but it didn't help.
Anything else that I missed? Is this how it works only on BSD or can I expect problems on Linux? I see "Kernel hacker" beside your name...
Ah, and I have this book by Arnold Robbins, Linux Programming by Example where he covers on pg 532 flock(), fcntl() and lockf().
Maybe I should try my luck with flock() or lockf()?
And even in Beginning Linux Programming, by Neil Matthew & Richard Stones they use fcntl() without any warnings about "shared volumes".