Ticket #18 (closed defect: fixed)
Support directory junctions and symlinks
| Reported by: | Joel | Owned by: | Joel |
|---|---|---|---|
| Priority: | major | Milestone: | Eraser 6.0 |
| Component: | Version: | 5.8.6a | |
| Keywords: | Cc: | ||
| Processor Architecture: | Blocked By: | ||
| Blocking: | Operating System: |
Description
Eraser needs to have proper support for both symbolic links as well as directory junctions in its code. Currently the erasures go on blindly.
Blocking
| Id | Summary | Milestone |
|---|---|---|
| #18 | └ Support directory junctions and symlinks | Eraser 6.0 |
Blocked by
| Id | Summary | Milestone |
|---|---|---|
| #18 | └ Support directory junctions and symlinks | Eraser 6.0 |
Change History
comment:2 Changed 15 years ago by Joel
Oh wait, sorry. Wrong ticket. But yah, this is in the v6 timeframe nonetheless.
comment:4 Changed 15 years ago by Joel
- Status changed from accepted to closed
- Resolution set to fixed
Fixed in r559.
The behaviour of Eraser when dealing with such files depends on the type of task:
- Files explicitly pointed to by the user is erased, leaving junk behind (other references will point to junk, but file metadata like size etc will remain)
- Folders selected for erasure will be erased, but:
- Files within the folder which are reparse points will be ignored
- Cluster tip erasures will skip reparse points
Hopefully this is adequate.
Note: See
TracTickets for help on using
tickets.
I think this will be in the timeframe for v6. v5 will continue to have the buffer expansion hack (which expands the maximum file path to ~4096 IIRC)