Transmission

Do you have something in your watch dir now? What is the permission on the directory itself?

Not possible with current state. I would give them access to drop files in watch directory and store the completed torrents in an accessible location.

I was thinking about something similar a few months back. I was actually thinking we should add a checkbox to the confirmation dialog that says "Also delete data".

If you have subversive users with that skill level, then you will need to intervene at application level. Remove the functions from RPC.

If you are strictly using the web interface, I would edit the web files to remove the settings button.

I would edit the web interface and change the text field properties to read only.

Those setting can be set, or changed in many ways... but the real problem is: why are they not saved? The reason they are not saved could be only one of 2: They are deliberately unset by the start-up script. The daemon doesn't have write access to its own configuration. Since you say you edited set...

It apparently has the same hash or it does have the same hash? That is important. If you are sure it is exact, you could stop torrents and T, rename your 99% file to match the other torrent, start T, verify data, and start torrent to complete.

Looks like your outbound firewall rules may be blocking port.

Interesting. Never tried that method. I'll have to try that sometime. Here is a cmd line method:

.transmission-daemon -u <username> -v <password> -a 127.0.0.1,192.168.*.*"

Then you can ctrl-c out or kill process to find new settings file update.

I'm not sure where you read that. The best thing to do is stop transmission, delete your current password in your settings file, and then restart using the command line to enter your rpc username and password combo. That is where it will automatically convert your plain text password from the comman...

Are you entering the password directly in the settings file?

-IL500%FF-

I just pull from the svn and compile on CentOS.

Sounds like firewall or port forwarding issue.