5 ms·
There is in fact a default timeout of 5 minutes and you can change it: https://rclone.org/docs/#timeout-time https://rclone.org/docs/#timeout-time I shorten it
by stiff 3y ago
There is in fact a default timeout of 5 minutes and you can change it: https://rclone.org/docs/#timeout-time https://rclone.org/docs/#timeout-time
I shorten it to prevent lockups like you are describing.
- ddeck 3y agoThanks, but unfortunately this doesn't work - for my issues at least. I have this (and conntimeout) set to 15 seconds, but it makes no difference. I tried those based on another user reporting the same issue here: https://forum.rclone.org/t/how-to-get-rclone-mount-to-issue-an-i-o-timeout-after-a-remote-becomes-unavaliable/24220 https://forum.rclone.org/t/how-to-get-rclone-mount-to-issue-... The timeout param is listed as "If a transfer has started but then becomes idle for this long it is considered broken and disconnected". This seems to be only for file transfers in progress. I traced it once, and Rclone gets a "temporary DNS failure" error once the network is down, but just keeps retrying.
- joshspankit 3y agoSounds like you have enough for a decent bug report