Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transfer problem #11724

Closed
cyberduck opened this issue Jul 6, 2021 · 1 comment
Closed

Transfer problem #11724

cyberduck opened this issue Jul 6, 2021 · 1 comment
Labels
bug googledrive Google Drive Protocol Implementation worksforme

Comments

@cyberduck
Copy link
Collaborator

a047070 created the issue

Hello,

I have been using mountain duck since yesterday.

I made a connection with google Drive in "Online" synchronization.
For some files, the synchronization works but sometimes there is a big problem is everything is transferred to AppData \ Local \ Temp and I don't know why.
Sometimes moutain duck seems to sync these files from AppData \ Local \ Temp to the cloud but sometimes it takes a long time.
In addition, it places a heavy demand on my C: \ hard drive.
The problem is that sometimes I will transfer a complete file and it does not appear immediately in the network drive.

Personally I would like it to work as if I were putting a realtime file directly on google drive.

Regards,

Windows Server 2016


Attachments

@cyberduck
Copy link
Collaborator Author

adc75a0 commented

Please try to disable the cache within the Mountain Duck preferences Connection tab. After this, the files shouldn't be copied into the temp directory unless it is necessary (e.g. if an application accesses the file).

If you have any further issues or want to share a log file with us send us an email to support@mountainduck.io

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug googledrive Google Drive Protocol Implementation worksforme
Projects
None yet
Development

No branches or pull requests

1 participant