Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Injected-Via-Gmane: http://gmane.org/ To: cygwin AT cygwin DOT com From: Joe Buehler Subject: /proc/registry performance problem Date: Tue, 25 Mar 2003 12:59:57 -0500 Organization: Spirent Communications, Inc. Lines: 20 Message-ID: Reply-To: jbuehler AT hekimian DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet AT main DOT gmane DOT org User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en X-Enigmail-Version: 0.73.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Running "ls /proc/registry/HKEY_LOCAL_MACHINE" takes 5 to 10 seconds on my NT build machine. Using gdb to step through it, the culprit is the GetSecurityInfo() call in get_nt_object_attribute(). A google search shows up the following, a bug in GetSecurityInfo() in Windows that looks like it might be the problem: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaskdr/html/drgui47.asp It is also interesting that there is a known problem with GetSecurityInfo() failing in NT SP4 when a registry key is passed to the function: http://support.microsoft.com/default.aspx?scid=KB;en-us;q217075 Their workaround involves the use of RegGetKeySecurity(), so perhaps this is what should be used for registry keys instead of GetSecurityInfo(). I'll see if I can come up with a patch. -- Joe Buehler -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/