Quote Originally Posted by oleo View Post
Is there source code for this somewhere?
Yepp, currently in my computer

Quote Originally Posted by oleo View Post
Does this controller spawn new ctorrent process for each torrent?
Because of CTorrent/CTCS architecture, yes. My CTCS implementation spawn new enh-ctorrent processes for each torrent. With default 4MB cachesize. (Of course, it can configureable, users usually use 4-8MB cachesize) Hereby it has advantages and disadvantages unfortunately.
[+]You can control processes easily just a ps command and if anything goes wrong, just you can kill required processes.
[-]But use little more memory than the Transmission which use threads.
[+]You can start enhanced-ctorrent by manually with your favourite options and SCTCS can controll it also.
[-]Every ctorrent processes has own port to the communication that means if you use 10 torrent you must open 10 ports.
[+]But the seeding is very effective.
[+]A simple bandwith management has been implemented.
and so on...

Quote Originally Posted by oleo View Post
How does communicate?
Communication is TCP/IP. Each ctorrent process can communicate with sctcsd and vica versa.

Quote Originally Posted by oleo View Post
Web page looks nice
thanks. It use awk cgi. I'm supresied it is very fast in wl500gp.

Quote Originally Posted by oleo View Post
How does global speed limiter balances between jobs?
Currently it balances speed by very simple method. Static bandwith management means when you add a new torrent, the system recalculate the bw, and set new speed limit for all processes.
I'm working on dynamic bandwith management that can use idle capacity of bandwith and respawn to processes that require it.

thx,
seaky
http://sctcs.seaky.hu