Re^3: File::NFSLock owner identification?

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.

Comment on Re^3: File::NFSLock owner identification?

Replies are listed 'Best First'.
Re^4: File::NFSLock owner identification? by Anonymous Monk on Dec 06, 2013 at 04:14 UTC
... 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	[reply]
Re^5: File::NFSLock owner identification? by taint (Chaplain) on Dec 06, 2013 at 05:35 UTC
"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.	[reply]
Re^6: File::NFSLock owner identification? (vague) by Anonymous Monk on Dec 06, 2013 at 08:44 UTC
... I think it's also fair to say;... Sure , you start with OPs vague description of code problem, in a module you're vaguely familiar with, follow with some vague idea about "NFS changes" ... and in no time you're on the path to ... vagueville	[reply]