Mark D. Baushke wrote: > some odd race conditions with more than > one user trying to create write locks in the same directory at the same > time both believing they have obtained their exclusive lock.
IIRC, this one had to do with clients caching the state of a directory. Something like both clients would query the lock directory's existence and if they had cached that it didn't exist, both would return a successful status code to a program before they get the failure response from the NFS server. I've fixed that at least once (for running sanity.sh between two hosts) by setting the dir-cache-time for my NFS client to 0. On my Linux client the options are acdirmin=0,acdirmax=0 and can be set separately for each mount-point. Regards, Derek -- Derek R. Price CVS Solutions Architect Ximbiot <http://ximbiot.com> v: +1 717.579.6168 f: +1 717.234.3125 <mailto:[EMAIL PROTECTED]> _______________________________________________ Bug-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/bug-cvs
