Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)


Topic review


Re: Keeping remote directory up to date, timestamp precision only by DAY

Please attach two separate log files showing both the regular upload and the "keep remote directory up to date" (using the latest version of WinSCP).

To generate log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

Keeping remote directory up to date, timestamp precision only by DAY

Have been using WinSCP successfully for many years, but I recently did a full re-install of Windows and now "Keep Remote Directory Up To Date" is not working :(

I am now running the WinSCP 5.7.7 (Build 6257) on Windows 10, and using SCP.

If I drag and drop files within the UI, the timestamps show with MINUTE precision., eg. 20/04/2016 12:01. When I run Keep Remote Directory Up To Date the first time I save (change) a file on the local machine, the file synchronises, but then the precision drops to DAY, eg. 20/04/2016. So no subsequent updates the same day will trigger an update. All I get is "Change in 'C:\.....' detected.

Although I've looked at the documentation, and can't for the life of me find a solution to this problem. Please help as this is driving me nuts.