I used Azureus before KTorrent. I've made torrents and uploaded them to a private tracker. I redownloaded the .torrent file and opened it with KTorrent 2.0beta1, when I pointed it to download where the data is, it didn't 'see' that it's already there and starts leeching from the other seeders.

To top that when I removed the torrent it asked me 'do you want to delete the incomplete data', I clicked yes (presuming I had selected the actual directory instead of the parent directory, which I hadn't) and it deleted the completed files! In azureus there is an option "force re-check" is there an equiviant in KTorrent?

In a nutshell: how do I open torrents for seeding?

ranunculoid wrote:I used Azureus before KTorrent. I've made torrents and uploaded them to a private tracker. I redownloaded the .torrent file and opened it with KTorrent 2.0beta1, when I pointed it to download where the data is, it didn't 'see' that it's already there and starts leeching from the other seeders.

To top that when I removed the torrent it asked me 'do you want to delete the incomplete data', I clicked yes (presuming I had selected the actual directory instead of the parent directory, which I hadn't) and it deleted the completed files! In azureus there is an option "force re-check" is there an equiviant in KTorrent?

In a nutshell: how do I open torrents for seeding?

You use the import plugin in 2.0beta1, we have added an auto import feature, where preexisting files will be scanned. This will be available in the next release.

Thanks.

KTorrent > all

Out of interest: How does it compare with uTorrent in terms of memory usage?

ranunculoid wrote:Thanks.

KTorrent > all

Out of interest: How does it compare with uTorrent in terms of memory usage?

Don't know, never used µTorrent (don't have windows installed)

Utorrent is a little extreme in this, but ram usage is not a problem on my system (1024MB)
I personally think it's more important that a program runs "nice" on a system instead of looking at 10MB ram usage, but that's me.

George wrote:

ranunculoid wrote:I used Azureus before KTorrent. I've made torrents and uploaded them to a private tracker. I redownloaded the .torrent file and opened it with KTorrent 2.0beta1, when I pointed it to download where the data is, it didn't 'see' that it's already there and starts leeching from the other seeders.

To top that when I removed the torrent it asked me 'do you want to delete the incomplete data', I clicked yes (presuming I had selected the actual directory instead of the parent directory, which I hadn't) and it deleted the completed files! In azureus there is an option "force re-check" is there an equiviant in KTorrent?

In a nutshell: how do I open torrents for seeding?

You use the import plugin in 2.0beta1, we have added an auto import feature, where preexisting files will be scanned. This will be available in the next release.

And it is not possible with ktorrent prior to this beta? For example I use ktorrent 1.2 so I cant seed the torrents ever d/l except if I install the last beta?

Gnux wrote:And it is not possible with ktorrent prior to this beta? For example I use ktorrent 1.2 so I cant seed the torrents ever d/l except if I install the last beta?

No George probably meant that there's an "auto import" feature added after the last beta. Both 1.2 and 2.0 beta has an import plugin which you can use to import and seed a torrent, you only have to enable this plugin.

stoeptegel wrote:

Gnux wrote:And it is not possible with ktorrent prior to this beta? For example I use ktorrent 1.2 so I cant seed the torrents ever d/l except if I install the last beta?

No George probably meant that there's an "auto import" feature added after the last beta. Both 1.2 and 2.0 beta has an import plugin which you can use to import and seed a torrent, you only have to enable this plugin.

Ah I dont see it in the 1.2 version. Nevermind, I install the 2.0 version and could find the nice "import existing d/l" option
Where could we find more plugins?

Gnux wrote:Where could we find more plugins?

8(!) plugins is not enough?
AFAIK all plugins that are scheduled to go in 2.0 are already in the beta.