Find files created yesterday (confirmation)

Question

Find files created yesterday (confirmation)

I am looking for a way to find the total size of all files created each working day. Basically to see who and what is taking up all the space on our RAID.

I am using following find command under OSXS 10.4.9:
sudo find . -atime 1 -type f ! -name '*.DS_Store' -exec ** -hs {} ';

From find's man page I deduce that '-atime 1' flag is true for all the files that have been accessed in last 24 hours, but not within last 12 hours (as the time is "rounded up to next full 24-hour period").

Is this correct, as there are a lot of files to go checking.

TIA
C.

MacBook Pro 15" 2.16GHz Intel Core 2 Duo, Mac OS X (10.5)

Posted on Feb 20, 2008 7:38 AM

Reply

Answer 1

Feb 20, 2008 8:05 AM in response to Craig Roberts1

Ok, think I worked out what was puzzling me about the results to date.

I should have used mtime, rather than atime, as it is the modification of files not their access that I am interested in.

Does anyone have a suggestion of how I could actually add the modification date/time to the information retrieved. At the moment the results show:
size <space> relative filename_from.

TIA
C

Reply

Answer 2

Camelot

Level 9

60,595 points

Feb 20, 2008 9:19 AM in response to Craig Roberts1

Does anyone have a suggestion of how I could actually add the modification date/time to the information retrieved.

Since you're including the -f switch in your find statement, find it only going to return a list of files (i.e. not directories), so there's no point in using ** whose main advantage is the ability to calculate the total space used by all the files in a directory.

Instead, consider just switching the -exec to run ls -l instead of ** -hs:

<pre class=command>sudo find . -mtime 1 -type f ! -name '*.DS_Store' -exec ls -l {} \;</pre>

Reply

Answer 3

Feb 20, 2008 10:03 AM in response to Camelot

I imagine that `ls -l` is much quicker than **.

However, I've written a FM Pro dbase to import a text file with results and calc all the different field values from the output of **.

Thanks though.

Reply

Answer 4

Camelot

Level 9

60,595 points

Feb 20, 2008 10:16 AM in response to Craig Roberts1

However, I've written a FM Pro dbase to import a text file with results and calc all the different field values from the output of **.

I don't understand. If you're already parsing the output of **, it shouldn't be hard to change that parser to use ls's output instead - e.g. file size is column 5 instead of column 1, etc.

Reply