Timeline for `cat` affects last `Access` time but not last `Change` time
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2022 at 13:53 | history | edited | dr_ |
edited tags
|
|
| Oct 7, 2022 at 13:51 | answer | added | dr_ | timeline score: 1 | |
| Oct 7, 2022 at 13:16 | comment | added | jesse_b | It doesn't say changing any inode information and it also says "setting inode information" When the last access time is updated you are not setting it, the system is. Again, if it behaved the way you expect it to it would be a bug and would completely negate the purpose of access vs change. | |
| Oct 7, 2022 at 13:14 | comment | added | Franklin Pezzuti Dyer | @jesse_b Is "last accessed" data not part of the inode information? | |
| Oct 7, 2022 at 13:12 | comment | added | jesse_b |
(i.e., owner, group, link count, mode, etc.) If accessing a file modified it's last changed timestamp that would be a bug.
|
|
| S Oct 7, 2022 at 13:11 | review | First questions | |||
| Oct 13, 2022 at 7:02 | |||||
| S Oct 7, 2022 at 13:11 | history | asked | Franklin Pezzuti Dyer | CC BY-SA 4.0 |