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.15 openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.72.2.17 *** openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.72.2.15 Thu Nov 30 01:50:58 2006 --- openafs/doc/txt/winnotes/afs-changes-since-1.2.txt Tue Dec 26 15:31:40 2006 *************** *** 1,3 **** --- 1,49 ---- + Since 1.5.12 + + * When all buffers are in use, periodically sleep the threads + waiting for a buffer to become free while the global buffer + lock is not being held in order to permit those threads that + can free buffers to do so. + + * Power Management improvements. Maintain a global flag that + specifies whether or not the service is in a suspend state. + Do not panic if Netbios() returns NRC_BRIDGE meaning that the + lana is no longer valid. Instead, stop the listener threads + and if all listener threads are stopped, reset the lana_list. + Allow the cm_Daemon() thread to periodically check the state + of the smb listeners. If they are all stopped and the service + is not suspended, attempt to restart them. If there are no valid + lanas, return to the stopped state. + + * CreateX and NTCreateX use cm_CheckNTOpen() to test whether or not + the user is permitted to obtain read or write locks. This function + would obtain the lock and then drop it returning whether or not + the lock could be obtained. If the lock was in fact required, + CreateX/NTCreateX would then obtain it with cm_Lock(). The problem + of course being that this pattern results in three RPCs to the + file server (lock, unlock, lock). This is reduced to one RPC by + implementing cm_CheckNTOpenDone() which frees the allocated byte + range lock from cm_CheckNTOpen() after the cm_Lock() call is + performed. + + * Optimize the SMB FindFirst processing for the case in which there + are no wildcards. If a cm_Lookup succeeds, generate a response + from the stat cache entry we have a callback for. Its cheaper + than walking each buffer of directory data associated with the + directory stat cache entry when we have thousands of directory + entries to search. + + * Increase the SMB Ioctl MaxData size to support larger token sizes + + * Disable autorun of the AFS Server Wizard when the AFS Server is + installed. + + * Add AFS Server service dependencies on tcpip and PNP_TDI + + * Remove the AFS Server Configuration Tool shortcut + + * Add Freelance mode awareness to AFS Server Configuration Tool + Since 1.5.11 * Unlike previous versions of the OS, Vista performs a shutdown on *************** *** 20,26 **** * The old dirty buffer synchronization algorithm had a buf_IncrSyncer thread walking the all buffer list periodically searching for dirty buffers to write to the file server. This had several negative ! results. The alogirithm ate up ever increasing amounts of CPU time even when AFS is idle as the size of the cache increases. Also, buffers were written to the file server in an order based upon the original buffer allocation which has nothing to do with the order --- 66,72 ---- * The old dirty buffer synchronization algorithm had a buf_IncrSyncer thread walking the all buffer list periodically searching for dirty buffers to write to the file server. This had several negative ! results. The algorithm ate up ever increasing amounts of CPU time even when AFS is idle as the size of the cache increases. Also, buffers were written to the file server in an order based upon the original buffer allocation which has nothing to do with the order Index: openafs/doc/txt/winnotes/afs-issues.txt diff -c openafs/doc/txt/winnotes/afs-issues.txt:1.28.2.2 openafs/doc/txt/winnotes/afs-issues.txt:1.28.2.3 *** openafs/doc/txt/winnotes/afs-issues.txt:1.28.2.2 Sun Sep 3 13:03:44 2006 --- openafs/doc/txt/winnotes/afs-issues.txt Mon Dec 18 18:40:25 2006 *************** *** 1,61 **** ! This file is a rough list of known issues with the 1.5.8 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) File/Directory access is not integrated with windows security - (3) SMB LANA list is static. - - (3a) IP address changes cause the service to terminate due to an assertion - in smb_Listener() thread. - - (3b) New IP addresses do not get bound to the SMB server - (3c) Loopback adapter hack: (i) prevents use of AFS Gateway (ii) requires installation of loopback adapter (iii) the list of hack adapters is incomplete (VMWare, MS TV/Video, ...) - (iv) incompatible with Windows 2000 and earlier (9) Convert to IFS!!!!!! - (10) Kerberos 5 integration: - (10f) allow arbitrary cell to realm mappings - (10g) modify UI to allow user to choose whether to authenticate - using Kerberos or AFS - (10h) modify UI to allow user to select an existing principal to - be used to request AFS tokens - (10i) modify UI to display Kerberos 5 ticket info (principal, - ticket lifetimes, etc) - - (11) Default cell is system global just like everything else. Different - users logging in via Integrated Logon or using afscreds.exe cannot - be automatically prompted for different cells - (12) AFS Integrated Logon: - (12b) If using Kerberos, need to figure out a means of passing credentials - into the user space until such time as I finish the new credential - cache service. (12c) If network is not available must store the username and password somewhere until such time as the network starts. - (13) If a drive mapping is "in use", then afscreds cannot be used to Modify - or Delete the Mapping. If a map to "H:" to \afs\cell\foo" with - description "home" is modified to point to \afs\cell\bar, then the - description must be unique. "home" cannot be reused. We need a way - to remove "home" from the submount list. - - [Actually, an end user should not be able to modify the submount list] - (14) No support for Unicode CIFS/SMB data structures. OEM Code Pages prevent the use of interoperable file names; force the use of paths no longer than 256 characters; force share names to be no longer than 13 characters; restrict authentication to ASCII only names and passwords; etc. - (15) No auto-restart on service failure - (16) Better EventLog handling (17) Named Pipes Support [requires modifications to AFS servers to support] --- 1,27 ---- ! 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) File/Directory access is not integrated with windows security (3c) Loopback adapter hack: (i) prevents use of AFS Gateway (ii) requires installation of loopback adapter (iii) the list of hack adapters is incomplete (VMWare, MS TV/Video, ...) (9) Convert to IFS!!!!!! (12) AFS Integrated Logon: (12c) If network is not available must store the username and password somewhere until such time as the network starts. (14) No support for Unicode CIFS/SMB data structures. OEM Code Pages prevent the use of interoperable file names; force the use of paths no longer than 256 characters; force share names to be no longer than 13 characters; restrict authentication to ASCII only names and passwords; etc. (16) Better EventLog handling (17) Named Pipes Support [requires modifications to AFS servers to support] *************** *** 92,114 **** or by the new AFS Client Service Administration tool when executed by an authorized user. ------------------------------------------------------------------------- List of unfunded projects: - 1. No longer use AFS Client Service "cell" as the default cell for individual users - 2. Prevent panic situation when the root.afs volume is not reachable and - the AFS Client Server is not using Freelance mode - 3. Prevent panic situation when the IP address to which the SMB server is bound is removed - from the local machine's network configuration 4. Add support for Named Pipes within the afs filesystem (This is not currently a supported feature of AFS; it will require changes to the servers as well as the clients.) - 5. Replace afscreds.exe with netidmgr.exe to support: - 1. choosing between Kerberos 5 and Kerberos 4 on a per principal basis - 2. providing users with the ability to map multiple cells to a single principal - 3. providing change password functionality on a per principal basis - 4. no longer include drive mapping - 5. configuration of afscreds startup options in shortcut 6. Re-write afs_config.exe to be only "per user" functionality which does not require admin privileges 1. default cell and principal for the user --- 58,71 ---- or by the new AFS Client Service Administration tool when executed by an authorized user. + (24) Compatibility with Vista User Account Control (UAC) + ------------------------------------------------------------------------- List of unfunded projects: 4. Add support for Named Pipes within the afs filesystem (This is not currently a supported feature of AFS; it will require changes to the servers as well as the clients.) 6. Re-write afs_config.exe to be only "per user" functionality which does not require admin privileges 1. default cell and principal for the user *************** *** 163,166 **** --- 120,124 ---- 26. Implement RX Connection Pools in the Cache Manager allowing more than four simultaneous requests to a single server to be processed at a time for a single user + 27. Support the Vista User Account Control (UAC) interface \ No newline at end of file