From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11286 invoked by alias); 20 Feb 2009 14:47:23 -0000 Received: (qmail 11277 invoked by uid 22791); 20 Feb 2009 14:47:23 -0000 X-SWARE-Spam-Status: No, hits=-0.2 required=5.0 tests=AWL,BAYES_50,UNPARSEABLE_RELAY X-Spam-Check-By: sourceware.org Received: from mailout-t2.spb.de (HELO mail2.sparda-bank.de) (195.145.106.114) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 20 Feb 2009 14:47:17 +0000 Received: from upmailcrypt2.spb.de (unknown [194.15.183.131]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail2.sparda-bank.de (Postfix) with ESMTPS id 9D3E93E8053 for ; Fri, 20 Feb 2009 15:47:14 +0100 (CET) Received: (from smtpd@127.0.0.1) by upmailcrypt2.spb.de (8.13.8/8.13.8) id n1KElErp027526 for ; Fri, 20 Feb 2009 15:47:14 +0100 In-Reply-To: <20090122114202.GD17948@calimero.vinschen.de> References: <20090122114202.GD17948@calimero.vinschen.de> To: cygwin@cygwin.com MIME-Version: 1.0 X-KeepSent: F36E2CC4:772DB5B8-C1257563:004E05DF; type=4; name=$KeepSent Message-ID: From: Carsten.Porzler@spb.de Date: Fri, 20 Feb 2009 14:47:00 -0000 X-SafeGuard_MailGateway: Version: 5.30.1.7110 SGMG (smtpd: 6.71.2.3) Date: 20090220144713Z Subject: Re: SSH V.5.1 with Cygwin1.dll 1.7.0: Very large logon times... Content-Type: text/plain; charset="US-ASCII" X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2009-02/txt/msg00465.txt.bz2 Hello, > > No. Not really. The only reason could be that the code isn't called. > Only further debugging will help. > It ist very difficult to put in debug statements at the right places within the sourcecode because of the complexity of the programs. But we have just found out these new facts: - We copied our productive Active Directory database into a test environment + AD database contained 8700 users, 6000 groups, 9600 computers + part of this test network are only three computers: root domain controller, domain controller, member server + problem of large logon time could also be seen in this copied environment - In the next step we deleted most of the Active Directory objects + After this deletion process AD database contains only 278 users, 784 groups and 32 computers + SSH login takes only 1 sec. for login With theses informations it should be possible for you developers to adjust the situation. Increase the number of your Active Directory objects, and you will probably see that the logon time will also increase! Anything within your ssh logon process takes more time the bigger the Active Directory database is. Thanks a lot in advance and best regards Carsten Porzler -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/