`Find`ing with finer granularity than 1 day

[Adam S. Moskowitz]

It came up the other day that there doesn't seem to be an easy way to find
files based on their modification time if what you care about is files
modified within the past 2 hours. Sure, "find ... -mtime 1" would get them,
but it would potentially get lots of other files too.

The way we solved the problem was to create a temporary file with touch,
thus setting it's mtime to the correct time, and then using the "-newer"
switch. That seemed rather inelegant to me so I was wondering if it would be
worth modifying find to understand either hours & minutes or absolute times
(or both). Or, would it be better to write a hack that find could call via
"-exec" to do the comparison we need?

I'd say send email & I'll summarize, but I think this one's worth discussing
"in public."

AdamM
-- 
"OSI: Same day delivery in a nanosecond world."           | Adam S. Moskowitz
                                                          | adamm at necis.nec.com
                                                          | ...!uunet!harvard!\
Van Jacobson (on a T-shirt)                               |  necntc!necis!adamm