Re: cygwin 1.7 lock directory problem

2010-08-18 Thread Corinna Vinschen
On Aug 18 01:52, Christopher Faylor wrote: 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

Re: cygwin 1.7 lock directory problem

2010-08-18 Thread Andrey Repin
Greetings, Corinna Vinschen! 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.

Re: cygwin 1.7 lock directory problem

2010-08-18 Thread Corinna Vinschen
On Aug 18 14:28, Andrey Repin wrote: Greetings, Corinna Vinschen! 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,

Re: cygwin 1.7 lock directory problem

2010-08-18 Thread Eric Blake
On 08/18/2010 05:08 AM, Corinna Vinschen wrote: Looks like this behaviour is a problem and we should better close the old handle. What to do with the new one? Just set it to NULL and disallow stackdumps as long as we're in a virtual path? Or set it to some well known path, like Cygwin's

Re: cygwin 1.7 lock directory problem

2010-08-18 Thread Huang Bambo
2010/8/18 Eric Blake ebl...@redhat.com: On 08/18/2010 05:08 AM, Corinna Vinschen wrote: Looks like this behaviour is a problem and we should better close the old handle.  What to do with the new one?  Just set it to NULL and disallow stackdumps as long as we're in a virtual path?  Or set it to

Re: cygwin 1.7 lock directory problem

2010-08-18 Thread Christopher Faylor
On Wed, Aug 18, 2010 at 09:51:29PM +0800, Huang Bambo wrote: 2010/8/18 Eric Blake ebl...@redhat.com: On 08/18/2010 05:08 AM, Corinna Vinschen wrote: Looks like this behaviour is a problem and we should better close the old handle. ?What to do with the new one? ?Just set it to NULL and disallow

Re: cygwin 1.7 lock directory problem

2010-08-18 Thread Corinna Vinschen
On Aug 18 10:07, Christopher Faylor wrote: On Wed, Aug 18, 2010 at 09:51:29PM +0800, Huang Bambo wrote: 2010/8/18 Eric Blake ebl...@redhat.com: On 08/18/2010 05:08 AM, Corinna Vinschen wrote: Looks like this behaviour is a problem and we should better close the old handle. ?What to do with

cygwin 1.7 lock directory problem

2010-08-17 Thread Huang Bambo
cygwin version: 1.7.6(0.230/5/3) 2010-08-16 16:06 i686 Cygwin I don't know if this happen to previous version or not. If I first cd to a directory, for example /cygdriver/x then cd to a virtual directory, for example /proc the /cygdriver/x will be locked untile I change director to other

Re: cygwin 1.7 lock directory problem

2010-08-17 Thread Larry Hall (Cygwin)
On 8/17/2010 10:44 PM, Huang Bambo wrote: cygwin version: 1.7.6(0.230/5/3) 2010-08-16 16:06 i686 Cygwin I don't know if this happen to previous version or not. If I first cd to a directory, for example /cygdriver/x then cd to a virtual directory, for example /proc the /cygdriver/x will be

Re: cygwin 1.7 lock directory problem

2010-08-17 Thread Huang Bambo
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 )

Re: cygwin 1.7 lock directory problem

2010-08-17 Thread Christopher Faylor
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