On Jan 17, 2011, at 11:28 PM, Aaron McCaleb wrote: > Actually, you _can_ sorta use find(1) to find files changed in the > last hour ...or any arbitrary time interval... but it means you have > to use the '-newer <file>' test. That means you have to create a file > with the arbitrary mtime using touch(1).
That's what I meant by "they don't necessarily make it so easy". It is physically possible, yes. > I actually used this, back > in the day, when creating my own incremental backup system. That still doesn't tell you how much data changed within the file, or which parts changed. You still have to do multiple runs with different "-newer" files, and then look at the differences in the output to determine which files were changed within which timeframe. That also assumes that nothing else on the system is mucking about with atime/ctime/mtime values on files. If you were only backing up the differences, what would those differences be? And if it was a binary file, how could you get the list of differences on a block-by-block basis as opposed to a textual mode? It's a first-level approximation, at best. Better than nothing, I'll grant. -- Brad Knowles <[email protected]> LinkedIn Profile: <http://tinyurl.com/y8kpxu> _______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
