Shell script to delete directories older than n days
To they bare any relation on their actual creation/modification time? Because find could do it without looking at the name then.
What do you mean by «older than»? Are you referring to the time the directory was created, the time its contents were last changed, or something else? Be careful with some of the answers below; ctime is the inode change time. For a directory, it changes when files are added or removed from the directory.
5 Answers 5
This will do it recursively for you:
find /path/to/base/dir/* -type d -ctime +10 -exec rm -rf <> \; Explanation:
- find : the unix command for finding files / directories / links etc.
- /path/to/base/dir : the directory to start your search in.
- -type d : only find directories
- -ctime +10 : only consider the ones with modification time older than 10 days
- -exec . \; : for each such result found, do the following command in .
- rm -rf <> : recursively force remove the directory; the <> part is where the find result gets substituted into from the previous part.
Alternatively, use:
find /path/to/base/dir/* -type d -ctime +10 | xargs rm -rf Which is a bit more efficient, because it amounts to:
rm -rf dir1; rm -rf dir2; rm -rf dir3; . With modern versions of find , you can replace the ; with + and it will do the equivalent of the xargs call for you, passing as many files as will fit on each exec system call:
find . -type d -ctime +10 -exec rm -rf <> + -mtime was better for me as it checks content changes rather than permission changes, otherwise this was perfect.
The more efficient approach can backfire if you have too many folders to delete: stackoverflow.com/questions/11289551/…. For the same reason, in order to avoid deletion of the base folder it’s better to use -mindepth 1 (rather than /path/to/folder/* ).
If you want to delete all subdirectories under /path/to/base , for example
/path/to/base/dir1 /path/to/base/dir2 /path/to/base/dir3 but you don’t want to delete the root /path/to/base , you have to add -mindepth 1 and -maxdepth 1 options, which will access only the subdirectories under /path/to/base
-mindepth 1 excludes the root /path/to/base from the matches.
-maxdepth 1 will ONLY match subdirectories immediately under /path/to/base such as /path/to/base/dir1 , /path/to/base/dir2 and /path/to/base/dir3 but it will not list subdirectories of these in a recursive manner. So these example subdirectories will not be listed:
/path/to/base/dir1/dir1 /path/to/base/dir2/dir1 /path/to/base/dir3/dir1 So , to delete all the sub-directories under /path/to/base which are older than 10 days;
find /path/to/base -mindepth 1 -maxdepth 1 -type d -ctime +10 | xargs rm -rf Delete files older than X days +
Possibly fun when I have files with spaces. E.g a file called «test one» and rm gets fed rm test one . (Which will delete a file called «test» and a file called «one», but not a file called «test one»). Hint: -delete or -print0
As a side note, always quote the argument provided by find to avoid issues with special characters, as mentioned in the answer’s first line. E.g.: find /path/to/files/ -exec somecommand ‘<>‘ \;
4 Answers 4
Be careful with special file names (spaces, quotes) when piping to rm.
There is a safe alternative — the -delete option:
find /path/to/directory/ -mindepth 1 -mtime +5 -delete That’s it, no separate rm call and you don’t need to worry about file names.
Replace -delete with -depth -print to test this command before you run it ( -delete implies -depth ).
- -mindepth 1 : without this, . (the directory itself) might also match and therefore get deleted.
- -mtime +5 : process files whose data was last modified 5*24 hours ago.
Alternatively, if you want to do the same for all files NEWER than five days: find /path/to/directory/ -mindepth 1 -mtime -5 -delete
Note that every find argument is a filter that uses the result of the previous filter as input. So make sure you add the -delete as the last argument. IE: find . -delete -mtime +5 will delete EVERYTHING in the current path.
Note that this command will not work when it finds too many files. It will yield an error like:
bash: /usr/bin/find: Argument list too long Meaning the exec system call’s limit on the length of a command line was exceeded. Instead of executing rm that way it’s a lot more efficient to use xargs. Here’s an example that works:
find /root/Maildir/ -mindepth 1 -type f -mtime +14 | xargs rm This will remove all files (type f) modified longer than 14 days ago under /root/Maildir/ recursively from there and deeper (mindepth 1). See the find manual for more options.
How to delete files older than X hours
This will delete of the files older than 1 day. However, what if I need a finer resolution that 1 day, say like 6 hours old? Is there a nice clean way to do it, like there is using find and -mtime?
9 Answers 9
Does your find have the -mmin option? That can let you test the number of mins since last modification:
find $LOCATION -name $REQUIRED_FILES -type f -mmin +360 -delete Or maybe look at using tmpwatch to do the same job. phjr also recommended tmpreaper in the comments.
Using —mmin +X returns all files with my find. My fault for not checking this first, but this command just deleted most of my home directory. For me, —mmin -X is the correct argument.
tmpreaper is a fork of tmpwatch. It is safer, and exists as a debian package in the distro. Benefits over find -delete : tmpreaper will not remove symlinks, sockets, fifos, or special files
Point out that $REQUIRED_FILES need to be in quotes (double quotes) and you can use a pattern like: «.txt» for all .txt files or files beginning with a pattern like: «temp-» to delete all files named with temp-
@PaulDixon how to modify this so that $LOCATION and $REQUIRED_FILES can both have multiple values such as dir1 dir2 and *.txt *.tmp ?
@Enissay $LOCATION is a single directory. For multiple extensions you’d probably want to use a pattern with -regex — see stackoverflow.com/questions/5249779/…
Here is the approach that worked for me (and I don’t see it being used above)
$ find /path/to/the/folder -name '*.*' -mmin +59 -delete > /dev/null deleting all the files older than 59 minutes while leaving the folders intact.
Better to single-quote ‘*.*’ or the shell will expand it to actual filenames instead of keeping it as a wildcard for find to resolve. This breaks find ‘s recursive operation on subdirs.
Also keep in mind that -name ‘*.*’ will not delete files that have no extension, such as README , Makefile , etc.
You could to this trick: create a file 1 hour ago, and use the -newer file argument.
(Or use touch -t to create such a file).
there is no -older switch (at least in my find command), and that’s what would be needed. -newer doesn’t help.
can you give a touch command that would generate a file 1 hour old that will work on machines that can’t use -mmin? (If you’re on Linux, -mmin is available, if not then date and other commands are also feeble in comparison.)
@iconoclast touch -t $(date -d ‘-1 hour’ +%Y%m%d%H%M.00) test Creates file test that’s always 1 hour old.
To rm files and directories older than file.ext run rm -r `find -maxdepth 1 -not -newer file.ext` . To rm files and directories newer than file.ext do rm -r `find -maxdepth 1 -newer file.ext` . To place file.ext where you want it in time run touch -t $(date -d ‘-1 hour’ +%Y%m%d%H%M.00) file.ext where ‘-1 hour’ specifies «1 hour ago». Credit: xoftl, rovr138, nickf.
Example 6 Selecting a File Using 24-hour Mode The descriptions of -atime, -ctime, and -mtime use the ter- minology n ``24-hour periods''. For example, a file accessed at 23:59 is selected by: example% find . -atime -1 -print at 00:01 the next day (less than 24 hours later, not more than one day ago). The midnight boundary between days has no effect on the 24-hour calculation. If you do not have «-mmin» in your version of «find», then «-mtime -0.041667» gets pretty close to «within the last hour», so in your case, use:
so, if X means 6 hours, then:
works because 24 hours * 0.25 = 6 hours
Was hopeful because this old UNIX doesn’t have -mmin, but, sadly this is of no help as this old UNIX also does not like fractional values for mtime: find: argument to -mtime must be an integer in the range -2147483647 to 2147483647
If one’s find does not have -mmin and if one also is stuck with a find that accepts only integer values for -mtime , then all is not necessarily lost if one considers that «older than» is similar to «not newer than».
If we were able to create a file that that has an mtime of our cut-off time, we can ask find to locate the files that are «not newer than» our reference file.
To create a file that has the correct time stamp is a bit involved because a system that doesn’t have an adequate find probably also has a less-than-capable date command that could do things like: date +%Y%m%d%H%M%S -d «6 hours ago» .
Fortunately, other old tools can manage this, albeit in a more unwieldy way.
To begin finding a way to delete files that are over six hours old, we first have to find the time that is six hours ago. Consider that six hours is 21600 seconds:
$ date && perl -e '@d=localtime time()-21600; \ printf "%4d%02d%02d%02d%02d.%02d\n", $d[5]+1900,$d[4]+1,$d[3],$d[2],$d[1],$d[0]' > Thu Apr 16 04:50:57 CDT 2020 202004152250.57 Since the perl statement produces the date/time information we need, use it to create a reference file that is exactly six hours old:
$ date && touch -t `perl -e '@d=localtime time()-21600; \ printf "%4d%02d%02d%02d%02d.%02d\n", \ $d[5]+1900,$d[4]+1,$d[3],$d[2],$d[1],$d[0]'` ref_file && ls -l ref_file Thu Apr 16 04:53:54 CDT 2020 -rw-rw-rw- 1 root sys 0 Apr 15 22:53 ref_file Now that we have a reference file exactly six hours old, the «old UNIX» solution for «delete all files older than six hours» becomes something along the lines of:
$ find . -type f ! -newer ref_file -a ! -name ref_file -exec rm -f "<>" \; It might also be a good idea to clean up our reference file.
bash как удалить файлы и директории, старше x-дней?
Есть некая директория Test. В ней находятся файлы и папки. Как удалить только то, что старше 10 дней к примеру.
find /volume1/Test -cmin +$storetime -delete приводит к удалению и самой директории Test, если в ней нет свежих файлов, естественно.
find /volume1/Test -mtime +10 -exec rm <> \; ?
TС: добавь ключик type -f к файнду и в результате будут только файлі.
TС: добавь ключик type -f к файнду и в результате будут только файлі.
Там не только файлы под удаление, но и папки, в том то и проблема.
Illujanka ( 07.11.19 10:21:52 MSK )
Последнее исправление: Illujanka 07.11.19 10:26:37 MSK (всего исправлений: 1)
find /volume1/Test -mtime +10 -exec rm <> \; ? При Test, без свежих файлов, удаляет и саму Test
Illujanka ( 07.11.19 10:23:13 MSK )
Последнее исправление: Illujanka 07.11.19 10:25:49 MSK (всего исправлений: 1)
Разница в скорости будет незаметна, но зато есть везде, ибо posix. Но для не \;, а +
vodz ★★★★★ ( 07.11.19 10:27:24 MSK )
Последнее исправление: vodz 07.11.19 10:28:39 MSK (всего исправлений: 1)
про ключ -mindepth тебе уже писали
про ключ -mindepth тебе уже писали
Всегда удивляет в тутошних комментаторов желание решить как можно узкую задачу с возможностью появления завтра у ТСа еще вопроса, например, что делать, если в каталоге появится другие подкаталоги и rm на них ругается. Одно дело, когда универсальное требует кучу нового кода, другое дело, что правильный ответ скорее всего не -mindepth, а таки тоже уже данный «-type f»
vodz ★★★★★ ( 07.11.19 11:12:42 MSK )
Последнее исправление: vodz 07.11.19 11:14:44 MSK (всего исправлений: 1)
При Test, без свежих файлов, удаляет и саму Test
Вариант с * не затронет сам каталог