Path: utzoo!attcan!uunet!husc6!bloom-beacon!bu-cs!purdue!decwrl!pyramid!oliveb!intelca!mipos3!merlyn
From: merlyn@intelob.intel.com (Randal L. Schwartz @ Stonehenge)
Newsgroups: comp.unix.questions
Subject: Re: "find" and {a,c,m}time
Message-ID: <3013@mipos3.intel.com>
Date: 11 Oct 88 22:46:06 GMT
References: <170@libove.UUCP>
Sender: news@mipos3.intel.com
Reply-To: merlyn@intelob.intel.com (Randal L. Schwartz @ Stonehenge)
Organization: Stonehenge; netaccess via BiiN, Hillsboro, Oregon, USA
Lines: 34
In-reply-to: root@libove.UUCP (Jay M. Libove)

In article <170@libove.UUCP>, root@libove (Jay M. Libove) writes:
| 
| My manual entry for find(C) (SCO uses bogus manual sections, that should
| be find(1) to the real world I think) says:
| 
| find pathname-list expression
| ...
| -atime n	True if the file has been accessed in n days.
| -ctime n	True if the file has been changed in n days.
| -mtime n	True if the file has been modified in n days.
| 
| Okay, so "find -?time 3 -print" should find all files ?'d within the
| last three days, right? Nope. 

Right.  Nope.  As it says in TFM (Ultrix, but you can translate...)...

"In the descriptions, the argument n is used as a decimal integer
where +n means more than n, -n means less than n, and n means exactly
n."

Yup.  Can you guess the correct response?  Try:

  find <wherever> -?time -3 -print
                         ^
                         +====== this was missing

I know, 14 other people are typing in this reply at this very moment.
Oh well.
-- 
Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095
on contract to BiiN Technical Information Services (for now :-),
in a former Intel building in Hillsboro, Oregon, USA
<merlyn@intelob.intel.com> or ...!tektronix!inteloa[!intelob]!merlyn
Standard disclaimer: I *am* my employer!