URL:
<http://savannah.gnu.org/bugs/?42164>
Summary: Confusing min and time interpretations
Project: findutils
Submitted by: None
Submitted on: Tue 22 Apr 2014 11:51:25 AM UTC
Category: find
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Originator Name: Mike Nagie
Originator Email: promike1...@gmail.com
Open/Closed: Open
Discussion Lock: Any
Release: None
Fixed Release: None
_______________________________________________________
Details:
Hi all!
We have found recently a bug in find command.
*min should represents the minutes and *time the days.
For example (on Arch linux) :
touch today ; find . -mtime 0 will find it because 0 means today.
result: ./today
touch today ; find . -mtime -1 should mean the same, just like the result:
./today
touch today ; find . -mtime +1 doesn't find it, because this searches
older than 1 day files
NOW, the problem is with the *min
touch now ; find . -mmin 0 and the result is nothing.
touch now ; find . -mmin 1 found it now.
(however on BSD: touch now ; find . -mmin 0 result: ./now)
So the problem is:
find something that is older than 1 day is find . -*time +0
find something that is older than 1 minute is find . -*min +1
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?42164>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
