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

Mountin Duck #11222

Closed
cyberduck opened this issue Oct 31, 2020 · 3 comments
Closed

Mountin Duck #11222

cyberduck opened this issue Oct 31, 2020 · 3 comments
Labels
bug high priority sftp SFTP Protocol Implementation thirdparty Issue caused by third party

Comments

@cyberduck
Copy link
Collaborator

c3f0dd3 created the issue

Hi,

I am currently using 3.1.2 (14611) I use your application to do very large file restores from Exchange.

The issue is you write to c:%USERPROFILE%\AppData\Local\Temp which would normally not be a big deal except for the large files I am working with. You need to add the ability to point to another drive for caching while the application is syncing between source and target. I.E. I have a attached 7TB hard drive I could use. Right now I am testing to see if you are using the Temp variables or just point to the temp path for the current user. Any insight or advice would be helpful as the way things are now your product won't work.

Thank you
Rich

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Milestone renamed

1 similar comment
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Milestone renamed

@cyberduck
Copy link
Collaborator Author

@dkocher commented

We should observe the TEMP environment variable. You can also reduce temporary disk usage by disabling Preferences → Connection → Enable Cache. Please write to [mailto:support@mountainduck.io] for more assistance.

@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 high priority sftp SFTP Protocol Implementation thirdparty Issue caused by third party
Projects
None yet
Development

No branches or pull requests

1 participant