Re^6: locking over the network (NFSLock)

[rovf]

Maybe I indeed need more practice reading, or at least improve my English. The first paragraph says:

Program based of concept of hard linking of files being atomic across NFS. This concept was mentioned in Mail::Box::Locker (which was originally presented in Mail::Folder::Maildir). Some routine flow is taken from there -- particularly the idea of creating a random local file, hard linking a common file to the local file, and then checking the nlink status. Some ideologies were not complete (uncache mechanism, shared locking) and some coding was even incorrect (wrong stat index). File::NFSLock was written to be light, generic, and fast.

I can read here: "Program based of concept ... being atomic across NFS". I have understood this as being a class which is used to do locking on NFS. Please explain where I misinterpreted this text.

Also, I am curious to know in what respect using NFSLock is better than my original solution. For example, is the code which I posted unreliable? If so, this would certainly be an argument to try NFSLock.

[DrWhy]

The docs of File::NFSLock are not the clearest I've ever read. However, with some background knowledge it's possible to surmise that this module can be used on local filesystems too. The problem with most file locking schemes when used on NFS is that they depend on certain operations which are atomic for local FS's actually being atomic -- but on NFS many of these operations are not atomic. So to introduce the concept by saying it works because something on NFS is atomic, it's a pretty safe assumption that that operation is atomic on local FS's as well and so the locking mechanism will also work there.