note
andreychek
Or, taking what you said a different way -- the sysadmin, doing the routine nightly backups, could throw the timestamp off too.. leaving you unsure if it was an automated process which touched the file, or a person manually looking at it.<br><br>
Backups, tripwire, the "locate" DB, and several other nightly processes can all interfere with it.<br>
-Eric
114066
114071