Forum » Support and Bug Reports »

Remote file last modified time

Advertisement

myndzi
Guest

Remote file last modified time

WinSCP appears to be setting the modified time of the remote file to my local system's timestamp. Is there any way I can get it to not mess with the timestamp at all? (That is, when it writes the file, the last modified time will be whatever the server assigned it?)

Reply with quote

Advertisement

myndzi
Guest

Ah, thanks. The name seems kind of counterintuitive to me, but I couldn't for the life of me find the checkbox you were referring to until I finally thought to click 'edit' on a specific entry in the transfer presets. Any chance of a global option that will apply to the whole connection so it doesn't need to be changed in multiple places?

Reply with quote

martin◆
Site Admin
martin avatar

myndzi wrote:

Any chance of a global option that will apply to the whole connection so it doesn't need to be changed in multiple places?
It is a global. Or what multiple places do you mean?

Reply with quote

Advertisement

martin◆
Site Admin
martin avatar

myndzi wrote:

I mean, you have to set it for all the transfer setting presets and the default, which is 4 dialogs
Ok, I see. If you actually use (do you?) all the presets, than yes.

Reply with quote

myndzi
Guest

I don't use any of the presets, actually, but they're already there. I don't really know what effect deleting them would have, for example on text file translation between Linux <-> Windows, or other subtle things I may not know about. Actually, I was used to the one-window-per-session layout so I didn't realize that the presets were global until you mentioned it, so thanks :)

Reply with quote

Advertisement

JAFU
Joined:
Posts:
4

Hello!
When move (upload and delete) directory (+subdirs and files) from local to remote - timestamps do not preserved. When copy (upload) timestamps ok (preserved).

WinSCP 6.3.5
File transfer protocol = SFTP-3
Cryptographic protocol = SSH-2
SSH implementation = OpenSSH_7.4
Encryption algorithm = AES-256 SDCTR (AES-NI accelerated)
Compression = No

local: windows 10, ntfs
remote: centos7, ext4

Is it bug or feature?
  • winscp_move_2024-10-25_09-15-37.png (41.44 KB, Private file)
Description: settings

Reply with quote

martin◆
Site Admin
martin avatar
Joined:
Posts:
41,518
Location:
Prague, Czechia

Please attach a full session log files for both scenarios (upload and upload and delete).

To generate the session 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.

Reply with quote

martin◆
Site Admin
martin avatar

Thanks. Though can you specify what timestamp is specifically not updated? The timestamp of the ID_106453_FILE_0.png file?

Reply with quote

Advertisement

martin◆
Site Admin
martin avatar

I do not see any difference regarding the timestamp in the log between the two transfers.
Does the problem occur, when you transfer just a single file (not a folder)?

Reply with quote

JAFU

CORRECTION: timestamp not preserved only on folder AND subfolders, while on files timestamp is preserved.
If move (upload and delete) just a single file - it's OK

Reply with quote

Advertisement

You can post new topics in this forum

Documentation

Support

Associations

Follow Us