On 3/11/08, Volker Lendecke <[EMAIL PROTECTED]> wrote: > On Tue, Mar 11, 2008 at 12:53:19PM +0100, Dragan Krnic wrote: > > I will, but is it really a bug? > > Or was it designed to hurt Samba? > > Naaa, a handle leak is definitely a bug. I never believed > that Microsoft puts in stuff to annoy Samba. The worst I > could believe is that they choose some nasty timing for > announcements, but I don't think they ever put stuff in to > explicitly break Samba. This does not say that they > deliberatly neglect Samba in their testing and that they > might have been happy in the past about the fallout when > they break us by accident, but directly nasty -- no.
By the way, a colleague of mine who was bothered by this problem (MFC Cfile objects leaking parent dir handles) found out that this problem only started with "MFC42.dll" in Version 6.6, which is installed in both "System32" and in "SysWoW64" subdirs of an XP/x64. He tried to replace it with the version 6.2, which is usually part of XP/ia32, but every time he deletes it or overwrites it, when he reboots the version 6.6 is again there. In short - by putting the "MFC42.dll" version 6.2 in the same directory with the executable, e.g. "Tester.exe", the problem can also be solved but your patch is a much cleaner solution, especially knowing that it is part of the new Samba 3.0.28a. Thank you very much. Regards Dragan -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
