[OpenAFS-devel] afs and byte-range locking ideas

[Derek Atkins]

Harald Barth <haba@pdc.kth.se> writes:

> > Ahh, that's what you mean.  Yes, this should be supported.  All that
> > has to happen is that client 1 requests a lock (any type of local
> > lock, byte-range or otherwise).  The client1 CM requests a file lock
> > from the server; if the lock is granted, then the CM provides the lock
> > to the requesting application.  When client 2 comes along, the server
> > (hopefully) wont let it lock the file (because the file is locked by
> > client 1).
> 
> I suppose you talk about the windows AFS client which is some kind of
> loopback mount + translator. Does the lock make it to the CM (Cache
> Manager) at all? Does the lock make it to the Server? Is the
> information passed to the second client? Sorry, I do not have the
> answers, but I can help ask the questions :-)

No, I'm talking about a theoretical new-feature to AFS.  I have no idea
how the windows client works or interacts with itself.

> Harald.

-derek

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord@MIT.EDU                        PGP key available