X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: <417118 DOT 17356 DOT qm AT web111104 DOT mail DOT gq1 DOT yahoo DOT com> Date: Wed, 11 Mar 2009 10:22:27 -0400 Message-ID: <5a05e0e60903110722i6ae35a95p9105eb7300846f15@mail.gmail.com> Subject: Re: Upgrade woes ("file in use") From: Dave Steenburgh To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 On Tue, Mar 10, 2009 at 5:24 PM, Tim McDaniel wrote: > > On Tue, 10 Mar 2009, Nuzhna Pomoshch > wrote: >> >> During a recent upgrade of about a dozen packages, I saw >> the =A0Cygwin setup window progress normally ("deleting >> package xyz..."), and then up popped a window that said: >> >> "In-use files detected" >> >> "Unable to extract /etc/postinstall/bash.sh -- the file is >> in use. Please stop all Cygwin processes and select >> 'Retry,' or select 'Continue' to go on anyway (you will >> need to reboot)." >> >> I didn't have any Cygwin processes running > > There can be processes running that you can't see easily. =A0I use > Process Explorer, from , which now > redirects to > . > Perhaps the default Task Manager works OK for this purpose. The Windows Task Manager will indeed show you all the processes running on your computer. However, Process Explorer can show you the dlls and handles that processes are using. It also lets you search for specific items, like etc\postinstall\bash.sh (use backslash as a separator, or you won't get any hits). On Wed, Mar 11, 2009 at 8:00 AM, Dave Korn wrote: > 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, y= ou > 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. Reinstalling everything is probably overkill. I would reinstall the Base group, then use cygcheck -c to figure out which other packages need to be reinstalled. Reinstall any packages that aren't OK, and then everything should work. -- 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/