i have a group of files in a directory that i sometimes need to update... since i need to go thru all of them & may do it over a period of days or even weeks, when I'm done i often use a win32 console version of the unix touch command to update the date/time stamp on an edited file to some time in the future. This makes it easy to see which ones I still need to update -- the ones that don't have the same time stamp.
so anyway, i edited one file & it synced to another PC (i don't sync these to the desktop). Then i touched it & set it to June 1, 2009 12:01:00am. The update to the timestamp never synced. Should it? isn't that metadata, & i've read LM will always sync metadata on mp3 files, for instance? Very annoying, but as long as the contents always get synced when they differ... i verified a checksum with MS' own fciv.exe and the files are the same. In the end that's what matters.
so here's where it gets weird: i edited another file & touched it BEFORE it ever synced. So it never did -- we're now @ 3 days later, just noticed it when i got on the other PC. I thought LM synced based on a hash of files to determine if they're identical, not simply a timestamp? If i'm correct in that it hashes, it would seem to be a bug. I could see how it doesn't even run a hash unless the timestamps are different, but in this case it is -- just in the future, not the present or past.
this should be easy enough to duplicate... i will upload logs later, no time right now.
When you do get the bug filed with logs, please post a link to the bug here. I can't answer you on the mechanics of the sync process, but I do believe that it is date driven. The fact that you are setting the date to a future date may be confusing Live Mesh. -steveMicrosoft MVP Windows Live / Windows Live OneCare & Live Mesh Forum Moderator