[3305] in Release_7.7_team
Re: Athena Disconnected Operation White Paper Draft 2.
daemon@ATHENA.MIT.EDU (Thomas Bushnell, BSG)
Sat May 25 13:36:17 2002
To: dryfoo@mit.edu
Cc: lcs@mit.edu, Bill Cattey <wdc@mit.edu>, source-developers@mit.edu,
release-team@mit.edu
From: tb@becket.net (Thomas Bushnell, BSG)
Date: 25 May 2002 10:38:11 -0700
In-Reply-To: <200205250638.CAA06112@thelonious.mit.edu>
Message-ID: <87off4b01o.fsf@becket.becket.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
dryfoo@MIT.EDU writes:
> We have one advantage with AFS, I think: that when the user is
> disconnected, AFS has "lock" among its permission types. So if the user
> is off-line somewhere modifying his own files, his own locker at least
> could be locked to all other users who might have modification rights to
> any subdirs in it.
I'm not at all sure what "the user" is here.
Is it "anytime I have a locker mounted rw, and I go offline, the
locker becomes locked"? That can't be right, because I might have rw
access to, say, the sipb locker.
