Bashscripts.org

Well at least a part of it...



This script is located in /usr/local/bin and converts the flv files in the current directory to mp3 files in a directory called mp3 that is in the current directory.

eg:
tmp/ - flv files go here
tmp/mp3 - script produced mp3 files go here...

Why doesn't the find command actually run?? The script stops dead as if the cd command does not work and obviously the find command doesn't find anything!

If I manually run the find command in the mp3 directory that works fine...

Total beginner here too! Cant seem to fathom it out - If anyone has any good links to pdfs/docs for BASH Scripting I'm all ears!

The script itself seems okay (apart from some if-then-else-fi's in case of errors)
The only tip I can give you if you want to debug the script yourself is: put a set -x before the commands you want to debug and set +x after the last command. If you want to debug the entire script, which might produce quite a lot of output, put it right below the #!/bin/bash line.

Thanks like I said complete beginner to scripting so I need all the help I can get!

Been doing some testing/debugging on my script...

if I put it in /usr/local/bin the last two lines won't work

if I put it in /home/martin/bin they will - So I think thats where I shall keep it...

Why is that anyone know..??

The command works in whatever directory you call it in.

So calling the command "cd mp3" in the script might not be the best way to do that, as some directory might not contain a "mp3" dir. Putting the full path in the output variable would be the best way to go there.

Also, when running the command from /usr/local/bin or cron or other places than your own directory, or if your running it as another user, you could have $PATH issues, IE: commands might not be in your path.

echo $PATH

Many times, simply putting the full path to every command you call can fix those issues.

IE: /full/path/to/ffmpeg instead of just ffmpeg.

Clear as mudd right ?