Hi, maybe this feature already exists, or maybe someone has already asked for, but it should be practical to have the possibility to rename the files into a torrent file, and chose the folder to download it. I have a "download folder", but it works like a temporary dir, I always move and rename the files I download in order to have a clean computer, and to retrieve simply my files. But I would like to seeds for torrents, even if I rename the files I download. Actually, when I move and rename my files, ktorrent considers they have been deleted, and I didn't find how to fix this. Have a nice day, bye

Katen wrote:Hi, maybe this feature already exists, or maybe someone has already asked for, but it should be practical to have the possibility to rename the files into a torrent file, and chose the folder to download it. I have a "download folder", but it works like a temporary dir, I always move and rename the files I download in order to have a clean computer, and to retrieve simply my files. But I would like to seeds for torrents, even if I rename the files I download. Actually, when I move and rename my files, ktorrent considers they have been deleted, and I didn't find how to fix this. Have a nice day, bye

We plan on adding that in the KDE 4 version, currently you can move whole torrents (right click -> set download location), but not individual files.

Actually I am rather interested in the OP's use case. I tend to move my files from the download directory after they're watched, but there are a couple of good reasons to keep them in the torrent client, one being seeding and the other being corrupt file checking. A torrent file is an alternative to keeping an MD5 digest file, and it can even "fix" the files if they become corrupt, by re-downloading that chunk. Although no download lasts forever, so in the long term that part doesn't really work, but the digest is still useful.

I'm not sure if a GUI-based torrent client is really a good idea for super long term storage and seeding. For that I think I'd prefer to use some kind of daemon. But AFAIK there is no daemon which allows the files to be renamed either.

I have been considering custom making myself some kind of tool for managing all this, but I suspect it would probably use symlinks to perform all the magic and have some ordinary torrent client doing the work but pointing at a directory full of symlinks. If I were serious I would get something like RubyTorrent and modify it to allow the files to have different names, and then build on top of that.

looking at the files it could be helpful (in this case) to simply store the MD5 of the finished file and if it is removed/damaged or what have you it can be found and/or fixed. MD5 makes some sense as a few (maybe more) clients include this inside the torrent file and it could be found at creation and copies searched for. Though it could take a lot of time and processor power to check each file on a drive to see if the hashes match.

That's certainly what I do at present, and I back up only the digest lists. So if/when I lose the disk, I have a record of what needs to be re-fetched. I haven't been doing any manual checking lately, as what I'm planning to do is move to a filesystem which is a little smarter about corruption detection (maybe ZFS...)