Lars Schimmer wrote:
> Hi!
>
> Just studied the release notes to the 1.4 release.
> There is written:
> Byte-range locking as described in cm_vnodeops.c has been implemented.
>
> Does that mean, we can now safely edit MS Office Files IN AFS Space
> while all servers/clients are 1.4 versions?
> *h
Christian Fischer wrote:
> I got it runing, after I open a doc file in word as a second user, it
> locks the file for both of us.
> suggestions?
Christian:
I'm not sure what your issue is but if you wish me to continue working
on this I will need a faster turn around time between my replies and
Jeffrey Altman wrote:
Christian Fischer wrote:
Jeffrey Altman wrote:
What does afsd_init.log report?
here the log..
8/31/2005 2:37:58 PM: cm_GetRootCellName code 0, cm_freelanceEnabled= 1, rcn=
ethz.ch
8/31/2005 2:37:58 PM: Mountpoint[0] = abled= 1, rcn= ethz.ch
#abled= 1, rcn= ethz
Christian Fischer wrote:
> Jeffrey Altman wrote:
>
>> What does afsd_init.log report?
>
>
> here the log..
> 8/31/2005 2:37:58 PM: cm_GetRootCellName code 0, cm_freelanceEnabled= 1, rcn=
> ethz.ch
> 8/31/2005 2:37:58 PM: Mountpoint[0] = abled= 1, rcn= ethz.ch
> #abled= 1, rcn= ethz.ch
> :root
Jeffrey Altman wrote:
What does afsd_init.log report?
here the log..
11:54:33 AM: Create log file
11:54:33 AM: Created log file
PATH=C:\Perl\bin\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program
Files\OpenAFS\Common;C:\Program Files\OpenAFS\Client\Program
8/30/2005 11:54:33 A
Jeffrey Altman wrote:
If you are not familiar with how to debug OpenAFS for Windows,
please read afs-install-notes.txt
I can run the afs service, when I disable the freelance-mode..
I will send further information (logs..) next week.
cheers christian
__
Christian Fischer wrote:
> Jeffrey,
> I can run the setup, but the service can't be started successfully..
> I tried it on an xp sp1 machine..
>
> suggestions?
> cheers
What does afsd_init.log report?
If you are not familiar with how to debug OpenAFS for Windows,
please read afs-install-notes.tx
Jeffrey,
I can run the setup, but the service can't be started successfully..
I tried it on an xp sp1 machine..
suggestions?
cheers
Jeffrey Altman wrote:
No. Byte range locking is not in the 1.4 release.
Byte range locking exists on the CVS HEAD and will be released
in a future 1.4 release
t; To: Lars Schimmer
> Cc: openafs-info@openafs.org
> Subject: Re: [OpenAFS] ByteRangeLocking in 1.4RC2
>
> No. Byte range locking is not in the 1.4 release.
> Byte range locking exists on the CVS HEAD and will be released
> in a future 1.4 release once it is stable.
>
>
No. Byte range locking is not in the 1.4 release.
Byte range locking exists on the CVS HEAD and will be released
in a future 1.4 release once it is stable.
Apparently the CVS HEAD version of the afs-changes file was
published instead of the 1.4 version.
The correct version is available at
/af
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
Just studied the release notes to the 1.4 release.
There is written:
Byte-range locking as described in cm_vnodeops.c has been implemented.
Does that mean, we can now safely edit MS Office Files IN AFS Space
while all servers/clients are 1.4 vers
11 matches
Mail list logo
