Transmission

How do i change the format to ASCII? That depends on the editor you use. I guess you're using TextEdit.app, then use "Save as...", and in the options change the format to "plain text"... if that is an option (I don't use Mac OSX), if not... you can do it on a terminal, with some...

You edited the script as UTF, change it to text (ASCII text). The quotes you see, are not quotes (") but the UTF equivalent (probably opening, and closing quotes), which is not valid as quotes on a script.

You didn't answer any of my questions. That is rude. You really should start by using the terminal. The lines I suggested adding will make the bash script tell you what its doing (when you run it on a terminal -- Terminal.app in Mac speak), the log is going to change name each time you run the scrip...

Its says "It"? Am I supposed to guess what you are talking about? the script manually pressed Are you running scripts by double clicking on them? Have you tried running them on a terminal? Sorry I didn't realize this was on a Mac, I don't know what could be different there, but the last p...

Looks like Transmission is not setting environment variables correctly before the bash script is called which relies on them. (said by one on the forum on filebot) Wrong. A lot of people use scripts with Transmission, and we don't have any problem like that, the variables are set. if $TR_TORRENT_DI...

when you type vi in linux and you get that intro screen with the version and the basic navigation info? No you don't. That depends on what version of "vi" you have installed, and there are several (yes I use vim, and vi is just a symbolic link to it). I figured I don't need to enter into ...

You mean you don't see anything you type?

That's just bad settings, either putty, or the shell. Try 'reset' or 'stty sane', even if you don't see what you type.

Does anyone know if this all down to the missing libminiupnpc5 install? No, its not. With version 1.93 you'll have to do a lot more work: libevent has to be a version before the 2.x series, which is the current. You don't need to install it, you can build it alongside Transmission, and link statica...

You are using transmission-daemon, to set authentication: Read Editing Configuration Files , look for options rpc-authentication-required , rpc-username , rpc-password . Also check rpc-enabled , which has to be enabled, rpc-whitelist-enabled , which could be either way but, if it is enabled, then rp...

a Debian based My Book Live You need terminal access, ssh is the most common. where I'd start Extending Transmission using Scripts My goal ... There are tools for that, none as far as I know that fit exactly, some are used with Sickbeard, Couchpotato, and other similar tools. I'm no expert on this ...

To be more complete, I use: Just in case there is no torrent's dir (i.e. just one file).

Jingo wrote:Is there any internal variable that can be used?

Actually its 2: "$TR_TORRENT_DIR/$TR_TORRENT_NAME"

Inside quotes.

my addition worked fine No it really didn't, just appeared to work. You can't use "find *.rar", the asterisk is expanded by the shell, find is not looking beyond the top directoy just returning what the shell already expanded (which in your test just happens to be the rar file you wanted)...

Did you even try my changes? It "seems wrong" because its wrong. I just didn't want to sound too harsh. Look at the manual for find . It doesn't matter that the original script, which doesn't come from Transmission, is also wrong. TR_TORRENT_DIR could contain spaces, and other characters, ...

The whole addition seems wrong for a shell script, try it like this: PATH=/usr/bin:/bin cd "$TR_TORRENT_DIR" find -name "*.rar" | while read file do unrar x -inul "$file" done The PATH would need to be changed if the programs used (find, unrar) are somewhere else. I'm n...