seedsync
seedsync copied to clipboard
ipsingh06
grabs torrent files before torrent finishes downloading
Seedsync pulls down incomplete files because it is starting before the torrent finishes.
Can this be resolved by changing interval scan times? What if the interval time comes around again when the files aren't completed again
How I and many others use SS is to use file automation on the seedbox, let's take rtorrent.
After the download finishes RT can be set to move the downloads to a new folder. It's this new 'sync' folder that you would have setup in SS to download from. That way SS only dl's complete files.
With rTorrent you can also set it to not just move the files but rather hardlink instead. This makes sure you don't chew up drive space as it isn't duplicating the data. It also means that your are free to delete the files you've transferred using SS (from that new 'sync' folder) as the files that are seeding are still on the seedbox.
How I and many others use SS is to use file automation on the seedbox, let's take rtorrent.
After the download finishes RT can be set to move the downloads to a new folder. It's this new 'sync' folder that you would have setup in SS to download from. That way SS only dl's complete files.
With rTorrent you can also set it to not just move the files but rather hardlink instead. This makes sure you don't chew up drive space as it isn't duplicating the data. It also means that your are free to delete the files you've transferred using SS (from that new 'sync' folder) as the files that are seeding are still on the seedbox.
Interesting reading how others are using it. I am using it the same way as you but I am interested between hardlink vs. move - wouldn't the "move" option also not chew up drive space, since it is moving the file, rather than copying, the space the drive occupied before is now free?
Doesn't move also mean you are free to delete the files you've transferred to your local server using SS after importing them?
@ItsMeAPizza SeedSync should resume downloading the file once it notices that the size changed on the remote server. Let me know if this is not what you observe and I'll create a bug for it.
