Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#3422 closed Enhancement (invalid)

Migrate torrent from one client to another

Reported by: Xake Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version:
Severity: Normal Keywords:


What I really miss sometimes is the possibility to migrate a torrent from one instans of transmission to another. As example here comes a use case:

I download (or start download) a torrent on my laptop, but for different reasons (unstable wireless network, out of battery) I do not want to finish the torrent at that time on said laptop. In my home I have transmission-daemon running on one computer. So when I come home I plug my laptop into my local lan, I start transmission on the laptop and tell it to migrate the torrent to my seedbox running transmission-daemon. When the process is done the torrent is being finished on the seedbox, and the laptop have no leftovers from the torrent (unless you specify to keep a local copy of the files from it).

I do not know how plausible this is whith current bittorrent standards, but it would be an awesome feature.

Change History (2)

comment:1 Changed 12 years ago by charles

  • Resolution set to invalid
  • Status changed from new to closed

All you have to do is copy the torrent's data, and the two config files for the torrent from ~/.config/transmission/torrents/torrentname.torrent and ~/.config/transmission/resume/torrentname.resume

comment:2 Changed 12 years ago by Xake

So to get this to work I had to:

  • manually copy said files to the seedbox,
  • ssh into the seedbox and copy the files to the right place and give them the right permissions,
  • restart transmission-daemon
  • $ transmission-remote -t <torrentnr> --find <path-to-data>
  • $ transmission-remote -t <torrentnr> -v # this step I am actually not so sure if needed
  • $ transmission-remote -t <torrentnr> --start

This was actually I guess what I hoped for getting automated, maybe without the need of restarting transmission-daemon...

But thanks anyway, your pointers at least told me this is possible and scriptable.

Note: See TracTickets for help on using tickets.