From: Jeffrey Altman <jaltman@secure-endpoints.com>
Date: Sun, 28 May 2006 14:58:01 +0000 (+0000)
Subject: STABLE14-windows-notes-20060527
X-Git-Tag: openafs-stable-1_4_1c~8
X-Git-Url: https://git.michaelhowe.org/gitweb/?a=commitdiff_plain;h=ffa9ce0c7ee8d9ea7b1ff6d0c0609b40227f9e7d;p=packages%2Fo%2Fopenafs.git

STABLE14-windows-notes-20060527


update changelog
---

diff --git a/doc/txt/winnotes/afs-changes-since-1.2.txt b/doc/txt/winnotes/afs-changes-since-1.2.txt
index 03e0549d2..aa6bffe04 100644
--- a/doc/txt/winnotes/afs-changes-since-1.2.txt
+++ b/doc/txt/winnotes/afs-changes-since-1.2.txt
@@ -1,3 +1,31 @@
+Since 1.4.1b: 
+ 
+ * Fix aklog AFSID lookup to use not send the realm
+   name when the realm is the local realm for the 
+   cell.  The PT Server doesn't strip the realm 
+   name when it is the local realm.
+
+ * Treat "\\afs\*." as an alias for "\\afs\all" 
+
+ * Dynamically adjust the priority of server threads
+   based upon the age of the CIFS request that is 
+   being processed.  The priority is bumped one level
+   for every 15 seconds of processing time.
+
+ * smb_SendPacket cannot release a vcp since it doesn't
+   own the reference.
+
+ * The original openafs contribution mis-used the 
+   cm_GetCallback function.  This function should only
+   be called as a side effect of a call to
+   cm_SyncOp(CM_SCACHESYNC_NEEDCALLBACK).  The way it
+   was being called results in a FetchStatus RPC being 
+   performed even when the client already has a valid
+   callback and does so in a manner that destroys the
+   synchronization of the threads that are calling 
+   cm_SyncOp.  If nothing else this results in a 
+   significant performance penalty.
+
 Since 1.4.1a: 1.4.1b (16 May 2006)
 
  * More changes to cleanup of smb_vc_t objects in