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

.meta files somewhere else #343

Open
hboetes opened this issue Oct 18, 2015 · 12 comments
Open

.meta files somewhere else #343

hboetes opened this issue Oct 18, 2015 · 12 comments

Comments

@hboetes
Copy link

hboetes commented Oct 18, 2015

Is it possible to store the .meta files elsewhere? I think they should be stored in the .session dir, not in the download dir.

@alex3kov
Copy link

alex3kov commented Dec 1, 2015

+1, they are clogging download dir.

@chros73
Copy link
Contributor

chros73 commented Dec 2, 2015

What meta files are we talking about? The original one (that was put into watch directory) or the one that rtorrent has been created (inside session directory)?
Have you specified a session directory in rtorrent config?

@hboetes
Copy link
Author

hboetes commented Dec 2, 2015

  • The .meta files, which are created when a magnet url is used.
  • Yes I have a session directory configured.

@omgiafs
Copy link

omgiafs commented Jan 6, 2016

i just run next script by cron:

#!/bin/bash
DIR="ROOT_FOLDER_FOR_ALL_TORRENTS"
find $DIR -name \*.meta -type f -delete

This is workaround, but moving *.meta files elsewhere would be better than my method.

@tobia
Copy link

tobia commented Feb 19, 2016

Can anybody familiar with the source code say if / when it's OK to delete these .meta files?
(the ones created in the download dir when a magnet URL is used)

@hboetes
Copy link
Author

hboetes commented Feb 19, 2016

They are basically torrent files, required to download and check the
torrent. So removing them when the torrent is disabled seems fine. This
actually happens when the torrent actually finished. But in case the
torrent never downloaded in the first place an empty file is created and
that file is never removed. IMHO they should be stored in the .session
directory.

Han

On Fri, Feb 19, 2016 at 7:16 PM, Tobia notifications@github.com wrote:

Can anybody familiar with the source code say if / when it's OK to delete
these .meta files?
(the ones created in the download dir when a magnet URL is used)


Reply to this email directly or view it on GitHub
#343 (comment).

@artyuum
Copy link

artyuum commented Apr 21, 2016

I also think that .meta files should be stored in .session directory.

@rakshasa
Copy link
Owner

This is a change that someone else should easily be able to implement.

Just make a meta torrent dir variable and use session if not set. The time to implement and test is why I'm not doing this, not because I won't accept a patch.

@chros73
Copy link
Contributor

chros73 commented Jul 21, 2016

A.

Just make a meta torrent dir variable and use session if not set.

  1. It's a good idea, but the ideal would be if with some command parameter we can specify their place per torrent (e.g. a watch directory, that we can have more than one), since the downloaded meta file is tied to the torrent (similar way as a torrent file).
  2. Where are these meta files are created in the code? I couldn't find it, neither in rtorrent nor in libtorrent project.

B.

  1. There is a bug (probably it was a feature at some point :) ) in the produced meta file: it doesn't include info part, it starts with files straight away. The result is an invalid file, e.g. lstor from pyrocore can't process them.
  • currently: d5:filesld6:length
  • correct way: d4:infod5:filesld6:length
  1. Is it possible to include tracker info (if there's any) in these meta files?
    It'd be perfect in this way:
  • if there's tracker info then include it and use .torrent extension (we get a full valid torrent file)
  • if there isn't: then use .meta extension (as it is now, with the above fix)

@rakshasa
Copy link
Owner

rakshasa commented Aug 2, 2016

Meta files are just normal torrents that rtorrent creates, except they have a metadata variable set. (in loading of torrents iirc)

There's some special handling done in libtorrent too iirc, however just start from the point where rtorrent is passed a magnet link to load, and do some grep'ing of the variables it sets.

@Feriman22
Copy link

Hi,

This issue is still existing and should be store these *.meta files in session folder.

Is there any solution since last commment in this thread?

Thanks!

@chros73
Copy link
Contributor

chros73 commented Jul 20, 2019

This issue is still existing and should be store these *.meta files in session folder.

Here's a workaround that I use in my setup, but helper commands are all over place, so you can't just copy-paste the block.
And this is the simplified version of the above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants