Re: File::NFSLock owner identification?

Greetings, Sleepyjay

I think it might be worth noting, that it would probably be more advantageous if you were to share what OS the server(s) are running. Things have changed over the years in NFS, and not equally among all OS's. Perhaps more importantly; the module ( File::NFSLock ) you refer to is actually quite old. I know for a fact, that NFS has changed dramatically since 2003. This may well explain the unusual behavior you're experiencing.

Best wishes.

--Chris

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

Comment on Re: File::NFSLock owner identification?

Replies are listed 'Best First'.
Re^2: File::NFSLock owner identification? by Anonymous Monk on Dec 06, 2013 at 03:39 UTC
This may well explain the unusual behavior you're experiencing. Unlikely, the fundamentals of NFS haven't changed	[reply]
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.	[reply]
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
Re^6: File::NFSLock owner identification? (vague) by Anonymous Monk on Dec 06, 2013 at 08:44 UTC