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 {} \;
🐧 3 comments so far... add one ↓
| Category | List of Unix and Linux commands |
|---|---|
| File Management | cat |
| Firewall | Alpine Awall • CentOS 8 • OpenSUSE • RHEL 8 • Ubuntu 16.04 • Ubuntu 18.04 • Ubuntu 20.04 |
| Network Utilities | dig • host • ip • nmap |
| OpenVPN | CentOS 7 • CentOS 8 • Debian 10 • Debian 8/9 • Ubuntu 18.04 • Ubuntu 20.04 |
| Package Manager | apk • apt |
| Processes Management | bg • chroot • cron • disown • fg • jobs • killall • kill • pidof • pstree • pwdx • time |
| Searching | grep • whereis • which |
| User Information | groups • id • lastcomm • last • lid/libuser-lid • logname • members • users • whoami • who • w |
| WireGuard VPN | Alpine • CentOS 8 • Debian 10 • Firewall • Ubuntu 20.04 |
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.
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
its very good that -exec forks off a new process. Some commands have an upper limit of how many arguments you can give it. No complaining.