Re: ls / rm etc return "no such file or directory"

On Thu, Aug 09, 2007 at 01:50:59PM -0700, TomL wrote: > > Based on the idea that its a file locking problem, I ran "handle" from > sysinternals, and it showed up as an open filehandle in an explorer.exe > process. I terminated the process, and all is well. > > I don't understand how it got into

Re: ls / rm etc return "no such file or directory"

Based on the idea that its a file locking problem, I ran "handle" from sysinternals, and it showed up as an open filehandle in an explorer.exe process. I terminated the process, and all is well. I don't understand how it got into that state yet, but I'm closer. Thanks for the hints. Warren Yo

Re: ls / rm etc return "no such file or directory"

Files/directories in this mode only occur on the system when created from within cygwin. In this instance, it was created by FileUtils::mkdir_p in a cygwin ruby script. It went into this mode after attempting to remove it with FileUtils::rm_rf Incidentally, that may be the trick -- there might

Re: ls / rm etc return "no such file or directory"

TomL wrote: cmd.exe: H:\some_dir>rd /s .tmp1732200708091223 .tmp1732200708091223, Are you sure (Y/N)? y Access is denied. How is this a Cygwin issue if regular Win32 commands give the same problems? This is likely yet another example of why enabling file locking by default is brain damaged,

ls / rm etc return "no such file or directory"

I've been googling for two hours and I can't find any relevant information on this. Can the following be explained, and how can it be resolved? bash: $ vdir -d .* vdir: cannot access .tmp1732200708091223: No such file or directory drwxr-xr-x 1 xxx Domain Users 0 Aug 9 12:37 . drwxr-xr-x 1 xxx D