Jan
15
asked Return all primary keys affected by update query
Dec
27
awarded Teacher
Dec
15
comment Bash script acts differently depending on what executes it
I believe that you are right, i looked in filebot.sh (The script which is called by run.sh) and it had used ${HOME} which i have no replaced with the absolute path. Just to check, would it still be ok to use symlinks?
Dec
15
comment Bash script acts differently depending on what executes it
After giving the absolute path to the logs, they do actually return the correct stuff: /usr/share/filebot/bin filebot.sh
Dec
15
comment Bash script acts differently depending on what executes it
Yep: /home/xbmc/run.sh "%F" "%D" "%L" "%K" "%N"
Dec
15
comment Bash script acts differently depending on what executes it
Filebot.sh just runs java and the java class... It works fine when manually executed so this can't be the problem...
Dec
15
awarded Editor
Dec
15
awarded Commentator
Dec
15
comment Bash script acts differently depending on what executes it
Ah ok, so what environmental variables could they be and how would i set them?
Dec
15
comment Bash script acts differently depending on what executes it
Also, i tried out putting directory info via: pwd >> run.log and ls >> run.log however nothing is written?!
Dec
15
comment Bash script acts differently depending on what executes it
Possibly, but then why does it work when i manually execute the script rather than when uTorrent executes it...
Dec
15
revised Bash script acts differently depending on what executes it
added 540 characters in body
Dec
15
comment Bash script acts differently depending on what executes it
Please see original post for permissions
Dec
15
comment Bash script acts differently depending on what executes it
But its writing the error to run.log which is the stderr/stdout log file as stated in run.sh
Dec
15
comment Bash script acts differently depending on what executes it
Could it be that filebot.sh is owned by root, should i chown it to my user?
Dec
15
comment Bash script acts differently depending on what executes it
Is there anyway to record the output of the change in directory? So if it is failing to change, then we could know? UPDATE: change in directory didn't work, it says "line 9: filebot.sh: command not found"
Dec
15
comment Bash script acts differently depending on what executes it
Both files already have a+x
Dec
15
comment Bash script acts differently depending on what executes it
So, CD into "/usr/share/filebot/bin" and then call filebot.sh?
Dec
15
comment Bash script acts differently depending on what executes it
TORRENT_PATH is a parameter given to the script from uTorrent, i have verified the path is being given correctly by running the script used by uTorrent (it is stated in the uTorrent log) e.g /home/xbmc/run.sh "friends.s06e11.720p.bluray.x264-mrs.sujaidr.mkv" "/mnt/Storage/Downloads/Complete/TV/Friends Season 6 Complete 720p.BRrip.mrlss.sujaidr" "TV" "multi" "Friends Season 6 Complete 720p.BRrip.mrlss.sujaidr" And i'd assume the no-such-file is filebot.sh as thats the only script being called there, also filebot.sh has +x
Dec
15
asked Bash script acts differently depending on what executes it
1 2 3