> so now that I have my backup script files ready and functional from > either the command line or mouse click, I want cron running them, so am > doing "crontab -e" - i understand the format of crontab. i restart the > cron daemon or ensure that at least 2 minutes will pass before schedule > runs. however when the scheduled time has passed the expected file will > not have been created. i will have mail in var/spool/mail/roger saying: > > > /bin/sh: /windows/E/admin/backup-test.sh: /bin/bash: bad interpreter: > Permission denied > > alternatively i can use webmin to view the cron jobs and make it run > "now" - the same error is returned. > this will happen regardless of whether the cron job is run as roger or > as root. > > plenty of references to this error in google but nothing that seems > helpful - particularly since it will run from the command line and the > suggestions are usually to do with permissions. root and users both > have execute permission to the file. > > any suggestions anyone? > > Cheers, > Roger
At a guess, something to do with PATH or the fact that the partition that /windows/E is on is mounted noexec, or has funny permissions because it is on a windows filesystem, or something along those lines. How about putting it somewhere sensible like /usr/local/bin or /usr/bin and seeing what happens? > > > > > > > > > >
