[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: find -amin bug
From: |
Dave Saunders |
Subject: |
Re: find -amin bug |
Date: |
Tue, 11 Mar 2003 13:11:39 -0500 (EST) |
Sorry for omitting this--I'm on a solaris 2.8 system
SunOS ... 5.8 Generic_108528-14 sun4u sparc SUNW,Ultra-2
using the gnu gcc 5.8 complier.
Dave Saunders
On Tue, 11 Mar 2003, Dave Saunders wrote:
> Folks,
> I am trying to use the -amin option in 'find' to look at anything older
> than 8 hours (480 mins).
> My command is:
>
> find . -name "somename" -amin +480 -print
>
> But I keep coming up with nothing.
>
>
> Looking at your docs, I see this:
>
> - Test: -amin N
> - Test: -cmin N
> - Test: -mmin N
> True if the file was last accessed (or its status changed, or it
> was modified) N minutes ago. These tests provide finer
> ^^^^^^^^^^^^^
> granularity of measurement than `-atime' et al. For example, to
> list files in `/u/bill' that were last read from 2 to 6 hours ago:
> ^^^^^^^^^^^^^^^^
>
> find /u/bill -amin +2 -amin -6
>
> (The documentation is not consistent with respect to time units.)
>
>
> When I use -amin +420 (7 hrs), I get the expected count. When I use
> -amin +480, I get no hits.
>
> When I try '-amin +480 -amin -1440' (in the spirit of the example), I also
> get no hits.
>
> Dave Saunders
> UVa
>
>
>
- find -amin bug, Dave Saunders, 2003/03/11
- Re: find -amin bug,
Dave Saunders <=