From d360b6486e1e9edc9360880b279facf8474df580 Mon Sep 17 00:00:00 2001 From: Jeffrey Altman Date: Sat, 10 Feb 2007 15:28:15 +0000 Subject: [PATCH] DEVEL15-windows-release-notes-20070210 updates for 1.5.15. document changes in locking behavior and lack of support for .hlp files on Vista --- .../en_US/html/ReleaseNotes/logo.htm | 2 +- .../html/ReleaseNotes/relnotes-frames.htm | 2 +- .../en_US/html/ReleaseNotes/relnotes.htm | 48 +++++++++++++------ .../en_US/html/ReleaseNotes/toc.htm | 2 +- .../Documentation/en_US/html/index.htm | 2 +- 5 files changed, 38 insertions(+), 18 deletions(-) diff --git a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/logo.htm b/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/logo.htm index 9c8dd2eb5..a59426e76 100644 --- a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/logo.htm +++ b/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/logo.htm @@ -18,7 +18,7 @@ w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} -OpenAFS for Windows 1.5.14 Release Notes +OpenAFS for Windows 1.5.15 Release Notes -OpenAFS for Windows 1.5.14 Release Notes +OpenAFS for Windows 1.5.15 Release Notes
-

OpenAFS for Windows 1.5.14
+

OpenAFS for Windows 1.5.15
Release Notes

The Andrew File System (AFS) is a location-independent @@ -1547,8 +1547,9 @@ use.

lock semantics on top of AFS lock semantics it is important to understand how AFS file locks work.  In Windows there are no special privileges associated with obtaining file locks.  If you can read or execute a file, -then you can obtain a read lock.  If you can write or create a file, then -you can obtain a write lock.  In AFS if you can write to a file, then you +then you can obtain shared and exclusive locks.  In general, a Windows shared +lock equates to an AFS read lock and a Windows exclusive lock equates to an AFS +write lock.  In AFS if you can write to a file, then you can obtain a write lock.  However, in AFS if you can read a file it does not mean that you can obtain a read lock on it.   The ability to obtain read locks is granted only if you have the lock (or ‘k’) privilege.  @@ -1561,28 +1562,41 @@ out of read-only volumes the file server will deny all requests for read and write locks because the contents of the volume cannot be changed by the client.

Since Microsoft Windows applications almost always attempt -to obtain a temporary read lock when accessing files the OpenAFS Client’s +to obtain a temporary exclusive lock when accessing files the OpenAFS Client’s CIFS-AFS gateway implements the following semantics in order to reduce the inconvenience on end users. 

  • If the file is located on a read-only volume and the application requests a - read lock, the CIFS-AFS server will grant the lock request without asking + shared lock, the CIFS-AFS server will grant the lock request without asking the AFS file server.
  • If - the file is located on a read-only volume and the application requests a write - lock, the CIFS-AFS server will refuse the lock request and return a read - only error.
    • + the file is located on a read-only volume and the application opens the + file with write access and requests an exclusive lock, the CIFS-AFS server + will refuse the lock request and return a read only error.
  • If - the file is located on a read-write volume and the application requests a - write lock, the CIFS-AFS server will request a lock from the AFS file + the file is located on a read-only volume and the application opens the + file with only read access and requests an exclusive lock, the CIFS-AFS server + will fulfill the lock request with a read lock.
    • +
  • If + the file is located on a read-write volume and the application requests an + exclusive lock, the CIFS-AFS server will request a write lock from the AFS file server.  If granted by the file server, then the CIFS-AFS server will - grant the lock request.  Otherwise, the request will be denied either - with an access denied or an in use error.
    • + grant the lock request.  + + If the request is denied due to an access denied error and the user has the + lookup, read and lock privileges and the file was opened for read only access, + then the CIFS-AFS server will request a read lock from the file server.  + + If the request is denied due to an access denied error and the user has the + lookup and read privileges but not the lock privilege, then the CIFS-AFS + server will grant the request even though the AFS file server said ‘no’.  + If the user does not have at least those permissions, the CIFS-AFS server + will deny the request.
  • If the file is located on a read-write volume and the application requests a - read lock, the CIFS-AFS server will request a lock from the AFS file + shared lock, the CIFS-AFS server will request a read lock from the AFS file server.  If granted by the file server, then the CIFS-AFS server grants the lock request.  If the request is denied due to an access denied error and the user has the lookup and read privileges but not the @@ -2124,6 +2138,12 @@ the necessary privilege separation, until that time some functions such as the Start and Stop Service features of the AFS System Tray tool and the AFS Control Panel will not work unless they are “Run as Administrator”.

    +

    +The help files provided with OpenAFS are in .HLP format. +Windows Vista does not include a help engine for this format.

    OpenAFS for Windows

    -

    Version 1.5.14

    +

    Version 1.5.15

     

    -- 2.39.5