martin wrote:
Thanks. Are you able to reproduce the same problem with WinSCP application (not the FAR plugin)?
I have played with few servers I came to conclusion, that it is a matter of misconfiguration, but I was not able to locate the source of the problem. Suppose I have
server1 (SuSE) and
server2 (Debian), both are set "Adjust remote timestamp with DST (Windows)" option in session settings for WinSCP.
The experiment is:
- Take any file (install.cmd in my case) and copy it to remote server.
- Report the timestamp of the remote file
- Try to overwrite the file and report the timestamp, as seen to WinSCP.
Interesting that for
server2 the remote timestamp is OK, but WinSCP probably makes the wrong translation when it is reported back. I have checked the behaviour both for Far Plugin and WinSCP standalone: they both behave the same way. If you need additional information of the top of what I supply below - let me know.
For
server1 I got:
server1:~> ll install.cmd
-rw-r--r-- 1 u4412 users 94 Apr 26 21:02 install.cmd
server1:~> date
Tue May 4 12:25:24 CEST 2010
server1:~> date -R
Tue, 04 May 2010 12:25:50 +0200
server1:~> rpm -qa | grep ssh
openssh-4.2p1-18.36
Remote file 'install.cmd' already exists. Overwrite?
New: 94 bytes, 26/04/2010 21:02:56
Existing: 94 bytes, 26/04/2010 21:02:56
For
server2 I got:
server2:~$ ll install.cmd
-rw-r--r-- 1 dk users 94 Apr 26 21:02 install.cmd
server2:~$ date
Tue May 4 12:21:56 CEST 2010
server2:~$ date -R
Tue, 04 May 2010 12:22:11 +0200
server2:~$ dpkg -l | grep ssh
ii openssh-server 1:5.1p1-8
Remote file 'install.cmd' already exists. Overwrite?
New: 94 bytes, 26/04/2010 21:02:56
Existing: 94 bytes, 26/04/2010 22:02:56