[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #38899] Find by Last Access Time Actually Modifies the Last Access
[bug #38899] Find by Last Access Time Actually Modifies the Last Access Time by Itself
Sun, 02 Jun 2013 12:29:43 +0000
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.93 Safari/537.36
Update of bug #38899 (project findutils):
Status: None => Invalid
Assigned to: None => jay
Open/Closed: Open => Closed
Follow-up Comment #2:
find reads directories, so on a file system with Unix semantics, it is
expected that the access time is updated.
If find is modifying the access time of (non-driectory) files, then that is
unexpected (for filesystems which are supposed to have Unix semantics,
find doesn't open files, apart from files associated with actions -fprintf,
-fprint, and system configuration files such as /etc/fstab and /etc/passed.
Hence file access times shouldn't be updated.
Since you're running find on Windows XP, you should start by talking to the
GnuWin folks about why this is happening I think (this doesn't happen on
filesystems with real Unix semantics). For now I'm going to mark the bug as
not-valid, but if it turns out to be a bug in find rather than GnuWin, please
feel free to re-open the bug.
Reply to this item at:
Message sent via/by Savannah
|[Prev in Thread]
||[Next in Thread]|
- [bug #38899] Find by Last Access Time Actually Modifies the Last Access Time by Itself,
James Youngman <=