Differences between revisions 14 and 15
Revision 14 as of 2014-06-04 21:26:13
Size: 3878
Editor: GreyCat
Comment: Get that fork-bomb exploit crap out of here.
Revision 15 as of 2015-03-05 00:18:33
Size: 3974
Editor: izabera
Comment: syntax hl
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
{{{ {{{#!highlight bash
Line 15: Line 15:
{{{ {{{#!highlight bash
Line 27: Line 27:
{{{ {{{#!highlight bash
Line 34: Line 34:
{{{ {{{#!highlight bash
Line 42: Line 42:
{{{ {{{#!highlight bash
Line 52: Line 52:
{{{ {{{#!highlight bash

How can I find the latest (newest, earliest, oldest) file in a directory?

The tempting solution is to use ls to output sorted filenames and take the first result. As usual, the ls approach cannot be made robust and should never be used in scripts due in part to the possibility of arbitrary characters (including newlines) present in filenames. Therefore, we need some other way to compare file metadata.

The most common requirement is to get the most or least recently modified files in a directory. Bash and all ksh variants can compare modification times (mtime) using the -nt and -ot operators of the conditional expression compound command:

   1 # Bash/ksh
   2 unset -v latest
   3 for file in "$dir"/*; do
   4   [[ $file -nt $latest ]] && latest=$file
   5 done

Or to find the oldest:

   1 # Bash/ksh
   2 unset -v oldest
   3 for file in "$dir"/*; do
   4   [[ -z $oldest || $file -ot $oldest ]] && oldest=$file
   5 done

Keep in mind that mtime on directories is that of the most recently added, removed, or renamed file in that directory. Also note that -nt and -ot are not specified by POSIX test, however many shells such as dash include them anyway. No bourne-like shell has analogous operators for comparing by atime or ctime, so one would need external utilities for that; however, it's nearly impossible to either produce output which can be safely parsed, or handle said output in a shell without using nonstandard features on both ends.

If the sorting criteria are different from "oldest or newest file by mtime", then GNU find and GNU sort may be used together to produce a sorted list of filenames + timestamps, delimited by NUL characters. This will of course operate recursively (GNU find's -maxdepth operator can prevent that); Here are a few possibilities, which can be modified as necessary to use atime or ctime, or to sort in reverse order:

   1 # Bash + GNU find + GNU sort (To the precision possible on the given OS, but returns only one result)
   2 IFS= read -r -d '' latest \
   3   < <(find "$dir" -type f -printf '%T@ %p\0' | sort -znr)
   4 latest=${latest#* }   # remove timestamp + space

   1 # GNU find + Bash w/ arrays (To the nearest 1s, using an undocumented "find -printf" format (%Ts).)
   2 while IFS= read -rd '' 'latest[$(read -rd "" y; echo $y)]'
   3     do :
   4 done < <(find "$dir" -type f -printf '%p\0%Ts\0')
   5 latest=${latest[-1]}

   1 # GNU stat + Bash /w arrays (non-recursive w/o globstar, to the nearest 1s)
   2 while IFS= read -rd '' 'latest[$(read -rd "" y; echo $y)]'
   3     do :
   4 done < <(stat '--printf=%n\0%Y\0' "$dir"/*)
   5 latest=${latest[-1]}

One disadvantage to these approaches is that the entire list is sorted, whereas simply iterating through the list to find the minimum or maximum timestamp (assuming we want just one file) would be faster, however, depending on the size of the job the algorithmic disadvantage of sorting may be negligible in comparison to the overhead of using a shell.

   1 # Bash + GNU find
   2 unset -v latest time
   3 while IFS= read -r -d '' line; do
   4   t=${line%% *} t=${t%.*}   # truncate fractional seconds
   5   ((t > time)) && { latest=${line#* } time=$t; }
   6 done < <(find "$dir" -type f -printf '%T@ %p\0')

Similar usage patterns work well on many kinds of filesystem meta-data. This example gets the largest file in each subdirectory recursively. This is a common pattern for performing a calculation on a collection of files in each directory.

Readers who are asking this question in order to rotate their log files may wish to look into logrotate(1) instead, if their operating system provides it.


BashFAQ/003 (last edited 2018-01-19 22:00:52 by GreyCat)