Ok, thank you.
- geek569
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.
Topic review
- martin
So it works in the latest version, right? So what is the problem? Do you have a reason to use the old version?
Indeed, the
https://winscp.net/eng/docs/scriptcommand_synchronize#criteria
Indeed, the
-criteria=time,size syntax is new since 6.2.1. In older versions, you need to use -criteria=either:
https://winscp.net/eng/docs/scriptcommand_synchronize#criteria
- geek569
the attached file contains winscp log
- martin
Re: Issue with criteria=time,size
Please attach a full session log file showing the problem (using the latest version of WinSCP).
To generate the session log file, use
/log=C:\path\to\winscp.log command-line argument. 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.- geek569
Issue with criteria=time,size
WinSCP reports
and these files:
local lib.dll with size=433,560 bytes and timestamp1
remote lib.dll with size=433,048 bytes and same timestamp1
the remote file is stored on SFTPGo server
with these args:Nothing to synchronize
synchronize remote -criteria=time,size -transfer=binary -mirror -delete
and these files:
local lib.dll with size=433,560 bytes and timestamp1
remote lib.dll with size=433,048 bytes and same timestamp1
the remote file is stored on SFTPGo server