Index: openafs/doc/man-pages/pod1/fs_setacl.pod
diff -c openafs/doc/man-pages/pod1/fs_setacl.pod:1.4 openafs/doc/man-pages/pod1/fs_setacl.pod:1.4.2.1
*** openafs/doc/man-pages/pod1/fs_setacl.pod:1.4 Wed Mar 1 00:02:30 2006
--- openafs/doc/man-pages/pod1/fs_setacl.pod Mon Jan 29 14:33:40 2007
***************
*** 263,270 ****
=head1 PRIVILEGE REQUIRED
The issuer must have the C (administer) permission on the directory's
! ACL; the directory's owner and the members of the system:administrators
! group have the right implicitly, even if it does not appear on the ACL.
=head1 SEE ALSO
--- 263,278 ----
=head1 PRIVILEGE REQUIRED
The issuer must have the C (administer) permission on the directory's
! ACL, a member of the system:administrators group, or, as a special case,
! must be the UID owner of the top-level directory of the volume containing
! this directory. The last provision allows the UID owner of a volume to
! repair accidental ACL errors without requiring intervention by a member of
! system:administrators.
!
! Earlier versions of OpenAFS also extended implicit administer permission
! to the owner of any directory. In current versions of OpenAFS, only the
! owner of the top-level directory of the volume has this special
! permission.
=head1 SEE ALSO
Index: openafs/doc/txt/winnotes/afs-changes-since-1.2.txt
diff -c openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.72.2.19 openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.72.2.22
*** openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.72.2.19 Mon Jan 15 15:54:32 2007
--- openafs/doc/txt/winnotes/afs-changes-since-1.2.txt Tue Feb 13 13:33:27 2007
***************
*** 1,3 ****
--- 1,109 ----
+ Since 1.5.14
+
+ * A reference leak was discovered in the mountpoint traversal
+ functionality which resulted in cm_volume_t objects not becoming
+ eligible for re-use. This will trigger a panic condition when
+ more than the maximum number of volumes is accessed.
+
+ * Fixed the success test for the "fs memdump" operation. Success
+ is now reported as such. Added cm_volume_t object information
+ to the dump file.
+
+ * A data corruption error has been fixed. Write requests
+ queued for background processing were not retried upon failure.
+ This leads to inconsistencies between the contents of the file
+ in the local cache and the contents of the file on the file
+ server.
+
+ The implemented fix is to re-queue any request that has failed
+ due to timeout, volume busy, volume offline, server busy, or
+ server offline. Requests are not processed while all servers
+ for a volume are inaccessible. When servers become accessible
+ the background request will be retried.
+
+ In addition, if a background write fails, do not mark the buffers
+ as clean. Failure to preserve the dirty flag prevents the buffers
+ from being written to the file server in the future.
+
+ This fix does not address the possibility that the credentials
+ necessary to perform a write request might expire between the
+ time the request is queued and when the request can be processed
+ due to server accessibility.
+
+ * The Freelance volume does not support per user ACLs. The
+ cm_HaveAccessRights function did not handle this special case.
+ Requests for privileges greater than read|lookup would result
+ in afsd_service.exe entering an infinite loop. ISOBuster is
+ known to cause this behavior.
+
+ * When deleting files, the SMB Server would attempt to obtain
+ the access permissions for the parent directory instead of
+ for the file itself. This would result in an incorrect
+ assessment of whether or not the file can be deleted.
+
+ * The Network Identity Manager AFS plug-in has had its string
+ tables updated for consistency with the language used by NIM.
+ All credentials are referred to as credentials instead of tokens.
+ Drop-down combo boxes now in fact drop down.
+
+ * The AFS Salvager was not properly being built on Windows.
+ This is relevant only if the AFS servers are in use.
+
+ * The default signal handlers for the AFS servers incorrectly
+ processed SIGQUIT. Instead of stopping the server, an
+ exception was raised.
+
+ * Fix another volume refcount leak. This one was triggered by
+ an inability to contact the vlservers in order to update the
+ file server list.
+
+ * Fix checklist control used by the drive mappings tabs in
+ afscreds.exe and afs_control.exe.
+
+ * Improve output of "fs memdump" related to buffer management.
+
+ * Fix refcount leak of cm_buf_t objects when prefetching buffers
+ already in the process of being fetched.
+
+ * Improve cache performance by computing the buffer hash table
+ size based upon the number of buffers so that the average
+ number of entries in a bucket is seven.
+
+ * Improve cache performance of read/write data by locally
+ updating the dataVersion of all buffers associated with the
+ file on each StoreData or StoreStatus operation provided that
+ the dataVersion was incremented by one and the dataVersion of
+ the buffer matched the original dataVersion of the cached
+ status information for the file.
+
+ * When the status for a file/directory cannot be obtained
+ during a InlineBulkStat RPC, the EACCESS error state is
+ recorded within the stat cache object. If we later call
+ cm_AccessCheck() we should not attempt a new FetchStatus
+ call, simply return the allAccess rights since we know that
+ the FetchStatus will fail. When the parent directory is
+ accessed with better rights or when the ACLs change the
+ next InlineBulkStatus will clear the flag.
+
+ * When recycling cm_scache_t objects, make sure that we
+ clear all of the previous fields. It is no longer the
+ case that we can assume that the stat cache object is being
+ obtained only after a successful FetchStatus call.
+ InlineBulkStatus will allocate stat cache objects for which
+ the no status information is available.
+
+ * When a file is being opened with the OPEN_ALWAYS disposition,
+ do not require write permissions when the file already exists
+ unless of course the file is being opened requesting write
+ access.
+
+ * When a file has been opened for read-only access, if the
+ application requests an exclusive lock, obtain a read-lock
+ instead of a write-lock. The purpose of the exclusive lock
+ in this situation is to prevent changes to the file and the
+ full file read lock will provide this guarrantee.
+
+
Since 1.5.13
* Enforce Unix Mode Write bit to prevent file deletion of read only
Index: openafs/doc/txt/winnotes/afs-integration.txt
diff -c openafs/doc/txt/winnotes/afs-integration.txt:1.4 openafs/doc/txt/winnotes/afs-integration.txt:1.4.2.1
*** openafs/doc/txt/winnotes/afs-integration.txt:1.4 Tue Feb 14 08:25:10 2006
--- openafs/doc/txt/winnotes/afs-integration.txt Tue Feb 13 13:33:27 2007
***************
*** 1,4 ****
! ...(This document is current as of release 1.5.000)
How to determine if OpenAFS is installed?
--- 1,4 ----
! ...(This document is current as of release 1.5.15)
How to determine if OpenAFS is installed?
Index: openafs/doc/txt/winnotes/afs-issues.txt
diff -c openafs/doc/txt/winnotes/afs-issues.txt:1.28.2.3 openafs/doc/txt/winnotes/afs-issues.txt:1.28.2.4
*** openafs/doc/txt/winnotes/afs-issues.txt:1.28.2.3 Mon Dec 18 18:40:25 2006
--- openafs/doc/txt/winnotes/afs-issues.txt Tue Feb 13 13:33:27 2007
***************
*** 1,4 ****
! This file is a rough list of known issues with the 1.5.13 release of OpenAFS
on Windows. This list is not complete. There are probably other issues which
can be found in the RT database or on the mailing list.
--- 1,4 ----
! This file is a rough list of known issues with the 1.5.15 release of OpenAFS
on Windows. This list is not complete. There are probably other issues which
can be found in the RT database or on the mailing list.