Transmission add-on thread before MAY 2K10

[super-poussin]

yes

[rgakker]

Hi Super,

A couple of versions ago we had a problem with directory permissions, which were solved. When using 1.73b02, the old behaviour is back. Can you check the config files, and possible adjust?

best regards!

[super-poussin]

Hi Super,

A couple of versions ago we had a problem with directory permissions, which were solved. When using 1.73b02, the old behaviour is back. Can you check the config files, and possible adjust?

best regards!

it comes from new parameter in settings.json :

"umask" : 18,

so stop transmission and set the value to 0:

"umask" : 0,

I will do upload same version number with the change , but the parameter is undocumented actually

for sparc

for x86

[mkopel]

I am trying to use Transmission for the first time. I have been a long-time user of Vuze for OS X. Everything works great but I have 2 questions.
1. There is a directory under BitTorrent named "completed", what is it for? after a torrent completes it does not move the data there, it stays empty. It would be cool if it at least moved the .torrent file there, that way you could tell which torrents were complete without having to open the web interface.
2. I am using BitTorrent/sources as the autoload directory of torrent files. After a torrent completes I like to move the data to a new directory for organization. But if I forget to move the .torrent file out of sources, it will just start up again. Is there anything I can do about that?

I don't know if it matters, but I am not using the default download directory.
I have /media/Download/BitTorrent/ as the directory, with completed and sources directories under that.

Thanks for the great add-on, nice not to leave my computer on just to seed.

[super-poussin]

1) completed is no more use
2) the script used before to move completed torrent generate to much errors which can full your /
3) there's a transmissioncli command to move torrent
4) you can remove directory you did not use but they will appear again on each add-on update

[mkopel]

thanks for the quick reply...

what is transmissioncli and how do you use it? can you point me to any docs?

also, running on a readyNAS NV+, and it crashed overnight. should their be a max torrents parameter to limit the load on the NV+ cpu? How many torrents can it handle at once, I had about a dozen going over night.

thanks
mitch

[Trial_Master]

I'm trying to set up Transmission Remote but keep getting error "Connection Refused"

I've got Remote Host "localhost"
Port "8181"
Username "admin"
Password "password1"

I don't know if these are right settings can someone please help me?

[super-poussin]

can you post your settings.json file content (using code button)

[Trial_Master]

I only got my NAS on Monday and have just installed Tranmission this evening. The add-on you wrote works great I just don't know what I'm doing to get Remote running.

Code: Select all

{
    "alt-speed-down": 50,
    "alt-speed-enabled": false,
    "alt-speed-time-begin": 540,
    "alt-speed-time-day": 127,
    "alt-speed-time-enabled": false,
    "alt-speed-time-end": 1020,
    "alt-speed-up": 50,
    "bind-address-ipv4": "0.0.0.0",
    "bind-address-ipv6": "::",
    "blocklist-enabled": true,
    "dht-enabled": true,
    "download-dir": "\/media\/BitTorrent\/",
    "encryption": 1,
    "lazy-bitfield-enabled": true,
    "max-peers-global": 200,
    "message-level": 2,
    "open-file-limit": 32,
    "peer-limit-global": 240,
    "peer-limit-per-torrent": 60,
    "peer-port": 51413,
    "peer-port-random-enabled": 0,
    "peer-port-random-high": 65535,
    "peer-port-random-low": 1024,
    "peer-port-random-on-start": false,
    "peer-socket-tos": 0,
    "pex-enabled": true,
    "port-forwarding-enabled": true,
    "preallocation": 1,
    "proxy": "",
    "proxy-auth-enabled": false,
    "proxy-auth-password": "",
    "proxy-auth-username": "",
    "proxy-enabled": false,
    "proxy-port": 80,
    "proxy-type": 0,
    "ratio-limit": 2.000000,
    "ratio-limit-enabled": true,
    "rpc-authentication-required": true,
    "rpc-bind-address": "0.0.0.0",
    "rpc-enabled": true,
    "rpc-password": "{d15b146a3063b3ade7d0fecaa9602218a327a8c8gOoal64v",
    "rpc-port": 8181,
    "rpc-username": "admin",
    "rpc-whitelist": "*",
    "rpc-whitelist-enabled": true,
    "speed-limit-down": 400,
    "speed-limit-down-enabled": false,
    "speed-limit-up": 20,
    "speed-limit-up-enabled": true,
    "upload-slots-per-torrent": 14,
    "watch-dir": "\/c\/media\/BitTorrent\/sources\/",
    "watch-dir-enabled": 0
}


[super-poussin]

does it work without remote ?


did you try this one : http://code.google.com/p/transmission-remote-dotnet/ ?

[Trial_Master]

Yep works without Remote. Just tried the link you sent me and it worked straight away. Thanks!!!

How do you change the password from "password1"?

While I have your attention could you point me to a good post that shows how to set up scheduling with your settings.json file?

[super-poussin]

stop transmission

edit settings.json an replace the encrypted password with a plain-text one
"rpc-password": "super-poussin",

restart transmission

configuration file parameters

[Trial_Master]

stop transmission

edit settings.json an replace the encrypted password with a plain-text one
"rpc-password": "super-poussin",

restart transmission

configuration file parameters

Cool, thanks very much really appreciate your help!!!

[Trial_Master]

Can I assume that the download and watch directories can't be changed? I'm getting Permission Denied now.

[super-poussin]

yes it can but make sure new directories are world readable/writable