Re: 1.7.[67]: getting bash prompt takes 50 seconds
Am 02.09.2010, 04:30 Uhr, schrieb Mark Callow: Hi Andrey, Did you tried to *uninstall* bash-completion? I have now. Surprisingly (to me) it worked. The time-to-prompt has dropped to ~5 seconds on one of the machines and ~8 seconds on the other. Both are still too long but a vast improvement over 50 seconds. You can open a cmd.exe terminal window and type bash --login -x (or -xv) to figure if it spends a particularly long time in a certain area of the .bashrc execution, however, Cygwin is indeed a lot slower than Unix when shell scripting, because creating Unix processes is very costly in Cygwin, and that is an operation that happens a lot in shell scripts... -- Matthias Andree -- 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
Re: 1.7.[67]: getting bash prompt takes 50 seconds
On 9/1/2010 8:35 AM, Andrey Repin wrote: + Did you tried to *uninstall* bash-completion? What changed such that bash-completion, which previously worked fine, no longer does? -- 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
Re: 1.7.[67]: getting bash prompt takes 50 seconds
On 9/2/2010 11:03 PM, Reid Thompson wrote: On 9/1/2010 8:35 AM, Andrey Repin wrote: + Did you tried to *uninstall* bash-completion? What changed such that bash-completion, which previously worked fine, no longer does? Upstream changes. They're working on fixes. See recent email archives if you're interested in some details. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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
Re: 1.7.[67]: getting bash prompt takes 50 seconds
On 9/2/2010 11:03 PM, Reid Thompson wrote: On 9/1/2010 8:35 AM, Andrey Repin wrote: + Did you tried to *uninstall* bash-completion? What changed such that bash-completion, which previously worked fine, no longer does? The biggest change i've seen is in the slowdown of ./configure and make -- 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
1.7.[67]: getting bash prompt takes 50 seconds
We updated the cygwin installation on one of our systems on 8/26. We immediately started to experience a very lengthy delay of 50 seconds getting the bash prompt, measured beginning when the terminal emulator window appears. Also bash scripts seem to be taking longer to run than before. While investigating, today I updated the cygwin installation on another machine; and it immediately began to experience the same problem. Nothing else on this 2nd machine was changed. The cygwin versions involved are 1.7.6 and 1.7.7. The bash version is 3.2.51(24). I have another machine with a virtually identical environment as the 2nd but except it is still running cygwin 1.7.5 and bash 3.2.49(23). It does not suffer this problem. These are also the versions that were running on the 2nd machine prior to its upgrade. Seeing old reports in this list of all the scripts in bash-completion.d taking a long time to run, I moved that aside. It made no difference. I replaced bash.exe on an affected machine with 3.2.49 but the problem remains so it appears to be a cygwin rather than a bash problem. These machines all use cyglsa. Suspecting a delay during user authentication, I re-ran cyglsa-config to ensure the latest dll is installed; it made no difference. Needless to say, we do not want to update the cygwin installation on any other system until this problem is resolved. The machines are running Windows XP SP3 Japanese version. I am afraid to update my PC that runs the English version of XP SP3 so I cannot absolutely confirm it, but I don't think the language version is related to the problem. It happens without LANG set and when it is set to en_GB or ja_JP. Regards -Mark -- 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
Re: 1.7.[67]: getting bash prompt takes 50 seconds
Greetings, Mark Callow! We updated the cygwin installation on one of our systems on 8/26. We immediately started to experience a very lengthy delay of 50 seconds getting the bash prompt, measured beginning when the terminal emulator window appears. Also bash scripts seem to be taking longer to run than before. Did you tried to *uninstall* bash-completion? -- WBR, Andrey Repin (anrdae...@freemail.ru) 01.09.2010, 16:35 Sorry for my terrible english... -- 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
Re: 1.7.[67]: getting bash prompt takes 50 seconds
Hi Andrey, Did you tried to *uninstall* bash-completion? I have now. Surprisingly (to me) it worked. The time-to-prompt has dropped to ~5 seconds on one of the machines and ~8 seconds on the other. Both are still too long but a vast improvement over 50 seconds. Regards -Mark -- 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
