ctorrent

[papka__]

OK. Understand.
If I need to stop ctorrent client I must kill ctorrent processes and dctcs process?

(02-08-2009 01:40 PM)snarfle Wrote:  I'm not sure I understand this question completely. I'll try to answer it anyway.

It is not possible to select download locations for individual torrents. While this is theoretically possible, YODCTCS does not currently offer this feature. If this is really important to you, you could start a ctorrent client manually through telnet from the location where you want the downloaded file and have it connect to YODCTCS (on localhost:9001). You can then manage your torrent through the CTCS.

After modifying dctcs.conf you will have to restart the running dctcs process for changes to take effect (only dctcs- your ctorrent processes can keep running). I am currently looking in to a way to modify the configuration through a PHP script (I already have the configuration bit done, just need to figure out a way to restart dctcs safely).

Quote:For some reason whenever I stop a torrent and start it again it want to recheck the files before starting again.

"Stopping" a torrent with ctorrent means that the process (i.e. the torrent client) exits completely. Starting it again will result in a full hash check. If you want to keep the process running and avoid the hash check, use the "Pause" button instead.

[snarfle]

Quote:If I need to stop ctorrent client I must kill ctorrent processes and dctcs process?

Huh? Again, I'm not quite sure what you mean. To stop an individual ctorrent
client (= 1 torrent download), connect to the web interface, select the torrent
and click 'Stop'. One of the ctorrent processes will then exit.

To force a reload of dctcs.conf, kill the dctcs process only (e.g. kill `pidof dctcs`)
and then restart it. Your torrents (that is, ctorrent processes) will keep running
in the background no problem.

There is now a web interface available to modify the configuration file and restart
the dctcs automatically. See the web page for details.

[papka__]

Ok. Thanks.

Just have situation - NMT hangs on. Switch it off/on. Install new version. Ctorrent started ok and .... start to recheck all torrents
(already rechecked and previously seeded too).

(02-08-2009 04:58 PM)snarfle Wrote:  Huh? Again, I'm not quite sure what you mean. To stop an individual ctorrent
client (= 1 torrent download), connect to the web interface, select the torrent
and click 'Stop'. One of the ctorrent processes will then exit.

To force a reload of dctcs.conf, kill the dctcs process only (e.g. kill `pidof dctcs`)
and then restart it. Your torrents (that is, ctorrent processes) will keep running
in the background no problem.

There is now a web interface available to modify the configuration file and restart
the dctcs automatically. See the web page for details.

[hdfan]

So, if I understand correctly, if NMT hangs and have to be rebooted (and this happens, unfortunately, very often), all incomplete files will be verified (like in Transmission)? If so, is cTorrent verifies them faster than Transmission? Thanks!

[nianoniano]

I will try.

Thank you

[snarfle]

Quote:So, if I understand correctly, if NMT hangs and have to be rebooted (and this happens, unfortunately, very often), all incomplete files will be verified (like in Transmission)? If so, is cTorrent verifies them faster than Transmission? Thanks!

Both complete and incomplete files will be fully hash checked. I'm not sure about the performance of ctorrent vs. Transmission in this. As I understand it cTorrent should be quicker, but I'm not sure. I do know that cTorrent seeds while hash checking. I think it also already starts downloading while still checking but I'm not sure.

I'm having some unrelated issues with my NMT which prevent me from checking this properly.

I have however noticed (but this could just be me) that I don't have to reboot my NMT as often since I stopped using Transmission a while ago.

[papka__]

(02-08-2009 05:54 PM)snarfle Wrote:  Both complete and incomplete files will be fully hash checked. I'm not sure about the performance of ctorrent vs. Transmission in this. As I understand it cTorrent should be quicker, but I'm not sure. I do know that cTorrent seeds while hash checking. I think it also already starts downloading while still checking but I'm not sure.

I'm having some unrelated issues with my NMT which prevent me from checking this properly.

I have however noticed (but this could just be me) that I don't have to reboot my NMT as often since I stopped using Transmission a while ago.

Seems the situation with rehashing completed torrents is not good. If I have 10 completed torrents with size ~10GB each anyway process will be very long.
I will use Ctorrent for downloading but Transmission for seeding. Good application .... but rehashing....

[dany88]

mmm.....we may modify the sourcecode in order to rehash only downloading files, and maybe to rehash in a more convenient way for NMT (i have some ideas, but i must look some details)......

I will try the next week to see the sourcecode

edit:

-f Force saved bitfield or seed mode (skip hash check at startup)

Perform a fast startup by skipping the initial (or background) hash verification of the files. This option is not generally recommended since the client now performs initial hash checking in the background. Use this option only if CTorrent was shut down cleanly when last downloading this torrent and you are absolutely certain that the bitfield (if download is not complete) and data files are intact and correct. To emulate the old behavior of hash-checking all pieces before beginning download or seeding, use -f along with the -c option.

mmm....we can use -f, but i don't know if it is a good idea...the file could be corrupt....

[snarfle]

Quote:mmm....we can use -f, but i don't know if it is a good idea...the file could be corrupt....

It's not a good idea. Like you say, the file may be corrupt. Especially in the case
of NMT, situations where your torrent clients exit are usually crashes or unclean
shutdowns. After a crash/unclean shutdown a hash check should always be done
to guarantee the integrity of the data files.

Instead of changing the options, I would recommend going after the source of the
problem (which is that the NMT crashes frequently). It would be better to collect
as much information on the crashes as you can and report them to Syabas so they
can maybe fix the actual problem.

[papka__]

(02-08-2009 08:59 PM)snarfle Wrote:  It's not a good idea. Like you say, the file may be corrupt. Especially in the case
of NMT, situations where your torrent clients exit are usually crashes or unclean
shutdowns. After a crash/unclean shutdown a hash check should always be done
to guarantee the integrity of the data files.

Instead of changing the options, I would recommend going after the source of the
problem (which is that the NMT crashes frequently). It would be better to collect
as much information on the crashes as you can and report them to Syabas so they
can maybe fix the actual problem.

For incomplete torrents hash checking is needed, but for completed? Files already checked and saved.
To wait for correction of all bugs in NMT (IMHO it's not possible) is equal to wait for Transmission without bugs/hangs.
Why we need Ctorrent? It's light, stable, quick NOW. But we can't normally use it because NMT sometime crash due to self bugs. As I tell for ex if NMT crashes 1 time in a week - I need 2 days for recheck due to HD content size. Due to recheck it's not possible to use NMT normally. We need useful Ctorrent now - not after all bugs will be fixed.

[snarfle]

Quote:For incomplete torrents hash checking is needed, but for completed? Files already checked and saved.

The fact that the files were checked and saved at one point does not mean
they will stay that way. While admittedly it is unlikely that data corruption
will occur, silent corruption after a crash is not unheard of. Therefore the default
behavior can be considered a normal precaution.

I don't understand why it's "not possible to use NMT normally". I restarted my
NMT earlier this evening with about 10GB worth of torrents downloaded and
they were done checking after I finished watching a movie (on the NMT) while
it was busy.

The other problem with disabling hash-checks is that there is currently no way
of doing it automatically. YODCTCS is "dumb" in the sense that it just hands
over control to the ctorrent process. The ctorrent process won't know if a file
is for seeding or for downloading unless it does its hash-check, or you tell it
manually by adding a '-f' flag. Because YODCTCS can't decide what to use
a -f flag on, it's not currently possible to do it automatically.

The author of YODCTCS is also aware of this issue. See this thread on the
OpenWRT forum for a discussion about the topic (dske is the author):
http://forum.openwrt.org/viewtopic.php?id=13263&p=2

I don't believe this is something which can be "fixed" (though again, I don't
believe it's broken) without modifying YODCTCS, which is not something I
have the time or the will for these days.

All that being said, as a work-around for you, what you could do is move
or copy all the .torrent files for torrents you completed to a separate
directory (possibly by using the -X option to ctorrent) and use a script like
so (off the top of my head, not sure if it'll run):

Code:

#!/bin/sh

cd /share/Completed
ls *.torrent |awk '{system("ctorrent -S localhost:9001 -p 59332 -f \""$0"\"")}'

[mig25]

And this will be the best solution for completed torrents ,with we want to seed.
In this code you for sure forgot about -d switch ,witch sets cTorrent as daemon process (backgrounding it)

[papka__]

(02-08-2009 11:20 PM)snarfle Wrote:  The fact that the files were checked and saved at one point does not mean
they will stay that way. While admittedly it is unlikely that data corruption
will occur, silent corruption after a crash is not unheard of. Therefore the default
behavior can be considered a normal precaution.

I don't understand why it's "not possible to use NMT normally". I restarted my
NMT earlier this evening with about 10GB worth of torrents downloaded and
they were done checking after I finished watching a movie (on the NMT) while
it was busy.

The other problem with disabling hash-checks is that there is currently no way
of doing it automatically. YODCTCS is "dumb" in the sense that it just hands
over control to the ctorrent process. The ctorrent process won't know if a file
is for seeding or for downloading unless it does its hash-check, or you tell it
manually by adding a '-f' flag. Because YODCTCS can't decide what to use
a -f flag on, it's not currently possible to do it automatically.

The author of YODCTCS is also aware of this issue. See this thread on the
OpenWRT forum for a discussion about the topic (dske is the author):
http://forum.openwrt.org/viewtopic.php?id=13263&p=2

I don't believe this is something which can be "fixed" (though again, I don't
believe it's broken) without modifying YODCTCS, which is not something I
have the time or the will for these days.

All that being said, as a work-around for you, what you could do is move
or copy all the .torrent files for torrents you completed to a separate
directory (possibly by using the -X option to ctorrent) and use a script like
so (off the top of my head, not sure if it'll run):

Code:

#!/bin/sh

cd /share/Completed
ls *.torrent |awk '{system("ctorrent -S localhost:9001 -p 59332 -f \""$0"\"")}'

Hmm.... It's not so bad solution. Thanks. Will try tomorrow.

[papka__]

Yeah! Your workaround is cool. With some modifications it's working for me very good. Thanks a lot.

[rabside]

Hi guys,
Why don't you try rtorrent? It's really great!
and the web ui (rtgui) is fantastic.

what abouy it?