Touching bin/httpd.exe.local just got me out from under a restart failure with a third-party module that provide a modified copy of the openssl libraries. Upon restart mod_ssl would glom onto the already-loaded (and modified) SSL libraries (and fail due to something like a missing symbol/ordinal). After creating the .local file, windows aggressively loaded the local lib as a 2nd copy.
Anyone recall other problems with libraries brought in by third-party modules that might be addressed by this? Any cautions? http://msdn.microsoft.com/en-us/library/ms811700.aspx#sidebyside_topic3 Activating DLL/COM Redirection DLL/COM redirection is activated on an application-by-application basis by the presence of a ".local" file. The ".local" file is an empty file in the same directory as the application's .exe file, with the same name as the application's .exe file with ".local" appended to the end of the name. For example, to activate DLL/COM redirection for an application called "myapp.exe," create an empty file called "myapp.exe.local" in the same directory where myapp.exe is installed. Once DLL/COM redirection is activated, whenever the application loads a DLL or an OCX, Windows looks first for the DLL or OCX in the directory where the application's .exe file is installed. If a version of the DLL or OCX is found in the directory where the application's .exe file is installed, the application uses it regardless of any directory path specified in the application or the registry. If a version of the DLL or OCX is not found in the directory where the application's .exe file is installed, the normal search path or server path is used. -- Eric Covener [EMAIL PROTECTED]
