honzakuchar wrote:

I'm still receiving this error message. Are you considering to fix this or are there any unexpected problems?

Can you be more specific?

I'm still receiving this error message. Are you considering to fix this or are there any unexpected problems?

Thanks for your feedback.
I'll consider it.

I'm genuinely sorry for these multiple posts, but I'm really just discovering these problems gradually. I probably should have made an account.

I just noticed that monitor is even more annoying than I thought, because I hit CTRL+S way more often than I am aware of. So when I finally check the WinSCP window to dismiss the permission error warning, WinSCP has queued all those changes in the same file and I have to get rid of the error a dozen times, just for one file to be updated (because the updated version will be uploaded for every change I made in the past).

Sorry again for the triple post.

I just noticed that the monitor function (Keep remote directory up to date) has the same issue. It's actually even worse, because (as opposed to the synchronization dialog) it doesn't even notify me that my Transfer settings can't be used. Plus, it's even more pointless to use the monitor function if I have to get back to WinSCP for every single file and click "Okay" on the "set times: Operation not permitted" dialog. At the same time, it's even less likely for the monitoring to fail without those permissions, because every change in the relevant files will be uploaded immediately. Hence the timestamps should be very close at all times - even if we can't "preserve timestamps".

So both for monitoring and synchronization, please add an option to turn off "preserve timestamps" :).

Martin

Hi there,

I think it would be very convenient if we would be able to switch off "preserve timestamps" for Synchronization, even if it's done by timestamp comparison.

I've researched this a bit and found this reply from a few years ago: https://winscp.net/forum/viewtopic.php?p=15116#15116

It says synchronization won't work if the feature is disabled. That's why it's enforced. However, my server won't let me modify timestamps (because my SCP user is not the file owner). Still synchronization works perfectly (for me). Of course, if I get a local file that is newer than the last sychronized version, but older than the last sychronization, this file won't be synchronized. But this really never happens for me. So I would benefit a lot from disabling the feature, because this way I have to sit there through the whole synchronization process and click "Okay" over and over again.

So basically I'm making a case for the fact that synchronization by timestamps DOES work (for me) if I can't preserve timestamps.

Switching comparison criteria from timestamp to size is not an option, because fixed typos won't be synchronized, and sometimes I already have a newer version on the server, that differs in size from the older one... so just checking size would overwrite the new file.

I'm aware that disabling this feature might stop synchronization from working in 100% of the cases. But it would still be nice to give the user control over it, because the few exceptions don't affect me (and I imagine a lot of other users). Throw a big red warning if "Preserve timestamps" is switched off and people want to synchronize by timestamp - but please make it possible! :)

Cheers,
Martin