transferring files using the wild * character from a folder

All about using TurboFTP. Exchange your use experience or post questions/problems here.

Moderator: idler

transferring files using the wild * character from a folder

Postby ranchodeluxe » Fri Jan 12, 2007 6:24 pm

I am trying to transfer the contents of a folder. But not the folder. Because the file name in the folder changes every day. So I will be transferring a different file every day. I am transferring a single file and I specify the file name. This is what my queue file (tbx) looks like:

C:\Test\Data\test.txt 140 -> / xxx.xx.xx.xx:22

And this works just fine. The file transfers without any problems. See below:


STATUS:> Crypto negotiation done, server to client using aes192-cbc, client to server using aes192-cbc
STATUS:> Login successful.
COMMAND:> Resolve path '.'
/
COMMAND:> Resolve path '/'
/
COMMAND:> LIST remote dir '/'...
List done
STATUS:> Sending C:\Test\Data\test.txt
Transfer done
STATUS:> 140 bytes sent in 00:00:00 (0.153 Kbytes/sec)
STATUS:> Successfully sent C:\Test\Data\test.txt
STATUS:> Queue transfer completed on Fri 10:58:29 AM 1/12/2007
STATUS:> 1 files totaling 140 bytes transferred in 00:00:01 (0.087 Kbytes/sec).
STATUS:> Notification Email successfully sent to kbalimtas@global-express.net.
STATUS:> Disconnected: 198.57.19.94 - Fri 10:58:30 AM 1/12/2007


But, when I do use the wild character * so that any filename with txt extension can be transferred and I get this:


C:\Test\Data\*.txt 140 -> / xxx.xx.xx.xx:22


It connects and says transferring but will not transmit or disconnect until I disconnect manually and the file is not in remote. Then I tried this:


C:\Test\Data\*.txt 0 -> / xxx.xx.xx.xx:22


Same thing. It connects and says transferring (sending) but will not transmit or disconnect until I abort manually (I waited about 10 minutes) per below:


STATUS:> Crypto negotiation done, server to client using aes192-cbc, client to server using aes192-cbc
STATUS:> Login successful.
COMMAND:> Resolve path '.'
/
COMMAND:> Resolve path '/'
/
COMMAND:> LIST remote dir '/'...
List done
STATUS:> Sending C:\test\Data\*.txt
STATUS:> Aborting...
STATUS:> Aborted


Then I reverted back to my single file transfer and it work just fine again. See below:


C:\Test\Data\test.txt 140 -> / xxx.xx.xx.xx:22


STATUS:> Crypto negotiation done, server to client using aes192-cbc, client to server using aes192-cbc

STATUS:> Login successful.
COMMAND:> Resolve path '.'
/
COMMAND:> Resolve path '/'
/
COMMAND:> LIST remote dir '/'...
List done
STATUS:> Sending C:\Test\Data\test.txt
Transfer done
STATUS:> 140 bytes sent in 00:00:00 (0.153 Kbytes/sec)
STATUS:> Successfully sent C:\Test\Data\test.txt
STATUS:> Queue transfer completed on Fri 10:58:29 AM 1/12/2007
STATUS:> 1 files totaling 140 bytes transferred in 00:00:01 (0.087 Kbytes/sec).
STATUS:> Notification Email successfully sent to kbalimtas@global-express.net.
STATUS:> Disconnected: 198.57.19.94 - Fri 10:58:30 AM 1/12/2007


You can transfer files using wild * characters, correct?

Any ideas? Thanks.
ranchodeluxe
 
Posts: 2
Joined: Fri Jan 12, 2007 6:10 pm

Postby ranchodeluxe » Fri Jan 12, 2007 6:38 pm

Ok. Instead of using queue I used sync service and I can specify * wild characters and that did work. It transfers and also it deleted my file on local folder which is exactly what I wanted.
ranchodeluxe
 
Posts: 2
Joined: Fri Jan 12, 2007 6:10 pm

Postby admin » Sat Jan 13, 2007 10:16 pm

Hi,

If you use wildcard in the transfer queue you need to use ->> and <<- to indicate the transfer direction. You can use the Download As or Upload As context menu command to insert an entry with wildcard.

Additionally you can read this KB for further info about transferring a folder:

http://www.tbsoftinc.com/support/index. ... 21&nav=0,4


Regards,

Leon
admin
Support Staff
 
Posts: 266
Joined: Mon Jul 11, 2005 1:24 am


Return to Using TurboFTP

Who is online

Users browsing this forum: No registered users and 1 guest

cron