12:06:28.532 Connected with x.x.x.x, negotiating SSL connection. (For example to set the interval 2,5 hours in CZ = avoiding a lot of problems with timestamp translations). In this case the third option seems me very helpful. I don't know, but I think a lot of people use synchronization like the 'backup'. A lot of the servers know FTP (FTPs) only!! Sure with this third option the online synchronization can be disabled, but it is not need. If the absolute difference between the timestamps will be in the interval, then take the timestamps of both files like the equal.Īll these possibilities should be accessible by all type of connections. The possibility to set the difference time-window (for example from 0 till 999 hours = cca 40 days). It should be possible for ALL TYPES of the connections:ī) Store in UTC timestamp include DaylightĬ) Store in Local timestamp (independent of Daylight)ĭ) Store in Local timestamp include DaylightĬ) Convert to Local convention (independent of Daylight)ĭ) Convert to Local convention include Daylight I think it should be some checkbox (translate back) or ReadyNAS returns stored timestamp till this time. Any FTP servers return UTC timestamp (timestamp which is stored), any servers translate stored timestamp into local time. Im using proftpd 1.3.3g-4 from epel on Centos 6.5 and having issues with the SITE UTIME command. I watched the log and there is the command MFMT to set UTC timestamp after putting the file into FTP. The timestamp on FTP is in UTC format stored. It seems me - for remote FTP (FTPS - TLS) properties is missed the back translation for the timestamp if you load any information from FTP. In Total Commander's FTP client I get properly timestamp in pure FTP mode. These wrong list I get from WinSCP 4.3.4 (interactive and script). Local (stored on NTFS disk, once on FAT32): I tried to synchronize File1.txt and File2.txt. Look bellow on the part of the connection log. 211-Features: SSCN SITE COPY LANG en-US.UTF-8 en-US SIZE PROT CCC SITE MKDIR PBSZ AUTH TLS REST STREAM UTF8 EPRT SITE SYMLINK EPSV SITE UTIME MDTM SITE RMDIR 211 End I think there is a problem with the FTP server, but other servers works with the configuration. It supports FTP and FTPS (over TLS) only.

220 ProFTPD 1.3.3c Server (NETGEAR ReadyNAS)

pathname n214-CPTO pathname n214-UTIME YYYYMMDDhhmmss .

ALL valids both modes - interactive and scripting. ProFTPD modcopy Unauthenticated Copying Of Files Via SITE CPFR/CPTO.

All valids for FTPS (TLS) version and for pure FTP connection. Problem is in the remote timestamp on FTP by the synchronization. I 'discovered' known problem, but therefore I can't use your program which seems me very nice.

Proftpd site utime