STABLE14-windows-notes-20050529

Update notes for 1.3.8300


(cherry picked from commit c915a6bce730fca994aef77b8a3224a3f126bae7)
This commit is contained in:
Jeffrey Altman 2005-05-30 05:13:42 +00:00
parent 29897ad340
commit e188ff4d99
2 changed files with 31 additions and 4 deletions

View File

@ -1,4 +1,17 @@
Since 1.3.82:
* The OpenAFS integrated logon obtains Kerberos 5 tickets as part of
the process of producing AFS tokens. The tokens are stored within
the AFS Client Service but the Kerberos 5 tickets have been discarded.
New functionality has been added to temporarily copy the tickets to
a file ccache during the short window between the NPLogonNotify and
WinLogon Logon Event. The Logon Event handler starts a process as
user, afscpcc.exe, that copies the tickets into the default ccache.
The file ccache is then destroyed by the event handler.
* During synchronization operations on stat cache entries, if threads
are forced to sleep it was possible that the threads would not be
woken under heavy load.
* Enforce the delete on close flag specified by the NTCreateX()
operation.

View File

@ -584,6 +584,20 @@ entries are present and that they refer to the dll "rpcrt4.dll":
HKLM "SOFTWARE\Microsoft\RPC\ClientProtocols" "ncacn_ip_tcp"
HKLM "SOFTWARE\Microsoft\RPC\ClientProtocols" "ncadg_ip_udp"
41. Starting in 1.3.83, when Integrated Logon is used in conjunction
with KFW, the Kerberos 5 tickets obtained during the process of
generating AFS tokens are preserved and stored into the default
ccache within the user logon session.
42. 1.3.83 adds a new command, "fs minidump". This command can
be used at any time to generate a mini dump file containing the
current stack of the afsd_service.exe process. This output can
be very helpful when debugging the AFS Client Service when it is
unresponsive to SMB/CIFS requests.
------------------------------------------------------------------------
Reporting Bugs:
@ -591,10 +605,10 @@ Reporting Bugs:
Bug reports should be sent to openafs-bugs@openafs.org. Please include as
much information as possible about the issue. If you are reporting a crash,
please install the debugging symbols by re-running the installer. If a dump
file is available for the problem include it along with the AFS Client Trace
file %WINDIR%\TEMP\afsd.log. The AFS Client startup log is
%WINDIR%\TEMP\afsd_init.log. Send the last continuous block of log
information from this file.
file is available for the problem, %WINDIR%\TEMP\afsd.dmp, include it along
with the AFS Client Trace file %WINDIR%\TEMP\afsd.log. The AFS Client
startup log is %WINDIR%\TEMP\afsd_init.log. Send the last continuous block
of log information from this file.
Configuring DrWatson to generate dump files for crashes: