[3341] in Release_7.7_team
Re: Athena Disconnected Operation White Paper Draft 2.
daemon@ATHENA.MIT.EDU (dryfoo@MIT.EDU)
Tue Jun 11 12:53:43 2002
From: dryfoo@MIT.EDU
Message-Id: <200206111653.MAA13978@thelonious.mit.edu>
To: Derek Atkins <warlord@MIT.EDU>
cc: Jonathon Weiss <jweiss@MIT.EDU>, lcs@MIT.EDU, Bill Cattey <wdc@MIT.EDU>,
source-developers@MIT.EDU, release-team@MIT.EDU
In-Reply-To: Your message of "11 Jun 2002 12:48:44 EDT."
<sjmfzztdamr.fsf@inky.mit.edu>
Date: Tue, 11 Jun 2002 12:53:40 -0400
} Jonathon Weiss <jweiss@MIT.EDU> writes:
}
} > dryfoo> We have one advantage with AFS, I think: that when the user is
} > dryfoo> disconnected, AFS has "lock" among its permission types. So if the
| user
} > dryfoo> is off-line somewhere modifying his own files, his own locker at le
| ast
} > dryfoo> could be locked to all other users who might have modification righ
| ts to
} > dryfoo> any subdirs in it.
} >
} > 'lock' doesn't mean what you think it does here. It is intended for
} > temporary locking of files to prevent multiple clients from changing
} > the same file simultaneously. I'm pretty sure that a client's lock
} > will be lost if the client falls off the net.
}
} AFS locks are also advisory locks, nothing more. Different clients
} can still write to locked files. The locks only help with
} coordinating applications.
}
} > Jonathon
}
} -derek
Okay. Then don't do that.
