in reply to Re^3: locking over the network (NFSLock)
in thread locking over the network

The man page is quite clear what it does. Did you read it? You only have to read the first paragraph.
Yes, I *did* read it, and it says that this class applies only to locking over NFS (which is not a big surprise, considering the name of the class). That's why I said this class might be nice, but doesn't help me much, because it would require that the file to be locked is accessed via NFS. Or did I misunderstand something in the documentation?

-- 
Ronald Fischer <ynnor@mm.st>

Replies are listed 'Best First'.
Re^5: locking over the network (NFSLock)
by tye (Sage) on Feb 02, 2011 at 14:05 UTC

    Then I guess you need more practice reading. I don't see the word "only" in the description and what is clearly described in the first paragraph is precisely the approach offered elsewhere in this thread as a generic approach known to work over NFS but not "only NFS": "creating a random local file, hard linking a common file to the local file, and then checking the nlink status".

    The module Name is even documented as "File::NFSLock - perl module to do NFS (or not) locking" where, just to be clear, "or not" indicates that NFS is not required.

    - tye        

[reply]
      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.
      -- 
      Ronald Fischer <ynnor@mm.st>
[reply]
[d/l]
        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.

        --DrWhy

        "If God had meant for us to think for ourselves he would have given us brains. Oh, wait..."

[reply]

In Section Seekers of Perl Wisdom