> (like the file I wanted crontab to run only needed the file name not the > .sh on the end of it)
That *is* the filename. foo.sh is the name of a file. foo is the name of another file. These are not the same file. If you tell the OS to execute a file called foo.sh, then foo.sh is the name of the file it will execute. It will not attempt to execute foo, because that is not the file you told it to run... This was the main problem I saw with your cron scripts - you were telling it to execute a file that did not exist. HTH Vic. -- Please post to: Hampshire@mailman.lug.org.uk Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire LUG URL: http://www.hantslug.org.uk --------------------------------------------------------------
