Thanks, my memory is losing this stuff, I did a search and didn't find it spelt out. Always been a bit worried about using noatime because there is no definitive authority on what it breaks. I use file duplicate detection software and these sometimes check attributes.Update inode access times relative to modify or change time. Access time is only updated if the previous access time was earlier than the current modify or change time. (Similar to noatime, but it doesn't break mutt or other applications that need to know if a file has been read since the last time it was modified.)
Since Linux 2.6.30, the kernel defaults to the behavior provided by this option (unless noatime was specified), and the strictatime option is required to obtain traditional semantics. In addition, since Linux 2.6.30, the file's last access time is always updated if it is more than 1 day old.Use noatime if you don't want it to update atime.I noticed my atimes have been getting updated when I view files yet I am using relatime in fstab. Atimes are showing greater than ctime or mtime which shouldn't happen with relatime.
I think what has changed, which freaked me, is that when chromium has an attachment selection box, the filelist box is now showing atime which I don't think was the case until recently, or is that me also misremembering? pcmanfm still defaults to mtime.
Statistics: Posted by pidd — Tue Apr 01, 2025 8:07 pm