Index: openafs/doc/txt/winnotes/afs-changes-since-1.2.txt
diff -c openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.13.2.53 openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.13.2.56
*** openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.13.2.53	Tue Jan 10 23:49:19 2006
--- openafs/doc/txt/winnotes/afs-changes-since-1.2.txt	Tue Jan 24 12:19:09 2006
***************
*** 1,3 ****
--- 1,28 ----
+ Since 1.4.1 rc4: 1.4.1 rc5 released (25 Jan 2006)
+ 				    
+  * Re-enabled LogoffTokenTransfer and LogoffTokenTransferTimeout
+    registry settings.  Default is ON and 120 seconds.  If set to
+    OFF, tokens will not be destroyed.
+ 
+  * Fixed a number of race conditions and reference count 
+    problems associated with global queues.
+ 
+  * Added a method to detect abandonded smb virtual circuits
+    so their associated file handles, locks, user tokens,
+    and smb session resources can be released.
+ 
+  * Added a mechanism to allow user tokens to be preserved 
+    during integrated login and be freed after logoff.
+ 
+  * Check access permissions to the file before the file is 
+    truncated.
+ 
+  * More improvements to the handling of SMB Virtual Circuits
+    when SMB sessions are closed.
+ 
+  * Correct a race condition introduced in rc4 that could result
+    in a crash of afsd_service.exe.
+ 
  Since 1.4.1 rc3: 1.4.1 rc4 released (11 Jan 2006)
  
   * Properly handle pre-mature SMB session closures.
***************
*** 7,16 ****
   * smb_username_t and smb_user_t objects are now properly reference
     counted and freed as appropriate.
  
!  * disable to use of AFS file locks.  Byte range locking is still
     implemented but all locks are managed locally.  This prevents
     multiple processes from editing the same file on the same 
!    machine but it does prevent multiple processes on separate 
     machines from modifying the file.
  
  Since 1.4.1 rc2: 1.4.1 RC3 released (4 Jan 2006)
--- 32,41 ----
   * smb_username_t and smb_user_t objects are now properly reference
     counted and freed as appropriate.
  
!  * disable the use of AFS file locks.  Byte range locking is still
     implemented but all locks are managed locally.  This prevents
     multiple processes from editing the same file on the same 
!    machine but it does not prevent multiple processes on separate 
     machines from modifying the file.
  
  Since 1.4.1 rc2: 1.4.1 RC3 released (4 Jan 2006)