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.

Options
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)

Options

Topic review

martin

Re: Timestamp Wackiness on Keep Directory up to Date

Dirk wrote:

Checking with ls on the remote server shows a timestamp of "Apr 7 2005" where all other files show "Apr 7 15:01".

Do you mean 'ls' command on the remote shell? If you do, have you any idea why the server shows no time for the file?

Also can you try SFTP instead of SCP?
Dirk

Timestamp Wackiness on Keep Directory up to Date

Greetings,

First let me thank you for your wondful product, it has already saved me tons of time.

I have been having some problems with the "Keep Remote Directory up to Date" function. At first, it did not appear to be working at all for me. Some research through the boards here have led me to change my Server offset time in SCP settings as my local client runs CST and my server runs GMT. I have "Preserve Timestamp" checked and copy files manually with the expected result, that the server timestamp matches my local one. However, if I turn on "Keep Remote..." and make a change to a local file, WinSCP (correctly) updates the remote file with the new version. However, the interface shows no MM:SS under the "Changed" column, only today's date, and only for that file. Checking with ls on the remote server shows a timestamp of "Apr 7 2005" where all other files show "Apr 7 15:01". Then, changing the local file no longer fires off a update of the remote file.

Not sure if this is a config issue on my side or a "feature" :D

Thanks again for WinSCP