in reply to Re: File::NFSLock owner identification?
in thread File::NFSLock owner identification?

This may well explain the unusual behavior you're experiencing.

Unlikely, the fundamentals of NFS haven't changed

  • Comment on Re^2: File::NFSLock owner identification?

Replies are listed 'Best First'.
Re^3: File::NFSLock owner identification?
by taint (Chaplain) on Dec 06, 2013 at 03:44 UTC
    They have, in fact. Quite a bit, since 2003. NSF4, in fact didn't even exist in 2003.

    The locking mechanism, has also been modified, in both *BSD, and Linux. I am aware of this, as I'm subscribed to the development lists on both.

    --Chris

    Hey. I'm not completely useless. I can be used as a bad example.
    

      ...

      How is that relevant to what File::NFSLock does? Have you ever read the source of File::NFSLock?

      ...

      Being subscribed to a list doesn't mean you know what you're talking about

        "Being subscribed to a list doesn't mean you know what you're talking about"

        It means that I do know that several changes have been made to NFS. Which I can be fairly sure should have an impact on anything that wishes to utilize it.

        I think it's also fair to say; contrary to your input, I am attempting to deduce a path that possibly provides a solution.

        --Chris

        Hey. I'm not completely useless. I can be used as a bad example.