Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!uw-beaver!tektronix!percival!qiclab!sopwith!snoopy
From: snoopy@sopwith.UUCP (Snoopy T. Beagle)
Newsgroups: comp.unix.questions
Subject: Re: "find" and {a,c,m}time
Message-ID: <30@sopwith.UUCP>
Date: 13 Oct 88 16:58:43 GMT
References: <170@libove.UUCP>
Reply-To: snoopy@sopwith.UUCP (Snoopy T. Beagle)
Organization: The Daisy Hill Puppy Farm
Lines: 29

In article <170@libove.UUCP> root@libove.UUCP (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. To wit:

No, probably not. "+n" means more than n, "-n" means less than n,
and "n" means *exactly* n.  (Unless SCO messed with the definition
of n, which I doubt.)

Also note the "-newer" option, if your find(C) [everyone else's find(1)]
has it.  This give you resolution down to the resolution of the mtime
itself, (normally to the second) rather than to a day.  The bad news is
that you are stuck with mtime with -newer, it doesn't let you choose
between all three.  :-(

    _____     
   /_____\    Snoopy
  /_______\   
    |___|     tektronix!tekecs!sopwith!snoopy
    |___|     sun!nosun!illian!sopwith!snoopy