X-Spam-Check-By: sourceware.org Date: Tue, 20 Jun 2006 10:14:17 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: bash and CSRSS consuming 100% of CPU Message-ID: <20060620141417.GF19534@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <003b01c69406$749c41f0$0a3b6080@joehome> <00c801c69460$c3fd0c70$a501a8c0@CAM.ARTIMI.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00c801c69460$c3fd0c70$a501a8c0@CAM.ARTIMI.COM> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Tue, Jun 20, 2006 at 12:57:54PM +0100, Dave Korn wrote: >On 20 June 2006 02:11, Science Guy wrote: > >> I got cygwin working once again on my problem machine. (Hooray!) >> >> The problem was that the snapshot tar file, cygwin-inst-20060614.tar.bz2, >> had cygwin1.dll in /usr/bin but failed to replace the old cygwin1.dll in >> /bin. I copied over the new cygwin1.dll into /bin, and things are working >> nicely once again. > > Yes, tar can't replace the cygwin dll, because tar relies on having the >cygwin dll loaded in order to run! You have to extract it separately and use >a dos prompt to copy it across. You obviously read the FAQ entry, because you >knew to use the "--exclude=usr/bin/cygwin1.dll" option; read the bit just >after that again. I guess it's only implied rather than explicit, that you >could have installed the dll first and the rest later; maybe we could make it >clearer. Dave, I think you missed this: >sciguy wrote: >>I am networked to a Linux machine, so I moved the tar file >>cygwin-inst-20060614.tar.bz2 over to the Linux machine, created a dummy >>cygwin directory to hold the file, and un-tarred it there using this >>command: >> >>% /bin/tar -jxvf cygwin-inst-20060614.tar.bz2 >> >>Then I ftp'd the entire un-tarred file and directory structure over the >>cygwin directory of the affected Windows PC. This is why I kept mentioning that the snapshot cygwin DLL wasn't installed in the right location. I correctly assumed that this step did not put the cygwin DLL (or any of the cygwin programs) in c:\cygwin\bin. The cygcheck output made this pretty clear. cgf -- 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/