TEST RELEASE: Cygwin 1.7.35-0.3

[John Hein]

Corinna Vinschen wrote at 11:59 +0100 on Feb 18, 2015:
 > Hi Cygwin friends and users,
 >
 > I released another very early TEST version of the next upcoming Cygwin
 > release.  The version number is 1.7.35-0.3.
 >
 > This release introduces a revision of the LDAP calls done to fetch
 > information from the DC.  By limiting the search scope, the calls should
 > now be faster even in bigger environments.  Please give it a try with
 > activated "db" settings for passwd and group entries in /etc/nsswitch.conf
 >
 >   passwd: db
 >   group: db
 >
 > Please report back your experience, especially if you're suffering
 > from "slow startup" problems.

Without 'files' in /etc/nsswitch.conf or 'cygserver' running, the
testing cycle here is slow.  So I've been a bit delayed at reporting
back.  I know some people have alleged wonderful speedups with
1.7.35-0.3, but I can't report the same.

Here I'm in an AD environment with ~8000 entries in AD (as determined
by 'mkpasswd -d | wc') and I'm in 200+ groups.  I guess I'd call it
somewhat large, and the network is geographically spread out and
connected by links that vary in speed (the slowest is probably 10s of
Mbps), although there is a local AD "slave" on the local LAN.

It's particularly slow if I force using my shell of choice (tcsh)
rather than forcing '/bin/dash' as the 'db_shell' entry in
nsswitch.conf.  This is likely because of all the various things that
get executed at shell startup (csh.cshrc, profile.d/*.csh).

Just to avoid any possible cruft from my old cygwin install, I
installed a minimal fresh cygwin.  The only change was to
nsswitch.conf:

passwd: db
group: db
db_shell: /bin/dash

Starting mintty with db_shell set to /bin/tcsh has taken up to a half
hour before the prompt appears.  I don't have a complicated .cshrc
(just a few alias definitions & 'set' commands).


Also mkpasswd -d seems to be taking a long time (haven't had it
complete in hours now).  That didn't happen with 1.7.34 - maybe
there's a local issue here on our network.  What's a good way to debug
what's happening with mkpasswd?  Seems like its not doing anything.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple