Topic "synchronize and timestamps"

Author Message
rec9140
[View user's profile]

Joined: 2009-05-04
Posts: 5
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.
Advertisements
martin
[View user's profile]
Site Admin
Joined: 2002-12-10
Posts: 24530
Location: Prague, Czechia
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.

Quote:
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:

Code:
put c:\source_directory\*.*

_________________
Martin Prikryl
rec9140
[View user's profile]

Joined: 2009-05-04
Posts: 5
prikryl wrote:

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

Code:
put c:\source_directory\*.*


I'll try that as I had

Code:

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.
martin
[View user's profile]
Site Admin
Joined: 2002-12-10
Posts: 24530
Location: Prague, Czechia
*.xxx should work as well. Can you post a log file and output of the script?
_________________
Martin Prikryl
Advertisements

You can post new topics in this forum






Search Site

What is WinSCP?

It is award-winning SFTP client, SCP client, FTPS client and FTP client integrated into one software program for file transfer to FTP server or secure SFTP server. [More]

And it's free!

Donate

About donations

$9   $19   $49   $99

About donations

Recommend

WinSCP Privacy Policy

WinSCP License