This is a multi-part message in MIME format.
--------------060701030100060703050305
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
I understand, but probably most files are used as templates so that
wouldnt be a problem in this case.
What still puzzles me is why this doesnt work on those pc's with such a
standard application as MS Word. (is there a more standard application
in the pc world ?)
Could it be a legacy from the novell client ? Never any problems when
they used that. I also noticed that some are running XP home edition,
does that make any difference ?
There must be something causing this. Maybe somebody else seen the same
problem ?
Jeffrey Altman wrote:
> If you set that value to 0, then winword will start but two users on
> different machines will be able to open the file at the same time.
> Doing so will corrupt the file if both decide to write to it.
>> Jeffrey Altman
>>> Hans Melgers wrote:
>>> Thanks Jeffrey. The older version was in the early stages, we found it
>> also happens with 1.5.25. On some pc's this happens, on others it doesnt.
>>>> So the problem is in winword trying to obtain a lock indefinitely.
>> What do you recommend ? is there any (registry) setting that does this ?
>>>> Would this be a solution ? I mean, would winword accept and act on
>> changing this setting to 0 ? :
>>>> If the CIFS-AFS server is unable to renew the AFS file server locks,
>> then it will invalidate the associated file handles. This is the same
>> behavior that an application will experience if it was using a Windows
>> File Share and the connection was broken. Invalidating the file
>> handles prevents subsequent data corruption from taking place.
>> If you wish to disable the acquisition of locks from the file server,
>> this can be performed using the EnableServerLocks registry value.
>>>> Value: EnableServerLocks
>> Type: DWORD {0, 1, 2}
>> Default: 1
>>>> Determines whether or not the AFS file server is contacted for
>>>> 0: never obtain server locks
>>>> 1: obtain server locks unless the file server says not to
>>>> 2: always obtain server locks
>>>> _______________________________________________
> OpenAFS-info mailing list
>OpenAFS-info@openafs.org>https://lists.openafs.org/mailman/listinfo/openafs-info>
--------------060701030100060703050305
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
I understand, but probably most files are used as templates so that
wouldnt be a problem in this case.<br>
<br>
What still puzzles me is why this doesnt work on those pc's with such a
standard application as MS Word. (is there a more standard application
in the pc world ?)<br>
Could it be a legacy from the novell client ? Never any problems when
they used that. I also noticed that some are running&nbsp; XP home edition,
does that make any difference ?<br>
There must be something causing this. Maybe somebody else seen the same
problem ? <br>
<br>
Jeffrey Altman wrote:
<blockquote cite="mid:474C8D0C.50500@secure-endpoints.com" type="cite">
<pre wrap="">If you set that value to 0, then winword will start but two users on
different machines will be able to open the file at the same time.
Doing so will corrupt the file if both decide to write to it.
Jeffrey Altman
Hans Melgers wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
Thanks Jeffrey. The older version was in the early stages, we found it
also happens with 1.5.25. On some pc's this happens, on others it doesnt.
So the problem is in winword trying to obtain a lock indefinitely.
What do you recommend ? is there any (registry) setting that does this ?
Would this be a solution ? I mean, would winword accept and act on
changing this setting to 0 ? :
If the CIFS-AFS server is unable to renew the AFS file server locks,
then it will invalidate the associated file handles. This is the same
behavior that an application will experience if it was using a Windows
File Share and the connection was broken. Invalidating the file
handles prevents subsequent data corruption from taking place.
If you wish to disable the acquisition of locks from the file server,
this can be performed using the EnableServerLocks registry value.
Value: EnableServerLocks
Type: DWORD {0, 1, 2}
Default: 1
Determines whether or not the AFS file server is contacted for
0: never obtain server locks
1: obtain server locks unless the file server says not to
2: always obtain server locks
</pre>
</blockquote>
<pre wrap=""><!---->
_______________________________________________
OpenAFS-info mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenAFS-info@openafs.org">OpenAFS-info@openafs.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openafs.org/mailman/listinfo/openafs-info">https://lists.openafs.org/mailman/listinfo/openafs-info</a>
</pre>
</blockquote>
</body>
</html>
--------------060701030100060703050305--