Re: Cyberduck doesn't send complete files
Re: Cyberduck doesn't send complete files
- Subject: Re: Cyberduck doesn't send complete files
- From: Dan Doughtie <email@hidden>
- Date: Wed, 19 Nov 2008 10:35:06 -0500
- Thread-topic: Cyberduck doesn't send complete files
Dana:
Thanks. Skeeve¹s suggestion worked really well (using the Shell Script). I
wanted to use Cyberduck because the users that need this all have it and in
a pinch they could manually do it. I¹m testing one with a CURL script right
now as a fall back. The problem with CURL is that some servers block HTML
based ftp and/or posts. But in this case I don¹t that that will happen.
Using Cyberduck gives me lots of options I would like to expand into .
Dan
On 11/19/08 9:39 AM, "Dana Hill" <email@hidden> wrote:
> Sorry, Dan. I meant to send my original email to the entire list! It's early
> here on the east coast!
>
> I use Cyberduck extensively in my publishing workflow and I am very interested
> in your 'final solution'. I also did a bit of research about your .zip
> question from yesterday. I found some possibly relevant information on
> macosxhints.com. Some posts were fairly old, circa 2003 and 2005, but the
> referenced shell scripts should still work. Below is a URL for one of the
> possible solutions:
>
> http://www.macosxhints.com/article.php?story=20050902030458181
>
> Dana
>
> On Nov 19, 2008, at 8.26 AM, Dana Hill wrote:
>
>> Can you get info for the local item to get its size and incorporate a loop
>> to get info for the remote file and disconnect when they are the same size?
>>
>> On Nov 19, 2008, at 4.34 AM, Dan Doughtie wrote:
>>
>>> I have a fairly simple script that follows Cyberduck's own Applescript
>>> examples. It is moving ZIP files . On my home network it moves the complete
>>> files (often 1 or 2 megs) to the FTP site. But on the company network I get
>>> ZIP files delivered that are much smaller and can¹t be unzipped because they
>>> aren't complete. I assume that the script isn¹t waiting for Cyberduck to
>>> finish the transfer before moving on to the next step which is disconnect
>>> then quit.
>>>
>>> I added a delay and it seems to have increased the file size but they still
>>> are the original size and won¹t open.
>>>
>>> Is there something that can force Cyberduck to wait for the transfer to
>>> complete? I can keep increasing the delay but then I run the risk of
>>> unnecessary waiting around when the process completes quicker than expected.
>>> I might just give up and use CURL in a command line script.
>>>
>>> Here's the script
>>>
>>> set theServer to "ftp.xxxx.com"
>>> set theUser to "xxxx"
>>> set thePass to "xxxx"
>>> set theProtocol to "ftp"
>>> set theUploadFolder to "PC"
>>> set myoutputFile to myoutputFile as alias
>>>
>>> with timeout of 300 seconds
>>> tell application "Cyberduck"
>>> set theBrowser to (make new browser)
>>> tell (theBrowser)
>>> --set encoding to "UTF-8"--I assume I don't need this since I'm
>>> moving ZIP files
>>> connect to theServer with protocol theProtocol as user theUser
>>> with password thePass with initial folder theUploadFolder
>>> upload item myoutputFile
>>> --I added this delay and it seemed to grow the file size.
>>> delay 5
>>> disconnect
>>> end tell
>>> quit
>>> end tell
>>> end timeout
>>>
>>>
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> AppleScript-Users mailing list (email@hidden)
>>> Help/Unsubscribe/Update your Subscription:
>>> om
>>> Archives: http://lists.apple.com/archives/applescript-users
>>>
>>> This email sent to email@hidden
>>>
>>
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden