On Tue, 7 Jan 2003, Charles Clancy wrote:
> Derrick's page:
>
> http://www-2.cs.cmu.edu/afs/andrew.cmu.edu/usr/shadow/www/afs/afs-with-kerberos.html
It's probably out of date. The canonical URL, by the way, is
http://www.dementia.org/~shadow/afs/afs-with-kerberos.html
but thanks to the magic of
> How do I realize the key synchronization? Sorry about this maybe simple
> questions but its realy hard to find any/a complete how to.
Use asetkey.
The README from Ken Hornstein's AFS migration toolkit does a pretty good
job. I have a personal copy:
http://ismene.csl.uiuc.edu/afs-mig/d
> >Derek Atkins wrote:
> > Synchronization is based on file open/close, not read/write. If
> > client 1 close()es the file before client 2 open()s it, then it will
> > see the new one. Otherwise it will see the old one.
>
> Client #1 close()es file XYZ and a few microseconds later client #2
>
On Sunday 05 January 2003 22:39, Charles Clancy wrote:
> On Sun, 5 Jan 2003, Thomas Grieder wrote:
> > On Sunday 05 January 2003 18:53, Charles Clancy wrote:
> > > What's the output of "aklog -d" in each case?
> >
> > Authenticating to cell afs.cell (server server.network.local).
> > We've deduced
We have 15 or so openAFS clients (mix of linux and windows) mounting an
AFS drive over the internet. An application writes a file to the openAFS
server from client #1 and another application begins to read that same
file on client #2 microseconds later.
What version of the file will client #2 read?
On Monday 06 January 2003 07:14, Norihiko Sugita wrote:
> I have tried to install OpenAFS 1.2.8a into my two Win XP SP1 PCs, but the
> installer didn't work well. It stopped with error code immediately. Does
> OpenAFS 1.2.8a support Win XP SP1? Did someone else work OpenAFS on WinXP
> SP1 well?
I have tried to install OpenAFS 1.2.8a into my two Win XP SP1 PCs, but the
installer didn't work well. It stopped with error code immediately. Does
OpenAFS 1.2.8a support Win XP SP1? Did someone else work OpenAFS on WinXP
SP1 well?
Norihiko
__
Synchronization is based on file open/close, not read/write. If
client 1 close()es the file before client 2 open()s it, then it will
see the new one. Otherwise it will see the old one.
-derek
"Jayme Cox" <[EMAIL PROTECTED]> writes:
> I have a question about file locking:
>
> We have 15 or so
I have a question about file locking:
We have 15 or so openAFS clients (mix of linux and windows) mounting an
AFS drive over the internet. An application writes a file to the openAFS
server from client #1 and another application begins to read that same
file on client #2 microseconds later.
What
