This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 1.1.10 Problem: mv and directories in use

> I believe the main source of the problem is a Windows "BUG" (Not really a
> bug, that is how Windows is "intended" to work). Anyways, it is an
> undesirable "feature" for sure, and very annoying when in the Cygwin
> enviornment. For the average joe Windows user in Windows Explorer it "kind
> of" makes sense that Windows works this way.
It is also due, in part, to the way Cygwin's fhandler's work.

> If bash (or cmd) is in a particular directory just sitting at the prompt,
> that directory is in use, then that problem will arise if the directory is
> attempted to be moved. It is very annoying. As a partial work around, bash
> could be maybe modified to never "sit" in the current directory, but
> to hang out on the root of the drive, and only switch to the current
> directory when a command is run.
I agree, try submitting a patch for bash and see if it gets accepted.

> A similar problem (due to the same, or related, Windows "BUG") manifests
> itself if you try to overwrite an executable that has an instance of
> currently running. That is a very annoying "feature" as well.
This is because the executable files are memory mapped so that currently
running applications don't take up so much memory.

> Though I agree with you, it would be nice if mv said ahead of time that it
> could not do it and saved me the clean up hassles when it fails.
I disagree. Ok, some files maybe can't be deleted at the present time, but
say I want a directory in its new location now. If mv refused to act when
one or more files were locked I'd have to copy the whole directory and then
come back and delete the old directory later. What if I forget? I lose a
whole load of disk space, whereas if only one or two files are left behind
that's far more acceptable. It's better for mv to execute the user's command
as far as possible.

> > Instead of returning an error, something like "/1" is in use, it copies
> > to /2, THEN returns:
> > mv: cannot remove directory `/1': Permission denied
> > mv: cannot remove `/1': Permission denied
> >
> > Shouldn't it say something like:
> > mv: cannot move `/1': Directory in use


Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]