Being able to time each script is really useful, I have just put
after each "wait" at the moment, but I think if I google some date functions, I could get the script to calculate timings and print them after they have all run, which is useful. Especially as after this long process has run, something needs to be run on another server and previously i was doing it the next day, but this way I can have a much more accurate idea of how long everything is taking and get the next process to start at an appropriate time.
Load times is another thing that would be useful for me to monitor during the process, as it does at times cause a heavy load.
Thanks for the tip from Grail as well that if one fails for some reason I need to think about how to have that covered, some if statement maybe, I will have a read around today, not having heard about "exit codes" before, the phrase sounds like they may be able to be used to do that somehow.
The reason it has been done this way, was due to when I started writing the scripts, I had never written a bash script, so I was doing bit by bit and each time I had to resort to php, I was ending the bash process and calling the php. When I tried running a php script from within bash, the next bash command was executing before the php had finished, but it may be I had made some other error. At least with the various script files, it keeps the process structure clear in my mind for now, but in the future maybe I will put them all together so that they run in the foreground.