I'm downloading a file with Transmission. It shows a connection to a web seed. See the below screenshot:
What is that "web seed", shown in the picture (which kind of seeders?)? Is it safe?
I have a machine running Ubuntu 12.04 server with transmission-daemon running to handle bitorrents. Everything works fine except the transmission-daemon creates files as the user/group, debian-transmission
, and with 744 file permissions.
I would like to be able to delete and move these file from a samba share.
I considered changing the primary group of the user debian-transmission, but I was worried that might mess up access to other files.
I thought it would be better to change the default permission of new files created by debian-transmission to 774, and add myself to the group debian-transmission.
I know that this can be done with a umask, but my understanding is that this would be set in the .profile file and since debian-transmission has no home folder I wan't sure if that file existed for the user. So how to I accomplish this?
Suggestions or alternate solutions are welcome. Thanks in advance.
I have a lot of torrents and currently I am using transmission as my torrent client, there is a problem that after I change the the folder name (this is important for me to organize my music folder) transmission stop recognize the files although they remained the same.
So I desire to change client but I can't find the torrent files where can i find them?
I can't find out how to make Firefox open magnet-links in Transmission.
There is no option to make it the standard program for magnet-links in its properties, and as I am not experienced with the filesystem so I can't add it as the standard program in Firefox either.
I am running the latest stable version of Transmission (version 2.31 from the Transmission ppa). Any time I try to log in to the web user interface, I get hit with this:
409: Conflict
Your request had an invalid session-id header.
To fix this, follow these steps:
When reading a response, get its X-Transmission-Session-Id header and remember it Add the updated header to your outgoing requests When you get this 409 error message, resend your request with the updated header This requirement has been added to help prevent CSRF attacks.
X-Transmission-Session-Id: CBcYiodnQIHKYkhr9EceZOMW3ICgMSgt6j2FTCOXbcunA1tK
Anyway, I've had this problem with Transmission for the last couple of versions, and I haven't been able to find an answer as to how to fix this anywhere online. If anyone has any ideas, let me know.