[sub]

Are you assuming that Yummy doesn't examine the sub folders? How many files and folders are there contained within the entire folder hierarchy of your server(s)? I bet it's a lot more than 600, or even 1100, right?

Certainly, 600 or 1100 file compares with Yummy will be completed within a few seconds, so it must be that your server(s) have a lot more files to process than that.

If you only want Yummy to compare the current folder (ie not compare sub folder contents) the un-check the 'Process sub-directories' checkbox in the Synchronize setup window.

For example, you could be trying to download a file from a busy site where a limited number of simultaneous clients are allowed.

In the case of the original poster, he sited a flaky connection as being the cause of the retries.

Thanks again!!!

Keep an eye open for another free update coming soon ...

Just to follow up for those of you who are following this thread, Reddog99 confirmed by email that the reconnection failure has disappeared after setting the maximum retries to unlimited and using the latest build of Yummy FTP.

To follow up for those reading, cdeath sent me a screenshot. It looks like Yummy is receiving garbled listing data from the server - I don't know why this is but it appears to be directly related to version 3.6.1p2-18 of OpenSSH. This ties in with the fact that I have never had a report like this before, so it must be a very rare case. cdeath is attempting to obtain a test account for me to have a look.

Yes, please send a screenshot via email to me. Also, is there any chance I can make a test connection? If so, I'll be able to fix the problem very quickly, I'm sure - please send me the connection details if this is ok: support at yummysoftware dot com

Glad you like it, KanaomiSS

If the alert said that Yummy had attempted a certain number of retries then setting unlimited retries will of course fix the problem, but since you didn't mention if that was stated in the alert I can only assume it wasn't. In this case, setting it to unlimited retries won't make a difference.

That said, I'm afraid there's a bug in 1.5.1 which causes unlimited retries to stop after 101 retries. I've already fixed this in the latest build and I'll email you the link to download it.

Let me know...

-Jason

Hi Pat,

The automatic retry mechanism is not kicking in here because the failure is deemed to be compete - ie. no connection to the Internet.

I can't find that exact error message anywhere in Yummy, though. Could you please let me know the exact message and I'll specifically add this instance as a place where the automatic retry *can* take over. Once that's done I'll send you a newer build and you should be good to go.

Thanks!
-Jason

1) Click the item to select it
2) Click on the text of the item and do not move the mouse
3) Editing will start

Ok here's what I did:

I made use of the 'Edit With' menu - each entry in that menu now has a keyboard shortcut, starting with Cntrl-Cmd-0 through Cntrl-Cmd-9

So, now you can have up to 10 alternative editors available at your fingertips.

Good? 

I didn't change anything I guess what you've described is simply a 'feature' of the Marquee list selection option, which is (as you probably guessed) provided by the OS's file browser control.

For what it's worth, version 1.5.2 beta handles this situation gracefully.

The "...and upload .DS_Store files" option has been changed to "...and include .DS_Store files" in version 1.5.2 beta, and this will address the issue you have been having.

Yep, the data connection is established only when file listing data or file data need to be transferred. The control connection remains connected at all times and is used to send commands to the server and receive replies.

The very fact that there is a reply from the server would indicate that a connection is being established, so I don't think there is a proxy problem here, otherwise there would likely be no connection at all. Actually, I think kiki only mentioned web proxies, in any case. But the change to the Passive FTP setting is a little odd.

Let's see...