You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After I've discovered 0, I'm writing a small tool for auditing a kv file. The plugable "lock" functionality adopted by kv earlier effectively forces to use the same locking as Camlistore uses. Otherwise the DB can be locked by Camlistore, but can appear unlocked to the tool if it doesn't use the same or compatible locking mechanism.
The docs1 say: "On Linux and OSX, a lock has the same semantics..." and later "Lock is not yet implemented on other operating systems, and calling it will return an error.".
Even though windows are not mentioned anywhere, I think they are supported, but I want to be sure. Can you please clarify this and/or fix the docs?
If you prefer me to do a pull request changing only the docs, please let me know.
The text was updated successfully, but these errors were encountered:
Easy: it is not easy, and esp. on POSIX, it is only advisory (your lock is effective only for the same locking mechanism - see https://en.wikipedia.org/wiki/File_locking).
After I've discovered 0, I'm writing a small tool for auditing a kv file. The plugable "lock" functionality adopted by kv earlier effectively forces to use the same locking as Camlistore uses. Otherwise the DB can be locked by Camlistore, but can appear unlocked to the tool if it doesn't use the same or compatible locking mechanism.
The docs1 say: "On Linux and OSX, a lock has the same semantics..." and later "Lock is not yet implemented on other operating systems, and calling it will return an error.".
Even though windows are not mentioned anywhere, I think they are supported, but I want to be sure. Can you please clarify this and/or fix the docs?
If you prefer me to do a pull request changing only the docs, please let me know.
The text was updated successfully, but these errors were encountered: