the ast find { -atime -ctime -mtime } [-+]N logic was bad
I just fixed it and added regression tests
thanks for the report
you can use the ast tw for intuitive time expressions:
tw -e "mtime>='today'"
where days start at midnight, or you can specify exact times:
tw -e "mtime>='2007-10-01+01:02:03' && mtime<='2007-10-03+03:02:01'"
-- Glenn Fowler -- AT&T Research, Florham Park NJ --
On Wed, 03 Oct 2007 18:19:09 +0200 Henk Langeveld wrote:
> Today I had a support call from a dba complaining about
> solaris 'find . -mtime +1 ' not reporting files older than 24 hours.
> To my surprise (I've been using unix for 20+ years now), the -mtime argument
> has to be interpreted as whole days. It makes sense, and it actually
> make find . -mtime 1 a useful thing to ask.
> However, I did check documentation and the POSIX spec, and looked for
> different implementations, in my case gnu/linux find and UWIN (ast).
> Gnu find conformed to the posix spec (rounding down to whole days),
> but UWIN gave me what our dba expected, files older than 24h.
> I also tested the daystart option, which did not show *any* files.
> ( I had three, one each for noon 10/1, 10/2 and 10/3 )
> $ find . -daystart -mtime +1
> $ find . -mtime +1
> ./m10011200
> ./m10021200
> but this looks like a conflict with the POSIX spec, not ?
_______________________________________________
ast-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-users
