This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Our company recently switched to an "active directory" network, with different login credentials. Don't ask me what that is exactly. Ever since, anything having to do with Cygwin takes seconds or minutes, whereas it used to be instantaneous. Even having "uname -a" in a Take Command (like CMD.EXE) shell causes the shell window to take seconds to come up. Comment out the uname, and the shell window comes up instantaneously. You don't want to know how long I have to wait for an Xterm to start so I can run Emacs to open a file... My /etc/nsswitch.conf is as follows (the only thing I define is db_home). # passwd: files db # group: files db # db_enum: cache builtin # db_home: /home/%U db_home: /cygdrive/c/Users/jr920141/Box%_Sync/Home # db_shell: /bin/bash # db_gecos: <empty> I've attached cygcheck.out but don't know if that will help. It's the exact same laptop. I don't know why a network change would cause Cygwin to slow down so much. Suggestions or speculations would be appreciated! Thanks - Jim -- Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us
Attachment:
cygcheck.out
Description: Binary data
-- 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
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |