X-Spam-Check-By: sourceware.org Message-Id: <1136145671.25904.250873783@webmail.messagingengine.com> From: "Brett Serkez" To: cygwin AT cygwin DOT com Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 Subject: Re: Hope this topic isn't taboo yet Date: Sun, 01 Jan 2006 15:01:11 -0500 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com I've not seen any particular difference using Cygwin between hyper-threaded and non-hyper-threaded CPUs. I have seen issues with bash and sshd consuming 100% CPU for periods of time on both, which may or may not be related to ZoneAlarm. You can better identify the specific process by starting the task manager, and looking at the 'Processes' tab. I usually add the 'CPU Time' column via 'View -> Select Columns', so I can sort on it and see which processes are consuming allot of CPU over time and sort on the CPU column when looking while the problem is occuring to see which process is consuming allot of CPU in real-time. On the ZoneLabs message boards I found references to use of tcsh in place of bash, that seems to work around the problem as follows: - Run setup and select tcsh from shells - Modify /etc/passwd and change /bin/bash to /bin/tcsh for all appropriate users - Modify c:\cygwin\cygwin.bat and change 'bash --login' to 'tcsh -l' - Modify individual scripts, as appropriate, and change the she-bang line to: #!/bin/tcsh. This is an imperfect solution, but I've seen a noticable performance improvement as well as elimination of the CPU spikes. If you also run the secure shell daemon (sshd), before running ssh-host-config, modify it by locating '-a -D' and change to '-a "-D -r"' in two places. Adding the -r, which is applied to the -a which is why the double quotes are needed, turns off an extra fork/exec that theoretically makes sshd more secure but also causes the CPU spike. If you've already installed sshd as a service, you'll need to stop it and delete it before making these changes. It is my intuition that both issues revolve around process creation and security software examination of these events, looking for viruses and other threats. Brett ---------------------------------------------------------------- Brett C. Serkez, Techie -- 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/