synchronize and timestamps

Advertisement

rec9140
Joined:
Posts:
5

synchronize and timestamps

winscp.com /console mode scripted
V4.2.1 build 428
Win XP PRo
connecting unknown server
SFTP protocol

Is there any way to use the synchronize command with SFTP when you have no ability to set permissions or timestamp. aka "permissions errors"

I may be in a unique position, but the local and remote directories I am sync'ng are going to be empty every day.

From FAQ and posts I found synchronize wants/need to use the timestamp, synchronize works better for me than put, especially since put creates "xxxx.xxx not found" errors when that days directory may be empty, but synchronize does not and the users who review these logs can not handle seeing errors regardless of training. Error means the world has ended to them, period. I then have to waste time to confirm that there was no error just that directory was empty that day.

I tried :

synchronize -nopermissions -notimestamps

No joy.

Any way or chance that synchronize can work similar to put, and only look at the filenames or something?

Thanks in advance.

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
27,253
Location:
Prague, Czechia

Re: synchronize and timestamps

rec9140 wrote:

Is there any way to use the synchronize command with SFTP when you have no ability to set permissions or timestamp. aka "permissions errors"
This issue is being tracked already.

From FAQ and posts I found synchronize wants/need to use the timestamp, synchronize works better for me than put, especially since put creates "xxxx.xxx not found" errors when that days directory may be empty, but synchronize does not
Do not see a reason with put should display errors when target directory is empty.
When source directory is empty, you should not get any errors when you use wildcard instead of specifying explicit name. Like:

put c:\source_directory\*.*    

_________________
Martin Prikryl

Reply with quote

rec9140
Joined:
Posts:
5

Re: synchronize and timestamps

martin wrote:


When source directory is empty, you should not get any errors when you use wildcard instead of specifying explicit name. Like:

put c:\source_directory\*.*    

I'll try that as I had

put *.xxx    

Where xxx is a specific file extension to ensure that is the only file type that gets sent.

Thanks, and I look forward to a resolution on the synchronize as that would make life a lot better.

Thanks.

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
27,253
Location:
Prague, Czechia

Re: synchronize and timestamps

*.xxx should work as well. Can you post a log file and output of the script?
_________________
Martin Prikryl

Reply with quote

Advertisement

You can post new topics in this forum