When you run commands from command line they inherit the environment you got when you logged in. (e.g. /etc/bashrc, /etc/bashprofile, /etc/profile, $HOME/.bashrc, $HOME/.bashprofile, $HOME/.profile and/or others depending on the shell you use.)
When you run commands from cron they have a minimal environment so it is important to insure that the commands have everything they need. You went a step in the right direction by specifying full path to chmod and move.sh but it is likely something WITHIN move.sh itself that is having an issue. For example if it contains the "mv" command but doesn't have the full path to it then it might fail. Also there could be other environmental variables it is expecting. For example if you had at login a variable named "PICPATH" that had the location of your pictures this wouldn't be there in cron so you'd have to include it.
You can fix such issues by doing one of the following:
1) Insure all variables including PATH ($PATH) used in your login environment are set within the move.sh script.
2) "Source" all the files in move.sh that you normally "source" at login (the bashrc and profiles stuff mentioned above). Typically this is less than optimal because it will include terminal settings that aren't approrpiate for a background process run such as cron. (It doesn't necessarilly mean it won't work - it just makes for ugly output in logs.)
3) Use fully qualified paths for ever command and file in move.sh.
4) If you don't have access to modify move.sh itself you could create a "wrapper script" that does option 1 or 2 then runs move.sh. e.g. name a file movewrapper.sh and insert the following:
Code:
$!/bin/bash
export PATH=/bin:/usr/bin:/usr/sbin:/usr/local/bin:/home/myuser/scripts"
export PICPATH=/home/myuser/mypictures
/kunden/homepages/mylocation/mylocation/htdocs/release/sites/default/files/randompics/move.sh
Note that in the above /home/myuser/scripts and /home/myuser/mypictures are made up by me as examples of what you COULD include - they shouldn't actually be included (unless by some fluke they actually exist as such in your environment).
One way to see what is in your login environment is to run "env" or "set". You can then include as much or as little of that in your move.sh or wrapper script.
