| www.delorie.com/archives/browse.cgi | search |
On Feb 20 16:20, Corinna Vinschen wrote: > On Feb 20 15:48, Carsten DOT Porzler AT spb DOT de wrote: > > 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. > > I just discussed this problem and my code with somebody having more > insight into this AD stuff. I now have a hunch what I could do to > fix this bad timing problem. Stay tuned. Please try the latest 1.7.0 incarnation: http://cygwin.com/ml/cygwin-announce/2009-02/msg00018.html This hopefully fixes the above problem. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |