Hi, so I found the time to test.
Unfortunately, WSCP cannot build up a SFTP-connection since some days to the server, so I can only report its FTP behaviour.
- establish FTP connection
- create 2 directories "test", one locally, one remote
- identify 2 files with timestamp difference and 2 without
- copy those from remote root to remote /test/ and local root to local /test/
- so there were 2 files without timestamp difference and 2, where
timestamp(remote) = timestamp(local) - 1h
- switch on logging
- switch on keep-dir-uptodate, without prior sync an without subdir check
- make a minor edit to one file , dyn.html, which had no timestamp difference
- let the copy process terminate
- stop keep-dir-uptodate
- stop logging
The result of the action was, that
- the modified file had also a timestamp difference as described,
- the unmodified file without prior difference remained untouched,
- the 2 unmodified filed with prior timestamp difference had
the same timestamp difference afterwards.
So it seems WSCP changes the timestamp in the course of updating a local file to the remote site during keep-dir-uptodate operation by subtracting 1 h.
I observed other peculiarities:
1. When I duplicate a file, the timestamp is reduced by 2 h, sometimes by 1 h.
2. When I copied a file from server to local, the timestamp was sometimes
reduced by 2h (before using keep-dir-uptodate), somtimes not and sometimes
it was the copy time (after keep-dir-uptodate).
3. When I copied a file up, the timestamp remained the same before keep-dir-
uptodate, but now it is reduced by 1 h.
So the timestamp behaviour seems very inconsistent to me.
Reply with quote