Find and Delete File If It Is More Than One Hour Old in UNIX Shell
Q. How do I find out file last modification time using a shell script or command? How do I delete or take any other custom action for all files more than one hour old in /home/ftp/incoming/raw/ directory?
A. There are many ways (commands) to find out file modification time under UNIX / Linux operating system. You can try any one of the following command:
find command (with -cmin switch)
$ find /home/ftp/incoming/raw/ -maxdepth 1 -cmin +60 -name FileName
The -cmin option will print FileName's status was last changed n minutes ago. This command will print all file names more than one hour old.
stat command (with -c switch)
To find time of last change as seconds since Epoch, enter:
$ stat -c %Z /path/to/file
date command (with -r switch)
To display the last modification time of FILE, enter:
$ date -r /path/to/file
I recommend using find command as it has -exec option to take action on all matching file such as move or delete files:
$ find /home/ftp/incoming/raw/ -maxdepth 1 -cmin +60 -name "*" -exec /bin/rm -f {} \;
Subscribe to our free e-mail newsletter or RSS feed to get all updates.
You can Email this page to a friend.
Related Linux / UNIX FAQ:
- Locate files on linux, FreeBSD and UNIX system
- Find the file permission without using ls -l command
- Stop Ubuntu / Debian Linux From Deleting /tmp Files on Boot
- FreeBSD Find out who is logged in?
- Find files that do not have any owners or do not belong to any user under Linux/UNIX
Discussion on This FAQ
Leave a Reply
We encourage your comments, and suggestions. But please stay on topic, be polite, and avoid spam. Please do not use the comment form to ask for help / question. Ask your question on the excellent Linux tech support forum. Thank you very much for stopping by our site!
Tags: date command, file names, find file modification time, find-command, linux operating system, modification time, raw directory, shell script, stat c, stat command, unix shell ~ Last updated on: April 20, 2008
April 21st, 2008 (4 weeks ago) at 1:57 pm
find … -exec is BAD!
For every single result, it will fork off a copy of the command you exec. So if the above find command returns 500 files, rm will be forked 500 times.
Instead of doing it the above way, try this:
find /home/ftp/incoming/raw/ -maxdepth 1 -cmin +60 | xargs rm -rf
The -name ‘*’ argument to find was redundant.
April 26th, 2008 (3 weeks ago) at 6:27 am
Isn’t it better to use null character as a files separator (because of spaces in file/dir names)? like this:
find /home/ftp/incoming/raw/ -print0 -maxdepth 1 -cmin +60 | xargs -0 rm -rf