Timeline for Faster way to delete large number of files
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 25, 2020 at 17:41 | comment | added | Steven the Easily Amused |
This was likely downvoted because it's dangerous. Where the original question mentioned ./cache this answer assumes that ./cache is the current directory - which it would not be per the OP. Secondly, the addition of the -print would spew (tens of) thousands of lines of output. There is another subtle issue: if there are subdirectories in the current directory, it will attempt (and fail) to delete them - unless they are already empty... but that may also be undesired! Why: Because find does a depth-first search starting at each subdirectory.
|
|
| Nov 25, 2014 at 7:02 | history | edited | Archemar | CC BY-SA 3.0 |
fixed some typos
|
| S Nov 25, 2014 at 6:49 | review | Low quality posts | |||
| Nov 25, 2014 at 7:02 | |||||
| S Nov 25, 2014 at 6:49 | review | Late answers | |||
| Nov 25, 2014 at 7:06 | |||||
| Nov 25, 2014 at 6:34 | review | First posts | |||
| Nov 25, 2014 at 6:37 | |||||
| Nov 25, 2014 at 6:33 | history | answered | Manoj | CC BY-SA 3.0 |