Due to the way ctorrent works it spawns one process for each torrentfile you open. This means that it may start incurring more overhead than other bittorrent clients for a large number of torrents. I have not tested the exact impact, and I suspect it is fairly small due to ctorrent's small resource usage. The more noticable effect is that each process will have to open its own port (see below).
Some of the more interesting options right now are as follows:
torrent-directory=/opt/sybhttpd/localhost.drives/HARD_DISK/.ctorrent/watchdownload-directory=/opt/sybhttpd/localhost.drives/HARD_DISK/Download
client-host=localhost:9001port=9002ctorrent-args=-p 59332
All of the above (and more) is stored in the configuration file /opt/sybhttpd/localhost.drives/HARD_DISK/.ctorrent/dctcs.conf. You can edit this file to your liking. You will need to restart YODCTCS (or your entire NMT) for any changes to take effect.
An experimental interface for changing the configuration options can be accessed after installation on: http://NMT IP address:8088/stream/file=/opt/sybhttpd/localhost.drives/HARD_DISK/.ctorrent/config.php
If it exists, the file dctcs_extra in your root (share) directory will be executed when dctcs first loads at boot time. An example use of this script would be to start 'seed' torrents from another location than the default. This script is not supplied with the distribution. It will not be overwritten by the installer.
If it exists, the file dctcs_complete in your root (share) directory will be executed when ctorrent finishes downloading a torrent file. This script is not supplied with the distribution. It will not be overwritten by the installer.
Torrentwatch now also supports downloading torrents to a directory rather than directly to a client. You can have it download torrents to /opt/sybhttpd/localhost.drives/HARD_DISK/.ctorrent/watch and it should work with YODCTCS.