bugfindutils - Bugs: bug #42164, Confusing min and time...

 
 

bug #42164: Confusing min and time interpretations

Submitter:  None
Submitted:  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:  -email is unavailable-
Open/Closed:  Open Release:  None
Fixed Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Tue 22 Apr 2014 11:51:25 AM UTC, original submission:  

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

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by None (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    No changes have been made to this item

    Back to the top

    Powered by Savane 3.13-d3ae.
    Corresponding source code