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.24 openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.13.2.26 *** openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.13.2.24 Mon Apr 4 07:51:53 2005 --- openafs/doc/txt/winnotes/afs-changes-since-1.2.txt Wed Apr 27 11:28:49 2005 *************** *** 1,3 **** --- 1,57 ---- + Since 1.3.81: + * Fix a race condition in cm_EndCallbackGrantingCall() that + could leave 'nrevp' pointing to freed memory. In the process, + optimize the processing to ensure that the applications monitoring + the status of the stat cache entry are only notified at most + once. + + * Conditionalize access to the Explorer Shell AFS->Mount Point + ->Remove menu item. Disable the item if the selected item(s) + are not mount points. + + * Activate AFS RPC (RX) Free Packet Queues stored in Thread + Local Storage. This eliminates thread contention on the + global RX free packet queue. This should improve performance + on multi-CPU systems. + + * Fix the IP address filtering code to properly load/unload + the IPHelper DLL so that Windows XP/2003 and beyond systems + do not have to manually probe the registry. + + * CleanupACLEnt() was not being called consistently with + the cm_scache_t object referred to by the back pointer + mutex locked. This could in very rare conditions lead to + an invalid memory access. + + * Added a script command to the msi installer "afs_replace" + which can be used to replace one version of OpenAFS with + another without requiring an uninstall and reinstall if + the installed msi is no longer in its original location. + + * Apparently the problem with multi-domain forests with cross- + realm trusts to non-Windows realms was not entirely solved. + The authentication to the AFS SMB service failed because + the wrong name was being used. Using ASU as an example, + the authentication was being performed with the name + "QAAD\user" (an account in the forest root) and not + "user@ASU.EDU (the MIT Kerberos principal used to login with) + + The solution was to add an additional dependency on KFW + in order or to be able to easily obtain the client principal + name stored in the MSLSA ccache TGT. This information is + used in two locations: + + - the pioctl() function + + - a new WinLogon Event Handler for the "logon" event. + + The pioctl function will now be able to use the correct + name when calling WNetAddConnection2() and the "logon" + event handler will now be able to call WNetAddConnection2(). + The hope is that the "logon" event handler will be called + before the profile is loaded but I have not guarrantee + that will happen. + Since 1.3.80: * Fixed a locking error in cm_TryBulkStat() which had the potential of deadlocking the system for the length of time Index: openafs/doc/txt/winnotes/afs-install-notes.txt diff -c openafs/doc/txt/winnotes/afs-install-notes.txt:1.11.2.16 openafs/doc/txt/winnotes/afs-install-notes.txt:1.11.2.18 *** openafs/doc/txt/winnotes/afs-install-notes.txt:1.11.2.16 Mon Apr 4 07:51:53 2005 --- openafs/doc/txt/winnotes/afs-install-notes.txt Wed Apr 27 11:28:49 2005 *************** *** 1,4 **** ! OpenAFS for Windows 1.3.81 Installation Notes --------------------------------------------- The OpenAFS for Windows product was very poorly maintained throughout the --- 1,4 ---- ! OpenAFS for Windows 1.3.82 Installation Notes --------------------------------------------- The OpenAFS for Windows product was very poorly maintained throughout the *************** *** 555,560 **** --- 555,561 ---- Windows domain which are centrally located (e.g., in a computing lab.) See registry.txt for details on the "Server Preferences" keys. + 39. As of 1.3.81, timestamps on file stored in AFS are reported to Windows in UTC all year round. Previously, in locales with daylight savings time, the time reported by AFS to Windows when DST is active *************** *** 574,579 **** --- 575,589 ---- timestamp from the Windows explorer. During DST, these two times will no longer agree even though they are in fact describing the same time. + + 40. If the installer refuses to install and complains about an RPC + configuration error, check to ensure that the following registry + entries are present and that they refer to the dll "rpcrt4.dll": + + HKLM "SOFTWARE\Microsoft\RPC\ClientProtocols" "ncacn_np" + HKLM "SOFTWARE\Microsoft\RPC\ClientProtocols" "ncacn_ip_tcp" + HKLM "SOFTWARE\Microsoft\RPC\ClientProtocols" "ncadg_ip_udp" + ------------------------------------------------------------------------ Reporting Bugs: Index: openafs/doc/txt/winnotes/afs-issues.txt diff -c openafs/doc/txt/winnotes/afs-issues.txt:1.8.2.12 openafs/doc/txt/winnotes/afs-issues.txt:1.8.2.13 *** openafs/doc/txt/winnotes/afs-issues.txt:1.8.2.12 Sat Apr 2 04:07:17 2005 --- openafs/doc/txt/winnotes/afs-issues.txt Tue Apr 19 01:12:19 2005 *************** *** 172,178 **** 10. Documentation Documentation Documentation 11. Large File support (> 2GB) in SMB/CIFS client 12. Integrate KFW installation into the NSIS and MSI installers ! 13. Add support for record locking to AFS (requires changes to the servers) 14. Unicode enable the SMB/CIFS server. OEM Code Pages: 1. prevent the use of interoperable file names 2. force the use of paths no longer than 256 characters --- 172,178 ---- 10. Documentation Documentation Documentation 11. Large File support (> 2GB) in SMB/CIFS client 12. Integrate KFW installation into the NSIS and MSI installers ! 13. Add support for byte range locking to AFS (requires changes to the servers) 14. Unicode enable the SMB/CIFS server. OEM Code Pages: 1. prevent the use of interoperable file names 2. force the use of paths no longer than 256 characters