Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

rmdir /s recurses into symlinkd directories

Oct
4
0
I am testing out 12.00.27 under Windows 7.

cmd.exe does not do this under Windows 7, and I would say this is correct behavior. The symlinkd should be deleted, but the files residing within the symlinkd should not.

Thoughts?

Josh
 
| I am testing out 12.00.27 under Windows 7.
|
| cmd.exe does not do this under Windows 7, and I would say this is
| correct behavior. The symlinkd should be deleted, but the files
| residing within the symlinkd should not.
|
| Thoughts?

First, the body of your post does not indicate what you'd like to be
different. Remember, those of us who read this as email have need superior
eyesight to read the title.
That aside, I agree in principle, regardless of what CMD.EXE does - by
default RMDIR /S ought to delete only what is in the physical tree, not its
logical extensions (those created as junctions or symlinks). Personally I'd
prefer the addition of the J suboption to /N as available in the ERASE etc.
commands. I always you ERASE to achieve what RMDIR could do due to its much
greater flexibility.
--
Steve
 
| I am testing out 12.00.27 under Windows 7.
|
| cmd.exe does not do this under Windows 7, and I would say this is
| correct behavior. The symlinkd should be deleted, but the files
| residing within the symlinkd should not.

First, the body of your post does not indicate what you'd like to be
different. Remember, those of us who read this as email have need superior
eyesight to read the title.

That aside, I agree in principle, regardless of what CMD.EXE does - by
default RMDIR /S ought to delete only what is in the physical tree, not its
logical extensions (those created as junctions or symlinks).

What you have stated, 'RMDIR /S ought to delete only what is in the physical tree', is precisely the default behavior I think RMDIR /S should have.

Thanks for the reply!
 
The symlinkd should be deleted, but the files residing within the symlinkd should not.

I agree. I think to remember that TakeCommand will also recurse into junctions. Which is just as bad. Or if you delete a junktion / symlink then it will try to delete content. You need to use MKLNK /D to delete junktion / symlink - which is a rather uggly hack.
 
Back
Top