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

Previous downloads cached? #408

Closed
btmdave opened this issue Aug 24, 2015 · 5 comments
Closed

Previous downloads cached? #408

btmdave opened this issue Aug 24, 2015 · 5 comments

Comments

@btmdave
Copy link

@btmdave btmdave commented Aug 24, 2015

Is there a cache for previous downloads? I downloaded a torrent, killed node, removed the directory from disk, but when i re-download the same one, it's goes to done right away and the full file(s) are there.

@btmdave

This comment has been minimized.

Copy link
Author

@btmdave btmdave commented Aug 24, 2015

In some cases it goes straight to done, but the files are zero bytes (for different previous downloads i killed partially through).

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Aug 30, 2015

If you don't specify a path option with webtorrent --path <path>, then a temporary path at /tmp/webtorrent is used. If you re-run WebTorrent than that previously downloaded data can be reused.

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Aug 30, 2015

@btmdave

Can you elaborate on your second comment? Are you saying that if a torrent was previously downloaded successfully that later downloads with --out <path> won't actually download anything to the given path?

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Jan 9, 2016

Closing this issue – it's so old that the parameter is now named --out.

@feross feross closed this Jan 9, 2016
@lock

This comment has been minimized.

Copy link

@lock lock bot commented May 4, 2018

This thread has been automatically locked because it has not had recent activity. To discuss futher, please open a new issue.

@lock lock bot locked as resolved and limited conversation to collaborators May 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.