|
From: | David Huffman |
Subject: | [bug #14991] mtime documented incorrect or bug? |
Date: | Wed, 16 Nov 2005 21:22:51 +0000 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc3 Firefox/1.0.7 |
URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=14991> Summary: mtime documented incorrect or bug? Project: findutils Submitted by: bigredradio Submitted on: Wed 11/16/05 at 21:22 Category: find Severity: 3 - Normal Item Group: Wrong result Status: None Privacy: Public Assigned to: None Originator Name: Originator Email: Open/Closed: Open Release: 4.1.20 Fixed Release: None _______________________________________________________ Details: Using the command argument -mtime with gnufind (4.1.20) I have found that files that are 25 hours old will not be listed in a find with -mtime +1. From my understanding +1 would result in files older than 1 day (24 hours). mtime 1 would be exactly 24 hours old (to the second) and -1 would be files that are less than 24 hours old. The documentation states that 1 means between 24-48 hours. Does this mean that +1 is greater than 24 hours? However it appears that +1 will only find files that are 72 hours old or older. I have tested the find command using watch and a file was not found using -mtime +1 until 72 hours (to the second) old. _______________________________________________________ Carbon-Copy List: CC Address | Comment ------------------------------------+----------------------------- address@hidden | _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=14991> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |