Timeout for unavailable SMB share takes minutes

[Peekstra]

One of my synchronization jobs tries to push some files from my to PC to two multimedia boxes. Both of them run Debian and their local storage is accessed via an SMB share. However, one of them is often not powered on when I'm running the job. This used to be no problem because it quickly continued after a short timeout when trying to access that unit(30 seconds?). However in more recent versions of FreeFileSync the timeout seems to have been increased to several minutes (5m?)

I understand that this may be needed in some scenarios (SFTP?) but in my home environment this seem to take forever. Is there anything what I can do to change this timeout? I couldn't find it in the options but maybe I overlooked something. If it's not possible to change this I hope that a future version makes this possible.

[therube]

(Aside from anything FFS may be able to do, if you were to run a shell script to test for the share(s), then have that run 1 of 2 FFS different .ffs_batch depending on what is or is not available...)

[Peekstra]

Thanks, that would be a workaround. I hope though that the current timeout can be reduced to a more reasonable value in a future release (assuming that this is some kind of timeout counter).