X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Wed, 18 Aug 2010 01:52:04 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygwin 1.7 lock directory problem Message-ID: <20100818055204.GA19288@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <4C6B5191.7070602@cygwin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: 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 Wed, Aug 18, 2010 at 01:05:13PM +0800, Huang Bambo wrote: >>Do you have a series of steps that produces the problem you see? >> > >As I said in previous mail. >1. cd /cygdriver/i ( I is mounted as a usb-stick) >2. cd /proc 3. Use some tools such as Unlocker to check driver I, >Unlocker said driver I is locked by bash. >4. cd / ( / is at d:\cygwin ) >5. do the same as step 3, driver is not locked by bash. That's how Cygwin 1.7.5 would work. I would expect different behavior for 1.7.6. cygcheck output would have saved speculation on which version you're running. -- 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