 <p><strong>UPDATE SOLUTION FOUND!</strong> well the solutionin fact deleted some random files so I have taken it off until I figure out why.</p> <p>I leave this important note from before</p> <p><strong>ANYTIME YOU USE CRON</strong> I cannot emphasize enough the importance of specifying completely the full path of all sh files, files in arguments and any files you want to pipe output too such as >> /mydirectorywhereiwantit/output.txt in full in both your crontab file and your sh files script files. </p> <p>As I learned <strong>cron will look for files and write files in whatever directory it happens to be in while bashing</strong> and that can get EXTREMELY confusing if that is a different directory from where you normally type from the terminal. SO FULLY SPECIFY ALL PATHS TO ALL FILES IN BOTH CRONTAB AND IN THE CALLED SH SCRIPT FILES AND IN ARGUMENTS!</p> <p>Thanks to John Mark Mitchell who so kindly offer so many possible solutions.</p>