On Sun, Apr 04, 2004 at 05:00:55PM -0400, Alexis Rosen wrote: > On Fri, Apr 02, 2004 at 04:13:05PM -0800, Justin Mason said: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > > > Alexis Rosen writes: > > >Hey, guys. I'm just following up because I'm curious about the final > > >disposition of the nfslock code. Did you add a function to correspond to > > >nfsunlock? I hope the rest of my comments were helpful. > > > > Actually, we haven't :( It dropped off my radar, unfortunately. > > > > I'm thinking we should take a look at that before 3.0.0 release, and > > You *really* should. > > > probably we should also add a *non*-NFS-safe locking function too for > > hosts where NFS is not involved -- as I think we could cut down > > lock overhead quite a lot that way. > > Absoultely. NFSlock is at least an order of magnitude more expensive than > using OS-supported locking schemes.
And, for that matter, at this point most (all?) NFS implementations implement locking anyway. It'd be fairly easy to add this to the tests. -- Kelsey Cummings - [EMAIL PROTECTED] sonic.net, inc. System Administrator 2260 Apollo Way 707.522.1000 (Voice) Santa Rosa, CA 95407 707.547.2199 (Fax) http://www.sonic.net/ Fingerprint = D5F9 667F 5D32 7347 0B79 8DB7 2B42 86B6 4E2C 3896
