Post a reply

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

bconner

That worked perfectly. Thank you so much!

--Ben
bconner

Oh! Thank you. Will give that a shot in a few minutes. Much appreciated!

--Ben
martin

That does not really show us how the script come to use the /home/users/ben/downloads folder.

Maybe you just need to add that folder to your command?
synchronize local w:\temp\xfer\import /home/users/ben/downloads
bconner

Here's what I have so far:
synchronize local w:\temp\xfer\import

--Ben
martin

Re: Storing relative vs full paths during a sync operation

We need to see your synchronize command.
bconner

Storing relative vs full paths during a sync operation

Hi,
I'm just starting to work with scripting and tried the synchronize local command. That worked very nicely. The only issue I had was the remote server drops me into a folder structure several levels deep and apparently WinSCP was aware of the full path. I need only the relative paths stored on the local side. Is there a way to specify that?
Example:
local workstation: c:\local\
remote ftp server home directory: /home/users/ben/downloads

Resulting files:
c:\local\home\users\ben\downloads\<file a>
c:\local\home\users\ben\downloads\<file b>
etc.
Desired local file path:
c:\local\<file a> etc.

It isn't a show-stopper as I can move the files/folders after the fact, but would prefer not to.

Thanks!

--Ben