(At least it is on my Mac.) If not this is the only place I see where you might be able to sort by date/time stamp, assuming it's not changing constantly like on my system.Īlso looking at the contents of the /Users/$USER/Library/Application Support/AddressBook/AddressBook-v22.abcddb file, the SQL Database used by Contacts, there is no field that holds a date/time stamp. You can look at /Users/$USER/Library/Application Support/AddressBook/Metadata and see the date/time stamp gets updated on all of them and checking Get Info you'll see the date/time stamp for both created and modified are the same. The new inode is how you can tell that the file was replaced, rather than simply having its contents changed.Īs for why this isn't working for you, I have no idea.You did not state what OS X or iOS version and my reply is base on my system, MacBook Pro Retina, 15-inch, Early 2013 running OS X 10.8.5, and I don't believe you can as the date/time stamp, both created and modified, on the datastore for Contacts is constantly changing each time Contacts is opened. So did the inode number - basically an identifier of which file it is on the disk - has changed. this is not showing the problem you're seeing), the modification date has changed. Note that the creation date is the same (i.e.
Then I changed the file in Word, saved again, and repeated the stat command: $ stat -f 'inode: %i, create: %SB, mod: %Sm' test.docx
I created a new file in Word, then checked its stats with the stat command: $ stat -f 'inode: %i, create: %SB, mod: %Sm' test.docx Here's an example of how it's supposed to work. It may be that this step - basically faking the creation date of the new file - isn't working for some reason on your system. But normally, the save process will copy the creation date from the old file, and set the new one's creation data the same. This means that the new file actually was created when the changes were saved. The net result is that, while it looks like the file was only modified, it was actually replaced by a similar-looking but actually completely new file. Basically, they save the new data in a new file under a temporary name, then delete the original file & rename the temp file into its place. To avoid problems if an error occurs partway through saving a document, many programs use some sort of "safe" or "atomic" safe process. I cannot reproduce the problem, but I may be able to explain it.
0 kommentar(er)
