X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS,ZMIde_GENERICSPAM1 X-Spam-Check-By: sourceware.org Message-ID: From: Mike Marchywka To: Subject: RE: Upgrade woes ("file in use") Date: Wed, 11 Mar 2009 07:57:05 -0400 In-Reply-To: <49B7A7F8.8050104@gmail.com> References: <417118 DOT 17356 DOT qm AT web111104 DOT mail DOT gq1 DOT yahoo DOT com> <49B7A7F8 DOT 8050104 AT gmail DOT com> Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 ---------------------------------------- > Date: Wed, 11 Mar 2009 12:00:56 +0000 > From: reliable sources > To: cygwin AT cygwin DOT com > Subject: Re: Upgrade woes ("file in use") > > Nuzhna Pomoshch wrote: > >> "In-use files detected" >> >> "Unable to extract /etc/postinstall/bash.sh -- the file is >> in use. > > This is thoroughly bizarre. Nothing should be opening that file except > setup.exe itself (either when creating it or when invoking bash to run it > after installation is complete). It sounds very much like BLODA interfere= nce: > your on-access anti-virus scanner may have kept an open handle on it after > setup.exe had closed its own. It's known to occasionally happen with some= AVs. > >> So I rebooted the machine (definitely no Cygwin processes >> running now), and the same thing happened. > > That just makes it seem even more likely that it's something else install= ed > in your system that is interfering. > I used to have this problem with building c++ apps and ld couldn't over write the exe. I used the sysinternals handles to determine it was TeaTimer... >> Now, I no longer have bash (as well as many other cygwin >> programs). Nothing looks unusual on the machine to me. >> >> Can someone tell me what happened (and just as important, >> how to repair the Cygwin installation)? > > Simplest thing to do would be to re-run through setup.exe with everything > set to 'reinstall', but you'll need to find out what's interfering and di= sable > it first. If you need to do an emergency repair to get up and running, you > should be able to get at least somewhere by copying 'sh.exe' to 'bash.exe= ' in > the cygwin bin dir using DOS or windows explorer. > > cheers, > DaveK > > > -- > 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/ > _________________________________________________________________ Windows Live=99 Hotmail=AE:=85more than just e-mail.=20 http://windowslive.com/explore?ocid=3DTXT_TAGLM_WL_t2_hm_justgotbetter_expl= ore_022009 -- 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/