New Transmission add-on thread

i think i've got it!!
various tweaks done, not sure which one fixed (in the order they popped into my head when writing this)..

- disabled watch folder temporarily (stop service, edit config file, start service and left it for 20mins and then re-enabled)
- reset permissions on all user data locations that transmission used. for me this was media & data shares. owner was the folder name, group was 'nogroup'. transmission was stopped while permissions propogated.
- add in '\' before any '/' in the config file for any folder locations. ie: '\/c\/data\/torrents'
- rename config file to .old and reinstall transmission; config file recreated.
- setup network connection limits in config file, using http://forum.utorrent.com/viewtopic.php?id=58404 as a guide. for me on 700kbit/s upload, this was reduce the pre-defined limits by around 20%.

transmission now ranging between 40-60% cpu time on 18 download, 12 seeding with a user-set limit of 250k down, 50k up.

currently using 2.01 final.

thanks for all your help guys - looks like with a 'benchmark' from other users experiences and performance claims there was something was up with my box which i've now fixed!

im wondering now i've set the permissions correctly, if this may have a bearing on if torrents will keep their status or not (in reguard to SP's start/stoptrans.sh scripts) - time will tell on that one.